Turning ten engineers into a team that ships like fifty

The VP of Engineering pulled up the quarterly metrics and felt his stomach drop. Headcount was up 40% year over year. Features shipped was down 22%. He'd hired the best engineers he'd ever worked with — and somehow, together, they were slower than the team had been twelve months ago.

Standups had become status theatre — fifteen people taking turns saying things three of them needed to hear. Code review queues stretched to four days. Senior engineers were burning out as the human bottleneck for every decision, while talented juniors quietly stagnated waiting for someone to say 'go.' Two of the best engineers had already had 'exploratory coffees' with recruiters.

We ran a simple exercise: every engineer wrote down the three decisions that had blocked them most in the previous month. The pattern was instant — 80% of the blocks traced to four people who hadn't been given explicit decision authority. They were senior in title, but the org chart had never told the team it was okay to listen to them. We fixed the org chart before we fixed anything else.

• Audited rituals, ownership, and decision rights across the team
• Designed three squads with explicit charters and on-call rotations
• Authored role scorecards for IC, senior, staff, and lead tracks — with crisp leveling criteria
• Coached leads through the rollout and a 30-day check-in

Cycle time dropped 46% within two months. The team shipped two major features the previous quarter had been blocked on, and two engineers stepped into staff roles with clear paths. The recruiter coffees stopped.