The Coordination Tax
When a system is designed badly, the difference shows up as effort, absorbed quietly by the people doing the work.
Who actually pays
In most organizations I've worked inside, the people doing the work end up carrying trouble that started somewhere else.
Day to day, they chase status the system should surface and re-enter information that already exists two systems over. Somebody keeps a private record because the official one isn't trustworthy enough to act on, somebody else reconciles two numbers that should never have diverged, and most of them hold in their heads the sequence nobody wrote down, along with which colleague to ask, because the routing that matters is social and was never designed.
None of it is in anyone's job description, and all of it is load bearing.
The load is spread unevenly, too, in a way that punishes the conscientious. The person who follows up is the person who can't stand watching something sit, and once they've followed up twice they become the informal owner of that seam. Nobody appointed them. The organization discovered that the gap gets covered if it waits, and stopped needing to cover it any other way. So the most reliable people pile up the most unpaid coordination, and nobody sees it in their workload until the day they leave.
Why it never appears as a cost
A tax you pay in money gets a line item, and a tax you pay in effort gets a person.
When a handoff breaks, what the organization records is somebody following 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.
Nobody has to hide the cost for it to survive this long. The accounting was never built to see this kind of thing, and the people best placed to describe it have stopped noticing they're doing it. Ask someone how they get a request through and they'll describe the official process. Watch them do it and you'll see something else.
The measurement problem is built into the structure. Functional reporting draws a boundary around each team and reports performance inside it, and coordination cost lives on the boundaries, so every report can be accurate while the sum of them misses the largest single expense in the flow. There's no level at which the number naturally shows up, because nobody owns the space between the boxes, and reporting follows ownership.
The cost also gathers in particular places. The heaviest of it sits on work that has stopped without anyone knowing, parked in a state nobody monitors, neither blocked nor moving until a person happens to look. A good share lands on information carried by hand between two systems holding versions of the same fact, where somebody quietly becomes the integration between them on top of their actual job. The rest collects around decisions with no defined owner, where the question is easy enough and belongs to nobody in particular, 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. The work stalled in the spaces between teams, at the points where ownership, sequence and status were inconsistent, and the compensating effort was spread 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, so people no longer had to keep supplying them, increased project completion by 37 percent. The instructive part is where the gain came from: the individual work moved at the same speed as before, and far less of it was being spent on knowing where things were.
The organization has the capacity, and it's spending it 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, just a workaround, and the workaround becomes the way things are done.
When the organization grows, the workaround grows with headcount, and nothing in the design pushes back. Ten people compensating is an irritation. Two hundred people compensating is a structural cost that shows up as needing more people, a conclusion nobody can argue with, because the alternative was never measured.
The growth is worse than linear, because coordination cost tracks the connections between people. Adding a team 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'll end up covering it, which comes to far more than one team's worth of chasing. An organization that feels slower at four hundred people than it did at eighty, while every individual is working harder, is usually running on exactly this mechanism. Nobody got worse at anything, and the number of edges went up.
How to see it without a study
You can measure the cost without commissioning anything, which matters, because a study is itself a coordination expense and the organizations that need this most can least afford another one.
Take one flow and count just 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. You can count both by watching, neither is ambiguous, and under any definition they're pure loss. A week of that produces a number nobody can argue with, because it's a count of events that either happened or didn't, with no estimate of effort or judgment about performance mixed in.
The other cheap instrument is the calendar. Look at the recurring meetings whose stated purpose is alignment, status or unblocking. Each of those is coordination cost that's been formalized and given a room, which makes it the one form of the tax already visible to anyone who adds it up. A weekly hour across nine people is a standing charge against the design that made it necessary.
What naming it changes
An unnamed cost still gets explained, only wrongly, and the explanation determines the budget.
Absorbed coordination usually reaches the executive level looking like a capacity problem. The team is stretched, throughput is short of what was promised, and the request that follows is for more people. Justifying it is easy, because the team genuinely is stretched, and it's also the most expensive response available, because the new people inherit the same arrangement and start paying the same tax on their first day.
There's a second wrong explanation too, which reads it as a performance problem. If the throughput shortfall is taken as a matter of 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 feel the added weight first.
Named correctly, it's a design problem, and design problems have a different cost profile: they're cheaper to fix than to staff around, they stay fixed once they're fixed, and the saving compounds in the same direction the cost was compounding.
None of that argument is available while the effort stays invisible, which is the whole reason to give it a name.
If this describes an operation you’re responsible for, the diagnostic is where that conversation starts.
How engagements begin
