Our original head of technology is a loyal, brilliant individual developer who has been with us since startup days, but as we automate our operations to prepare for an exit, he lacks the capability to lead a modern engineering team. How do we handle this transition without causing him to quit?

Question

Tyler Smith · Accepted Answer

This is a classic loyalty versus capability trap that many scaling owners face. Your legacy tech leader has high core value alignment, but as the company grows, the seat has outgrown his current capacity. If you keep him in a seat he does not GWC, you are hurting both the business and him.

You need to decouple his historic loyalty from his future seat on the Accountability Chart. Start by having a transparent, open conversation outside of your standard meeting rhythm. Frame the discussion around the future needs of the business as you build an exit-ready superstructure.

Show him the current Accountability Chart and where the company is heading. Discuss the difference between being a brilliant individual technical contributor and being an executive leader who manages a team, budgets, and complex integrations. Often, legacy performers are secretly relieved when they do not have to carry the burden of management anymore.

Create a new, highly specialized technical seat that leverages his unique skills without the leadership responsibilities. If he GWC's this new seat, transition him there. Ensure his compensation remains fair, but make it clear that the leadership seat requires a different set of capabilities. If he cannot accept this transition, you must be prepared to part ways to protect the scaling capability of your leadership team.