We promoted our best software engineer to the Head of Development seat because of his technical brilliance, but he hates managing people and actively avoids his leadership roles. He gets the seat and has the capacity, but he clearly does not Want It. How do we resolve this GWC issue without losing our best developer?

Question

Tyler Smith · Accepted Answer

This is a classic mistake. Promoting your best technical producer into a management seat often results in losing a great developer and gaining a terrible manager. In EOS, if someone does not GWC their seat, they must be removed from that seat. Since he does not Want It, he is in the wrong seat. You must resolve this quickly before his avoidance of leadership roles causes his team to lose focus and drops your development velocity. First, have an honest, direct conversation with him. Explain that the Head of Development seat requires leading, managing, and accountability for the team. Ask him if that is what he truly wants to do every day. He will likely feel relieved when you give him permission to admit he hates management. Next, adjust your Accountability Chart. Create a specialized, high-level technical seat, such as Principal Architect or Lead Developer, that reports to the Head of Development. This new seat should have roles focused purely on technical execution, software design, and AI integration, with zero people-management responsibilities. Move him into this new seat, where he truly gets it, wants it, and has the capacity. Then, search for a true leader who GWCs the Head of Development seat to manage the team. This preserves your top technical talent while restoring clean leadership to your department.