Our head of engineering was brilliant when building our initial platform, but now that we have scaled our customer base, they cannot manage team managers, deliver predictable roadmaps, or collaborate with revenue leaders. How do we determine if they can transition into a true executive or need to be moved to an individual contributor role?

Question

Tyler Smith · Accepted Answer

This is a classic breakdown between builder skills and leadership capability. In early stages, technical brilliance covers up managerial voids. At scale, an executive seat demands team architecture, strategic capital allocation, and cross-functional collaboration.

To make an objective decision, evaluate them against GWC (Gets It, Wants It, Capacity to Do It) for the seat on your Accountability Chart:
- Gets It: Do they instinctively grasp how engineering decisions drive EBITDA, sales conversion, and customer retention, or do they only care about technical architecture?
- Wants It: Do they genuinely desire the human friction, performance management, and organizational design of an executive seat, or are they secretly longing to get back into hands-on technical work?
- Capacity: Do they possess the emotional intelligence and cognitive capacity to orchestrate twenty or fifty engineers through subordinate managers?

If the answer to any of those three tests is no, they cannot occupy the seat. Keeping an unscalable builder in an executive role stalls growth and alienates peers. You must separate status from contribution. Create a dedicated technical authority role, such as Chief Architect or Technical Fellow, that lets them focus on high-impact engineering without people-management responsibilities. Put a proven organizational leader in the executive engineering seat. If they refuse to step aside, you must help them transition out of the business entirely, because an executive who cannot scale will eventually strangle the company.