Small Teams, Large Projects
Why organisational clarity sometimes matters more than headcount when the project is larger than the team.
A small team can carry a project far larger than its headcount suggests, but only when it is unusually clear about who decides what. The constraint is rarely capacity in the abstract. It is the number of open questions circulating without an owner.
Headcount hides ambiguity
Adding people to an unclear structure tends to multiply coordination rather than output. Each new participant needs context, and context is expensive to produce when nobody has written down how the work actually moves from a request to a delivered result.
Most delays I have seen were not caused by missing hands. They were caused by a decision waiting for someone who did not know it was theirs.
What small teams do differently
- One named owner per workstream, visible to everyone involved.
- A short written model of how the work flows, updated when reality changes.
- Direct contact with suppliers and customers rather than relayed summaries.
- Fewer meetings, but ones where decisions are actually made and recorded.
None of this is complicated. It is simply harder to sustain than hiring, because clarity has to be maintained continuously while headcount only has to be approved once.