The Hidden Cost of Coordination Friction on Growing Teams
Kinetiq Team
A team of five has ten possible pairs of people who might need to talk to each other. A team of fifteen has 105. Triple the headcount and you have multiplied the communication paths by more than ten, which is why the thing that felt effortless at five feels sluggish at fifteen without anyone having become worse at their job.
Fred Brooks made this point in The Mythical Man-Month in 1975, and it has aged unusually well. The arithmetic is not a metaphor. It is the actual count of relationships that have to be maintained for a group to stay aligned, and it grows roughly with the square of the group.
The Arithmetic Nobody Runs
Headcount Is Linear. Coordination Is Not
Hiring plans are built in straight lines. Two more engineers, one more designer, a second ops hire. Each addition is a known cost with a salary attached, and the expected return is treated as roughly proportional.
The coordination load added by each hire is not proportional, and it appears in no budget. The eleventh person does not add one relationship. They add ten, and every existing agreement has to be transmitted to them by somebody who already had a full week.
What It Costs in Hours
Asana’s Anatomy of Work Index puts a number on the visible portion. Workers lose an average of 58 minutes a day to duplicated work, and 58 to 60 percent of the working day goes to coordination overhead rather than the work itself. We went through the breakdown in where teams lose 60 percent of their day.
Run that against a team of twenty and the duplicated work alone is roughly 100 hours a week. Not the total coordination cost. Just the portion spent doing something twice because two people did not know about each other. Whatever else that team is short of, it is not effort.
The eleventh person does not add one relationship. They add ten, and every existing agreement has to be transmitted to them by somebody who already had a full week.
Why It Arrives So Suddenly
Growing teams rarely experience this as a gradual decline. They experience it as a cliff, usually somewhere between fifteen and forty people, and the timing confuses everyone because nothing obvious changed in the week it started hurting.
What changed is that the informal system ran out of capacity. Below a certain size a team coordinates by proximity and memory. Everyone hears most things. The person who knows is one desk or one message away. That works, it costs nothing to set up, and it is invisible precisely because it was never designed.
Then it stops working, all at once, because the informal channel has a hard ceiling. Nobody notices the ceiling approaching. They notice the day after it was crossed, and they reach for the explanations closest to hand: we hired too fast, the new people are not up to speed, the culture is slipping. All three are usually wrong.
The Costs That Never Reach a Spreadsheet
Decision Quality Degrades Before Throughput Does
The first thing to go is not output. It is judgement. Research from the American Psychological Association, cited in our piece on context switching, found that interruptions as short as five seconds can triple error rates on complex cognitive tasks, and that task switching can cut productive capacity by as much as 40 percent.
Coordination friction is an interruption generator. Every unclear owner produces a clarifying message. Every undefined handoff produces a meeting. The team still ships, so nothing looks broken, but the decisions going into what ships are being made by people who have been interrupted fourteen times since lunch.
Strategy Is the First Thing Crowded Out
Asana’s finding that only 7 percent of time reaches strategic thinking is the number executives should find most alarming, because that 7 percent is not evenly distributed. It is concentrated in exactly the senior people whose calendars fill first when coordination breaks down.
A leadership team spending its week resolving handoff disputes is not a leadership team. It is an expensive escalation queue.
Your Best People Leave First
This is the cost nobody models, and it is asymmetric. High performers are the ones most bothered by rework, most aware of what good looks like elsewhere, and most able to leave. Friction is a tax on their competence specifically, because they are the ones who could have been doing the 7 percent.
The Upside, Which Is the Same Data Read Forwards
McKinsey’s Organizational Health Index found organisations in the top quartile delivering three times the total shareholder returns of those in the bottom quartile. We covered the methodology in why healthy companies outperform three to one, and the components that drive the score are unromantic: clear direction, clear accountability, coordination and control.
That is the same list as the coordination problem, written as an asset rather than a liability. The gap between the quartiles is not talent. Both ends of that distribution hire from the same market.
What Actually Reduces It
The instinct is to add structure: more process, another layer of management, a heavier planning cycle. That usually makes it worse, because it adds coordination surface in the name of reducing coordination cost.
What works is narrower and cheaper. Reduce the number of relationships that have to be maintained for work to move, by making the agreements explicit so they do not have to be renegotiated in every pair.
- Assign decision rights before you need them. Who calls it when two functions disagree, named in advance, in writing.
- Define done at each handoff. Most rework lives at the seam between functions, not inside them. Handoff protocols are the mechanism.
- Write decisions down. A decision log is the cheapest thing on this list and removes an entire category of recurring argument.
- Declare priorities and decline things against them. A priority nothing was refused for is not a priority.
None of these is a project. Each is a sentence somebody writes once and then defends for a month. The reason they are hard is not complexity. It is that they require somebody to make a call that was previously being deferred, and deferring it felt collaborative.
If you recognise the pattern but are not sure which part is biting hardest, the companion piece on seven signs your team has coordination friction gives you observable tests you can run this week. And our Modern Team Operating System Guide sets out the five components these agreements belong to, with the sequence we recommend installing them in.
Related Reading
Written by
Kinetiq Team
The KinetIQ editorial team. We write about the systems behind how work actually gets done: communication, decision-making, accountability, handoffs, and the execution habits that hold up when teams are under pressure.
