Team Size: Why Small Teams Deliver Faster

Small teams deliver faster because every additional person increases the number of coordination paths disproportionately and decisions take longer. This article explains the mechanism, places the well-known rules and studies on team size and sets out a four-step approach to shaping teams for delivery capability.
Coordination Paths Grow Faster than the Team
In a team of n people there are n × (n − 1) / 2 possible communication links, so the number grows roughly with the square of team size. Frederick Brooks described this calculation in his 1975 book “The Mythical Man-Month”. Five people produce ten links, ten people 45 and fifteen people 105. The team triples in size, while the possible links increase more than tenfold.
Interactive tool
Team size calculator
Change the team size. You will see how the number of communication paths grows with every additional person.
This tool needs JavaScript to make a selection.
In daily work, by no means every link is used. The formula describes the upper limit of the coordination load and thus shows the direction: coordination effort grows faster than the capacity that additional people bring.
For delivery, this relationship has four consequences. The first is coordination effort: the more people involved in a decision, the more often questions go back and forth before anyone acts. The second concerns accountability. In larger teams a task is spread across more people, and it becomes less clear to each individual who will finish it. The third is handovers, because every handover between two people costs time and risks a loss of information. The fourth is decision time, because a group of twelve finds a common line harder than a group of five.
What is Brooks' law?
Brooks' law states that adding manpower to a late software project makes it later. Frederick Brooks formulated it in 1975 from his experience leading development of the OS/360 operating system at IBM. He gives two reasons. New people need onboarding, and that onboarding is done by exactly the experienced staff who are supposed to be delivering. In addition, every new person increases the number of coordination paths according to the formula above.
Brooks himself called the law an outrageous oversimplification. For steering, it yields a clear rule: on a late project, a narrower scope shortens the path to the result more reliably than extra headcount. Additional people help where the work can be split into independent work packages that a separate team completes without coordinating with the existing one.
What is the Ringelmann effect?
The Ringelmann effect describes how individual performance falls as the group a person works in grows larger. The French agricultural engineer Maximilien Ringelmann had men pull on a rope alone and in groups and published the results in 1913. The pulling force of the group stayed well below the sum of individual efforts, and the gap widened with each additional person.
Social psychology later split the effect into two parts. One part is coordination loss, because not everyone pulls at the same moment. The other is a loss of motivation that Bibb Latané, Kipling Williams and Stephen Harkins described in 1979 as social loafing: anyone who can no longer see their own contribution in the group makes less effort. For knowledge work, a 2012 field study by Jennifer Mueller showed that employees in larger teams perform worse because they experience less support from colleagues.
Is there an ideal team size according to research?
Research does not name a single ideal number, but it consistently points to teams of fewer than ten people. The reason is that the nature of the work differs from team to team. Four factors have proved useful as a test grid for the exact size:
- Task scope: a team responsible for a product feature from requirement to operation needs domain expertise and technology as well as operational responsibility. The more clearly the mandate is defined, the smaller the team can be.
- Dependencies: every dependency on another team creates waiting time. A small team with many dependencies delivers more slowly than a slightly larger one that completes the mandate on its own.
- Maturity: experienced teams with established routines coordinate with little effort. Newly formed teams need more time for coordination and benefit from a tighter scope.
- Role clarity: where responsibilities and decision rights are unambiguous, the number of queries falls. A group with more people can then work without slowing down.
The starting point is a corridor of five to nine people. It is consistent with the Scrum Guide, which has specified ten or fewer people since 2020, with Amazon's two-pizza rule and with J. Richard Hackman's team research. Within the corridor, the four factors determine the exact size. With more than two dependencies on other teams, the right size lies at the upper end; with a clearly defined mandate and a well-practiced team, at the lower end. How many people a manager can lead directly is covered in Span of control: how many direct reports a manager can lead effectively.
What Small Teams Require
A small team only delivers faster if it can complete its mandate without detours. If a skill is missing, an external dependency arises and the size advantage is lost. Shaping work into small units therefore requires a team that contains the necessary skills and decision rights that sit within the team. Leadership changes as well. The manager sets goals and boundaries, clarifies priorities between teams and removes obstacles, leading more teams with fewer individual interventions.
Shaping Teams in Four Steps
A robust team design follows four steps that delivery management uses to steer structural change.
The first step is an inventory. The company records its delivery mandates and the teams and handovers between them. In the second step, the skills each mandate requires are determined, along with which of them currently sit outside the team. In the third step, the design is created: teams receive a mandate with the necessary skills and a target size within the corridor, together with clear decision rights. The fourth step is implementation, with enablement of teams and managers, steered by metrics.
The effect shows in delivery. The company compares lead time, schedule reliability and decision time before and after the redesign. A pilot with two or three teams provides the comparison data before the design is extended to other areas. This shows which size achieves the shortest delivery time in which area, and executive management decides on the basis of its own figures. How team design relates to organization design as a whole is shown in the article characteristics and metrics of a high-performing organization.
Niehues Consulting as Partner for Team Design
Niehues Consulting combines analysis of the team structure with responsibility for implementation. In delivery management and organization design, the data on delivery mandates and dependencies, the team design and the roles with clear decision paths are created. During implementation, Marin Niehues steers the work as delivery manager, project manager or product owner until the teams deliver reliably in day-to-day business.
The approach follows the Niehues Delivery Model with the phases Understand, Build and Implement. Three review questions matter most for team design. In Understand: what is the baseline, and how do we measure success? In Build: which roles, decision paths and interfaces does operation require? In Implement: which metric shows after 90 days that the solution is landing? Marin Niehues looks at organizations from a delivery perspective and has led projects from VC-funded scale-ups to DAX 40 groups in 20+ countries. The entry point is a free 30-minute initial consultation via the contact page.
Frequently asked questions
What is the ideal team size?
A team should be small enough to contain all the skills the mandate requires, and no larger. The starting point is a corridor of five to nine people. Task scope and dependencies determine the exact number, as do maturity and role clarity.
How big should a Scrum team be?
According to the 2020 Scrum Guide, a Scrum Team typically has ten or fewer people, including product owner and Scrum Master. The earlier 2017 edition specified three to nine developers. If a team grows larger, the guide recommends splitting it into several teams sharing one product goal.
What is Amazon's two-pizza rule?
The two-pizza rule says a team should be small enough for two pizzas to feed all its members. It goes back to Amazon founder Jeff Bezos and refers to teams in single figures. It is a rule of thumb from practice whose direction matches team research.
What is the Ringelmann effect or social loafing?
The Ringelmann effect describes how individual performance falls as group size grows. Ringelmann demonstrated it with rope-pulling experiments published in 1913. Social loafing is the motivational part of the effect: anyone who can no longer see their contribution in the group makes less effort.
What is Brooks' law?
Brooks' law states that adding manpower to a late software project makes it later. Frederick Brooks justified it in 1975 with the onboarding effort for new people and the growing number of coordination paths. For steering, this means reducing scope first when a project runs late.
At what size does a team slow down?
A team slows down noticeably once it reaches double figures. The possible communication links grow roughly quadratically according to the formula n × (n − 1) / 2, so coordination effort between five and fifteen people rises far faster than capacity. Whether a particular team is too large is shown by lead time and decision time.
What should you do if a team is too large?
The mandate is split into sub-mandates, and each sub-team receives the skills and decision rights for its part. Splitting purely by specialism creates handovers, so the split follows the delivery mandate.
Does this apply to teams outside IT?
The relationship applies to any work that requires coordination. Ringelmann's experiments come from agriculture, Mueller's field study from knowledge work. In sales, finance or production, the same four factors determine the right size.
Let’s talk about your initiative.
In 30 minutes we clarify where your organization stands and which step will pay off most now.
Request a consultation30 minutes · free · no obligation

