The Coordination Tax
Here is something most engineering leaders don't want to say out loud: a meaningful fraction of the slowdown you feel as your organization grows has nothing to do with technical debt, tooling choices, or team skill. It's coordination overhead. The tax you pay for every boundary between people, systems, and decisions. I started calling it the coordination tax after watching a five-person team shi…
- The coordination tax is the overhead generated by every boundary between independently operating decision-makers, teams, systems, and ownership domains.
- Coordination overhead scales roughly quadratically with the number of independent parties, which is why organizations feel chaotic at 200 people even when the work hasn't changed.
- Tools make coordination overhead visible. They don't reduce it. Encoding decisions into systems is what actually reduces it.
- Wait time as a fraction of total cycle time is your coordination tax rate, in most organizations, it's forty to sixty percent.
- Platform engineering's highest-leverage job is identifying the coordination events that happen most frequently and eliminating them by encoding their resolution into the platform.
What the Coordination Tax Actually Is
The coordination tax is the overhead generated by every boundary between independently operating decision-makers. Decision-maker here is used broadly: it includes teams, but also systems, services, and ownership domains. Every time work crosses a boundary, from one team to another, from one system to another, from one review stage to another, it incurs overhead. That overhead includes the time to transfer context, the latency of waiting for the boundary to process the handoff, and the error rate
The Four Surfaces Where Coordination Tax Accumulates
Not all coordination surfaces are equal. The places where the coordination tax is highest are predictable once you know what to look for. Team boundaries are the most visible surface. Every time work needs to move from one team to another, a platform team to a product team, a security team to an engineering team, an infrastructure team to a developer, there's a handoff with context transfer costs, scheduling costs, and usually some queue. The deeper problem is that teams optimize for their own
Why It Compounds at Scale
The coordination tax doesn't scale linearly with headcount. It scales with the number of coordination paths between decision-makers, which is approximately quadratic in the number of independent parties. With two teams, there's one coordination path. With ten teams, there are forty-five coordination paths. With twenty teams, there are one hundred ninety paths. The math isn't quite this stark in practice, not every team coordinates with every other team, but the underlying dynamic is real. Every
Frequently asked questions
- Is the coordination tax the same as Conway's Law?
- Related but different. Conway's Law says that the system architecture tends to mirror the communication structure of the organization that produces it. The coordination tax is the overhead generated by that communication structure at runtime, the ongoing cost of operating a system whose architecture reflects org boundaries rather than functional b…
- How do you measure coordination tax in practice?
- The most useful proxy is cycle time breakdown. For a representative sample of features or changes, measure total time from start to done, then identify how much of that time was work time versus wait time. Wait time is where coordination tax lives: waiting for reviews, waiting for approvals, waiting for other teams to complete their piece. In most…
- Doesn't reducing team boundaries just create bottlenecks?
- Bottlenecks happen when a single ownership point doesn't have enough capacity to serve demand. That's a resource problem, not a structure problem. Most coordination tax doesn't come from too few teams, it comes from too many handoffs between teams. The interventions that work consolidate ownership of coordination events, not ownership of all work.…
- Is coordination tax avoidable or is it just the cost of scale?
- It's not avoidable, but the rate is variable. Every organization above a certain size pays coordination tax. The question is whether you pay twenty percent overhead or sixty percent overhead. Organizations that pay the lower rate have done specific structural work: they've encoded common coordination decisions into systems, consolidated ownership …
- How does the coordination tax interact with platform engineering investment decisions?
- Platform engineering is fundamentally a coordination tax reduction investment. When you evaluate whether to build a platform capability, the honest question is: which coordination events does this eliminate, and what's the recurring cost of those events compared to the one-time cost of encoding them? A platform that eliminates fifty cross-team coo…