Our original technical lead was instrumental in building our platform, but as our engineering organization has expanded, their lack of people management and operational discipline is crippling the department. How do we move them into an individual contributor seat without losing their technical genius or damaging morale?

Question

Tyler Smith · Accepted Answer

This is the classic founder trap of conflating technical capability with organizational management. Early on, your strongest technical problem-solver naturally sits at the leadership table. But leading a twenty-person engineering department requires people management, process architecture, budget allocation, and cross-functional coordination. It is an entirely different seat on the Accountability Chart.

You must address this through the lens of GWC. Your technical lead clearly Gets the technical architecture and Wants to build software, but they lack the Capacity to manage humans, direct roadmaps, and run departmental operations at your current scale. Have an honest, unsentimental conversation. Separate value to the company from executive status. Explain that your job as the leader is to place every person in a seat where they can excel and feel energized.

Redefine the Accountability Chart to create a distinguished Chief Architect or Principal Fellow seat that focuses entirely on innovation, deep technical execution, and high-level strategy without any direct reports. Strip the administrative, hiring, and management responsibilities from that seat and create a dedicated operational leadership seat, such as a VP of Engineering, to run the department. If you handle this with absolute clarity and dignity, frame it around their core genius, and maintain their financial standing, high-performing technical leaders will often breathe a sigh of relief when relieved of management duties they secretly dread.