Our lead software architect is a technical genius and a core values fit, but he absolutely hates managing people and resists the Lead, Manage, and Accountability role. He wants to remain a pure builder, but our current structure has him leading a team of five developers. How do we restructure the Accountability Chart to protect his technical focus while ensuring the team gets the leadership they need?

Question

Tyler Smith · Accepted Answer

This is a common issue in technical and creative fields. We often promote our best individual contributors into management seats as a reward, only to realize we have lost our best builder and gained a miserable, ineffective manager.

The Lead, Manage, and Accountability (LMA) role is non-negotiable for anyone sitting in a seat that has direct reports. If your lead architect does not want to do LMA, then he does not GWC a management seat.

To solve this, you need to split the technical leadership from the people leadership on your Accountability Chart. Create two distinct seats under your Head of Technology or Integrator.

The first seat is the Lead Architect. This is an individual contributor seat focused on high-level system design, coding standards, and technical innovation. This seat has zero direct reports and no LMA responsibilities, freeing him to do what he does best.

The second seat is the Engineering Manager. This seat is held by someone who excels at LMA, project management, and developer alignment. The five developers will report directly to this manager.

By separating these functions, you keep your technical genius happy and productive while ensuring your developers receive the coaching and structural accountability they need to hit their Rocks and scorecard metrics.