tyler-smith.com · Questions & Answers

Our Chief Technology Officer has been with us for twelve years, but as our team grew to twenty engineers, he refuses to do LMA and only wants to write code. How do we make an objective GWC call without insulting his tenure?

Tenure is not a substitute for GWC: Get It, Want It, and the Capacity to do it. Your CTO is currently occupying a leadership seat that requires LMA: Leading, Managing, and holding people Accountable. If he wants to sit alone writing code and refuses to manage his direct reports, he is failing the Want It and Capacity filters for that specific seat.

Keeping a technical founder or long tenured developer in a management seat they resent destroys engineering throughput. Your junior developers sit without clear direction, quarterly Rocks stall, and the CTO grows bitter because management responsibilities drag him away from technical problem solving.

Address this by separating technical authority from organizational management on your Accountability Chart. An enterprise needs high level architecture, but it also needs people management. Create two distinct seats beneath your Integrator:

- Head of Engineering: This person owns LMA for the development team, resource scheduling, sprint delivery, and engineering scorecard metrics.

- Chief Architect or Fellow: This person owns core code architecture, technical research, systems integrity, and intellectual property strategy, with zero direct reports.

Present this structural change during a private conversation focused on his unique ability. Frame it around the truth: the business has outgrown a structure where technical genius and team management sit in the same box. Moving him to an individual contributor seat where he can focus purely on technology protects company culture, honors his twelve years of loyalty, and installs proper accountability over your engineering department.

Category: Accountability Chart & Seats

← All questions