The Coordination Tax
When a system is designed badly, the difference does not show up as a system cost. It shows up as effort, absorbed quietly by the people doing the work.
Who actually pays
In most organizations I have worked inside, the people doing the work are rarely the source of the trouble. They are the ones carrying it.
They chase status the system should surface. They re-enter information that already exists two systems over. They keep a private record because the official one is not trustworthy enough to act on. They reconcile two numbers that should never have diverged. They hold in their heads the sequence that nobody wrote down, and they remember which colleague to ask, because the routing that matters is social rather than designed.
None of that is in anyone's job description. All of it is load bearing.
It is also unevenly distributed in a way that punishes the conscientious. The person who follows up is the person who cannot stand watching something sit, and once they have followed up twice they become the informal owner of that seam. Nobody appointed them. The organization simply discovered that the gap gets covered if it waits, and stopped needing to cover it any other way. The most reliable people accumulate the most unpaid coordination, and it is invisible in their workload right up until they leave.
Why it never appears as a cost
A tax you pay in money has a line item. A tax you pay in effort has a person.
When a handoff is broken, the organization does not record a failure. Somebody follows up. The follow up works, the work eventually moves, and the system that required the follow up is never charged for it. Every functional report shows a function performing adequately, because at the level the report is drawn, it is.
This is why the cost survives so long. It is not hidden by anyone. It is simply not the kind of thing the accounting was built to see, and the people best positioned to describe it have stopped noticing they are doing it. Ask someone how they get a request through and they will describe the official process. Watch them do it and you will see something else.
The measurement problem is structural rather than accidental. Functional reporting draws a boundary around each team and reports performance inside it. Coordination cost lives on the boundaries, so every report can be accurate and the sum of the reports can still miss the largest single expense in the flow. There is no level at which the number naturally appears, because there is no owner of the space between the boxes, and reporting follows ownership.
It also concentrates rather than spreading evenly. The heaviest cost sits on work that has stopped without anyone knowing, sitting in a state nobody monitors, neither blocked nor progressing until a person happens to look. It sits on information that has to be carried by hand between two systems holding versions of the same fact, where somebody quietly becomes the integration between them in addition to their actual job. And it sits on decisions with no defined owner, where the question is not difficult but is not obviously anyone's, so it waits for the most conscientious person in range to pick it up.
At scale
At Walmart I worked on enterprise operations large enough that getting anything finished required a dozen functions to stay in step. Work was not stalling inside teams. It was stalling between them, at the points where ownership, sequence and status were inconsistent, and the compensating effort was distributed thinly enough across enough people that no single team experienced it as a problem.
That thinness is the mechanism. If one team had been absorbing the whole cost it would have escalated within a month. Spread across twelve, it registered as an ordinary amount of chasing in each one, well inside the range everybody had come to expect of a large organization. The cost was enormous in aggregate and unremarkable everywhere it was actually paid, which is exactly the profile that survives review indefinitely.
Making ownership and status explicit around the work itself, rather than asking people to keep supplying them, increased project completion by 37 percent. The instructive part is that nothing about the individual work got faster. What changed is how much of it was being spent on knowing where things were.
The organization is not short of capacity. It is spending capacity on knowing where things are.
Why it compounds
Absorbed effort is stable, which is the worst property it could have. A broken handoff that people route around produces no incident, no escalation, and no evidence. It generates a workaround instead, and the workaround becomes the way it is done.
Then the organization grows, and the workaround scales with headcount rather than with design. Ten people compensating is an irritation. Two hundred people compensating is a structural cost that shows up as needing more people, which is a conclusion nobody can argue with, because the alternative was never measured.
The growth is worse than linear, because coordination cost tracks connections rather than headcount. Adding a team does not add one team's worth of chasing. It adds a new set of seams between that team and everyone it touches, each with its own ambiguity about who owns what and its own person who will end up covering it. This is the ordinary mechanism behind an organization that feels slower at four hundred people than it did at eighty while every individual is working harder. Nothing degraded. The number of edges went up.
How to see it without a study
The cost is measurable without commissioning anything, which matters because a study is itself a coordination expense and organizations that need this most can least afford another one.
Take one flow and count only two things. How many times a person had to ask where something was, and how many times a person had to supply information that already existed somewhere in the organization. Both are countable by watching, both are unambiguous, and both are pure loss under any definition. A week of that produces a number nobody can argue with, because it is not an estimate of effort or a judgment about performance. It is a count of events that either happened or did not.
The other cheap instrument is the calendar. Look at recurring meetings whose stated purpose is alignment, status, or unblocking. Each of those is coordination cost that has been formalized and given a room, which makes it the one form of the tax that is already visible if anyone adds it up. A weekly hour across nine people is not a meeting. It is a standing charge against the design that made it necessary.
What naming it changes
An unnamed cost still gets explained. It just gets explained wrongly, and the explanation determines the budget.
Absorbed coordination usually arrives at the executive level as a capacity problem. The team is stretched, throughput is short of what was promised, and the request that follows is for more people. That request is easy to justify, because the team genuinely is stretched, and it is the most expensive possible response, because the new people inherit the same arrangement and start paying the same tax on their first day.
It has a second wrong explanation, which is a performance problem. If the throughput shortfall is read as effort or capability, the response is closer management, tighter targets, and more reporting. Each of those adds coordination cost, so the intervention makes the underlying condition worse while appearing to address it, and the people who were already absorbing the most are the ones who feel the added weight first.
Named correctly, it is a design problem, and design problems have a different cost profile. They are cheaper to fix than they are to staff around, they stay fixed once fixed, and the saving compounds in the same direction the cost was compounding.
None of that argument is available while the effort is invisible. Which is the whole reason to give it a name.
If this describes an operation you are responsible for, the diagnostic is where that conversation starts.
How engagements begin
