The Right-Size Team Is Smaller Than You Think

Every struggling project eventually gets the same prescription: add more people. In eleven years, I have never seen this work the way leadership expects it to.

Brooks's Law is fifty years old and still ignored daily. Adding people to a late project makes it later. The communication overhead grows quadratically. The new people need onboarding. The existing people stop building to start explaining. You lose weeks before you gain anything.

The Two-Pizza Heuristic Is Real

Amazon's two-pizza team rule gets cited so often it has become a cliché, but clichés persist because they are true. The most effective teams I have managed had five to seven people. Small enough that everyone knows what everyone else is doing. Large enough to have the skills needed to deliver end to end.

When I do capacity planning, I resist the urge to staff up to match the backlog size. Instead, I ask: what is the minimum team that can deliver the most important outcomes? Then I ruthlessly prioritize the backlog to fit that team's capacity.

When to Add, When to Cut Scope

There are legitimate reasons to grow a team. New workstreams, geographic coverage requirements, or building bench strength for succession. But if the reason is "we have too much work," the first move should be cutting scope, not adding headcount.

I have had hard conversations with stakeholders about this. "We cannot do all twelve features with this team in this quarter" is uncomfortable to say. But it is more honest than hiring three contractors, watching velocity actually drop for six weeks while they onboard, and still missing the deadline.

Right-sizing is a discipline. It requires a PM who is willing to say no to scope and defend the team's capacity as a constraint, not a problem to be solved with more bodies.