Coordination cost grows faster than output as a team gets bigger
Aliases: diseconomies of collaboration scale · coordination overhead growth · marginal coordination burden
What it is
Superlinear coordination cost describes how, as a team grows, the number of interfaces that need to stay aligned grows faster than headcount itself, so total coordination effort does not scale proportionally with people added — it accelerates. Output is usually bounded by how many genuinely independent parts a task can be split into, so it rises fairly gently; coordination cost instead accelerates with the number of potential interactions, and the gap between the two growth rates is the actual root of diseconomies of scale in collaboration — not a vague sense that "more people means a bit more friction."
Why it happens
Every additional person in a multi-person collaboration can, in principle, form a relationship needing alignment with every existing member, so the number of potential interactions swells quickly as headcount grows. Even though actual interactions fall well below that theoretical ceiling — most teams suppress the swell through hierarchy, division of labor, and designated interface contacts — the coordination need that gets compressed does not vanish; it shifts into aggregation points like meetings, reviews, and status syncs instead. Output growth, meanwhile, mainly depends on how many independent units a task can be decomposed into, a count that rarely rises proportionally just because the team got bigger — so coordination effort's growth rate keeps outpacing output's.
Studying it
Team communication network analysis can count how many information-exchange relationships actually occur in teams of different sizes and how that count trends with headcount, set against self-reported meeting duration and review-round shares of coordination activity. Cross-project comparison needs to control for the task's own dependency structure, because a task with few interfaces to begin with will not show pronounced superlinear coordination cost at the same headcount, and mixing such projects in dilutes the effect. Log analysis is preferable to retrospective recall, since participants typically underestimate the time they actually spend on alignment.
Where it stops holding
Superlinear growth is not an unconditional physical law: a team can compress potential interactions into a manageable count through layered structure, designated interface contacts, and a fixed communication cadence, flattening actual coordination-cost growth toward linear or near-linear. When a task is highly modular with very few dependencies, coordination-cost growth from added headcount also slows markedly. The conclusion therefore describes the default trend absent intervention, not an inevitable outcome of team growth.
Applying it
- Before growing a team, assess the task's dependency structure; if interface count would grow quickly with headcount, design a layered or modular structure to compress potential interactions first, rather than expanding and fixing it afterward.
- Introduce designated interface contacts or sub-team representatives to converge all-hands alignment into a few channels, suppressing superlinear growth in coordination need.
- Track how meeting duration, review-round count, and cross-person coordination message volume trend against team size, not just total headcount.
- If the coordination-activity share rises noticeably faster than output as headcount grows, consider splitting the team or tightening interfaces, rather than simply adding communication tools or more sync meetings.
Related
- Same group: V1.06.1 Net benefit of collaboration equals division-of-labor gain minus coordination cost · V1.06.3 Task decomposability sets the floor on coordination cost · V1.06.4 Where coordination cost dominates, adding people lengthens the cycle · V1.06.5 Tools can only lower coordination cost, not remove the task's own dependencies
- Nearby: V1.07 Effects of Group Size · V1.02 Granularity of Collaboration
- Search terms:
coordination cost·communication overhead·diseconomies of scale
Cards in the same group
- V1.06.1Collaboration only pays off once coordination costs are subtracted from the gains of splitting work
- V1.06.3How finely a task can be split sets the floor on coordination cost
- V1.06.4Adding people to a late, tightly coupled project makes it later, not sooner
- V1.06.5Tooling lowers the cost of coordination but cannot remove the task's own dependencies