Our top software architect was promoted to Head of Engineering, but he hates managing people and just wants to write code. He refuses to step back down to an individual contributor seat because he views it as a demotion and a cut in pay. How do we resolve this structural misalignment using GWC™?

Question

Tyler Smith · Accepted Answer

This is a common issue when scaling companies. You have promoted a brilliant technician into a leadership seat, but they do not pass GWC™ because they do not want the management responsibilities. Wanting a seat means genuinely desiring to do the actual work of the seat, which in this case includes leading, managing, and holding people accountable.

If your software architect hates managing people, he does not want the Head of Engineering seat. Keeping him there will destroy his morale and lead to high turnover among your developers.

To resolve this, you must separate professional status and compensation from management hierarchy. In many technology organizations, a senior individual contributor seat can be just as valuable, if not more valuable, than a management seat.

Design a highly prestigious, senior technical seat on your Accountability Chart, such as Chief Architect, that reports directly to the Head of Engineering or the Integrator. This seat should have zero people-management responsibilities, allowing him to focus entirely on writing high-level code and designing system architecture.

Align his compensation with the immense value he brings as an individual contributor. Show him that stepping out of the management seat is a strategic lateral move that leverages his true strengths, not a demotion. If he still refuses to step down, you must recognize that you have a right-person-wrong-seat issue that will ultimately hold your company back from a successful exit.