Scaling a studio from 50 to 150+ without losing the plot

Tripling a team sounds like a good problem. It isn't — not on its own. The systems that let 50 people ship smoothly quietly break at 120, and by 200 you're slower than you were at half the size, wondering where the velocity went.

I've run that scaling curve as a Production Leader in AAA — taking organisations from roughly 50 to 150+ people — and the lesson is always the same: you don't scale a team, you scale a production system. Add people without rebuilding the system and you don't get more throughput, you get more coordination overhead.

The situation

A fast-growing AAA studio. Hiring was ahead of structure: new teams forming faster than ownership, decision-making, and the way of working could keep up. The symptoms were familiar — slipping milestones, duplicated work across teams, decisions bouncing back up to leadership, and onboarding taking too long.

The approach

1. Mapped where work actually flowed — not the org chart, the real path a feature took from idea to shipped, and where it stalled.
2. Rebuilt ownership and decision rights so teams could decide without escalating, and leadership stopped being the bottleneck.
3. Installed a shared way of working — a common production cadence and governance so 150+ people moved coherently instead of as 12 disconnected pods.
4. Sequenced hiring to structure, not the other way around — every new team had clear ownership before it had headcount.

The outcome

The results showed up where scaling usually breaks:

• Milestone predictability improved — teams could commit to a plan and hold it.
• Coordination overhead fell — less time spent reconciling work across teams that shouldn't have diverged in the first place.
• Onboarding-to-productive time shortened, because new hires joined teams with clear ownership.
• Leadership escalations dropped as decision rights moved into the teams.

The point isn't any single metric — it's that the studio could keep growing without velocity collapsing, because the system was rebuilt to carry the weight.

What this means for your studio

If you're scaling and it feels like you're getting slower, the headcount isn't the problem — the production system underneath it is. That's exactly what a two-week Production System Audit is built to find: where the work actually bottlenecks at your current size, and what to change before the next 50 hires make it worse.