Our legacy CTO has been with us since our bootstrap days and is a great culture fit. However, as we scale, the seat now requires complex enterprise architecture planning and automated testing frameworks, which he lacks the capacity to lead. He is insulted by the idea of bringing in an outside tech executive. How do we handle this GWC issue without losing him?

Question

Tyler Smith · Accepted Answer

This is a classic right-person-wrong-seat scenario with a loyal team member. Your legacy CTO clearly has the Right Person component solved, but he no longer passes the GWC test for the scaling CTO seat. He simply does not have the capacity to lead a modern, enterprise-grade technology department. To handle this without causing him to quit, you must decouple his identity from his title. You need to structurally split the technology department on your Accountability Chart. Create a new, highly specialized seat, such as Chief Architect or Head of Legacy Systems, that focuses entirely on his core strengths and technical brilliance. Then, create the executive technology director seat above it that will be filled by someone with the capacity to manage the scaling team and automation. Before you have this conversation, run a Thinking Time session using this question: How might I present this structural change to our CTO so that he feels elevated for his technical genius rather than demoted for his management limitations? When you sit down with him, be direct and unsentimental but deeply respectful. Explain that the business has outgrown its current structure and that you need his genius focused where it makes the biggest impact. Show him the updated Accountability Chart and explain how this new seat protects his focus while bringing in the leadership the business needs to hit its goals.