Small teams, big results: why a five-person squad often beats a fifty-person programme
· agileminds
When a programme matters, the instinct is to add people. More hands, more speed. In practice the opposite is often true. Past a certain size, every extra person adds more coordination than capacity, and the programme slows under its own weight.
A small, well-led squad can do better, for three reasons: accountability, quality and pace.
Accountability
In a large programme, responsibility spreads thin. Work passes between teams, suppliers and workstreams, and when something goes wrong it is hard to say whose it was. A single squad owns its piece end to end. There is one team to ask, one team that feels the consequences and one team that learns from them.
Our squads are five people: a hybrid team with UK leadership and offshore engineering, working as one. The UK leads stay accountable for the result, which means clear ownership and a named person on the end of the phone.
Quality
Small teams share context. Everyone knows what is being built and why, so reviews are quick and meaningful, misunderstandings are caught early and quality is built in rather than inspected at the end. Automated testing and delivery pipelines are part of how the squad works from the first week, not a phase that follows.
Contrast that with a large group of individuals assembled separately. Each person may be capable, but nobody owns the whole, and the seams between their work are where defects live.
Pace
Fewer people means fewer hand-offs, fewer meetings and shorter routes to a decision. A small squad can release early and often, show real progress in each demo and respond quickly to what customers tell it. That steady pace matters more than a burst of activity, because it keeps momentum and gives leaders evidence to steer by.
The overlap between UK and offshore working hours helps too. Reviews and decisions happen live during a shared window rather than waiting overnight.
Where a squad is not enough
Some work genuinely needs more people, or several teams. The answer is then not one huge group but a small number of well-defined squads with clear boundaries, coordinated through portfolio governance. The principle is the same: small, accountable units, joined up deliberately.
What to ask before you add people
- Who is accountable for the outcome, by name?
- How many hand-offs does a piece of work pass through?
- How early do customers see something real?
- If we doubled the team, what would we spend on coordination?
Often the answers point towards a smaller, more focused team rather than a bigger one.
You can see how this works on our Engineering & Platforms page. If you have a product to build and want one accountable team to build it, Talk to us.
