Your team feels slow. Meetings take longer. Decisions get relegated. Nobody’s quite sure who owns what. The instinct is to add more people to fix it. “The org chart is wrong” people cry.
Having worked in those teams, I am telling you, your team is too big.
Jeff Bezos famously had a rule for this at Amazon: if a team can’t be fed with two pizzas, it’s too big. While apparently cheesey, the logic underneath it is serious. Somewhere beyond 6 to 8 people, something breaks. Clarity drifts.
Why Bigger Teams Get Foggier
Small teams don’t need much process because everyone already knows what’s going on. There’s one conversation happening, and everyone’s in it. The goal is obvious because you all agreed on it an hour ago, out loud, in the same room.
Add people past a certain point, and that single conversation splits into several. Now there are sub-groups with slightly different understandings of what “done” means. Priorities that felt obvious start needing to be written down, then explained, then re-explained. Decisions that used to take five minutes now need a meeting, and the meeting needs a follow-up.
None of this shows up immediately. It creeps in. A team of 12 doesn’t feel dysfunctional on day one – it just feels like everyone is a little busier, a few more syncs, catchups, 1:1s. A little less sure why they’re doing what they’re doing. That fog is the cost, and it compounds.
Small Isn’t a Limitation – It’s a Feature
The two-pizza rule isn’t really about pizza, or even headcount. It’s a proxy for a much more useful question: can this group still hold one shared goal in their heads without writing a document about it?
When the answer is yes, everything moves faster:
- Priorities are self-evident, not negotiated
- Ownership is clear by default, not assigned
- Feedback loops are immediate, not scheduled
When the answer is no, you don’t actually have a team anymore – you have a small organisation pretending to be a team, and it needs an org’s worth of coordination to function.
What To Do Instead of Growing the Team
If a team is straining, the fix usually isn’t more people. It’s fewer people per goal. Split the team along a real seam – by product surface, by customer segment, by the problem itself – and give each half a genuinely distinct mission. Two focused teams of five will almost always outrun one diffuse team of ten.
The hard part is that splitting feels like it should be a demotion or a loss of momentum. It’s the opposite. Small, sharp teams are how you keep the clarity that made the company move fast in the first place.