Our technology director is a brilliant hands-on engineer who built our first product, but now that we need them to build and lead an engineering department of fifteen people, they keep getting sucked back into coding and the department is stalling. How do we transition this legacy leader from an individual contributor to a true department head without losing them?

Question

Tyler Smith · Accepted Answer

You are facing a classic GWC issue on your Accountability Chart. Your technology director gets the technology and wants the technology, but they do not have the capacity to lead, manage, and hold people accountable for a fifteen person team. In the EOS framework, we separate the seats based on what the business actually needs, not based on titles or tenure.

You need to have a direct, loving, and brutally honest conversation with this leader. Use the GWC tool to show them the requirements of the department head seat. Explain that leading, managing, and holding people accountable is a full time job. It is not something they can do in their spare time between coding sprints.

If they do not have the capacity or the desire to manage people, you must redesign your Accountability Chart. Create a technical fellow or chief architect seat that allows them to focus 100 percent of their time on proprietary code and technology strategy. Then, hire or promote a dedicated engineering manager to run the department daily and sit on the leadership team.

By splitting the technical genius from the management seat, you preserve their loyalty, keep them in their zone of genius, and build a scalable department. This transition is critical to make your company exit ready because a buyer wants to see an engineering department that runs on a repeatable system, not one that relies entirely on a single heroic coder.