Our Head of Engineering has been with us for ten years and is brilliant at coding, but our new growth requires him to manage a team of fifteen developers. He is miserable, misses his one-on-one meetings, and admits he hates management. He fails GWC on the leadership aspects of his seat. How do we handle this without losing our best developer?

Question

Tyler Smith · Accepted Answer

Your developer is a classic example of a Right Person in the Wrong Seat. He fits your core values perfectly, but he lacks the desire or capacity to manage people. Management is a completely different skill set than technical execution. Forcing a brilliant technical mind into a leadership seat just because of tenure is a recipe for a toxic department and high turnover.

You need to restructure your engineering department on the Accountability Chart. Do not fire him. Instead, split the technical execution from the people management. You need to create two distinct seats on your chart.

One seat will be the Technical Director or Chief Architect. This seat will be responsible for system architecture, code quality, and solving complex technical problems. Your long-tenured engineer will sit in this seat. He will GWC this role because it aligns with his passion and skills.

The second seat will be the Engineering Manager or Team Lead. This seat will be responsible for resource allocation, project timelines, one-on-one meetings, and team performance. This person will manage the developers and report directly to the Integrator.

By creating this dual-track structure on your Accountability Chart, you preserve your developer's technical genius, eliminate his management misery, and ensure your team is led by someone who actually wants to manage. This keeps your exit preparation on track by securing your intellectual property without destroying team morale.