tyler-smith.com · Questions & Answers

Our engineering director was brilliant when managing five developers directly, but now that we have thirty people across multiple squads, projects are stalling and they cannot manage through supervisors. How do we fix this scaling breakdown?

This is the classic player-coach trap. What made this person successful at five developers was personal hustle, subject matter mastery, and direct intervention. What is required at thirty developers is architectural leadership, coaching managers, delegating authority, and building predictable systems. They have hit their operational ceiling in the Capacity component of GWC™.

Start by resetting the seat definition on your Accountability Chart. Document the exact difference between their old role and their current role. Their five roles can no longer include direct project troubleshooting. They must be accountable for developing team leads, tracking delivery velocity, and setting engineering standards. Ask them candidly: Do you genuinely Want this seat, or do you miss individual coding and tactical problem-solving? Many leaders say yes out of pride or fear of losing status, even though they hate managing managers.

Next, use the Delegate and Elevate™ tool. Force them to audit their weekly tasks. If they are still approving minor pull requests, solving line-level code issues, or running daily squad standups, they are suffocating their mid-level managers. They must systematically hand off tactical decisions to their leads.

Give them a clear ninety-day sprint to show measurable improvement in managing through layers. If projects continue to stall and they cannot step back from tactical rescue missions, transition them to a high-level individual contributor seat like Principal Architect, and hire a seasoned VP of Engineering who understands how to lead leaders.

Category: Leadership Team

← All questions