The Coordination Tax: Why Work That Belongs to Everyone Gets Done by Whoever Asks Last

Every organization has work that technically belongs to the whole organization and practically belongs to no one. Cross-functional reporting that three departments each assume another department is producing. Customer communication that sits at the boundary of sales and service. Vendor relationships that touch procurement, legal, and a business unit simultaneously. When ownership of that work is unassigned, it does not stay undone forever. It gets done, eventually, by whoever last complained loudly enough to mobilize a response.

This is not a people problem. It is a structural condition, and most organizations above a certain size carry more of it than their leaders recognize.

How Shared Responsibility Becomes No Responsibility

When an organization designs roles and assigns accountabilities, it generally does so by function. The logic is sensible: group similar expertise, create clear reporting lines, and let each leader own a defined domain. What this structure does not naturally produce is clarity about the work that lives between domains.

The gaps are not oversights. They are almost unavoidable artifacts of drawing organizational lines through what is actually a continuous flow of work. A boundary placed between marketing and sales creates a seam. A boundary between engineering and customer success creates another. At each seam, some work requires both sides, and neither side has a mandate to own it entirely.

In practice, that ambiguity resolves in one of three ways. The first is that someone in one function informally adopts the work because they find it important or because their manager pushes them toward it. The second is that the work escalates repeatedly until a senior leader allocates time to coordinate it. The third is that the work gets done poorly, inconsistently, or not at all, and the organization notices only when something downstream fails.

None of these resolutions is stable. The informal adopter moves on or burns out. The senior leader becomes a recurring coordination bottleneck. The downstream failure becomes a recurring incident that the organization treats as exceptional rather than systemic.

The Cost That Does Not Appear on Any Report

The coordination tax does not show up cleanly in budget reviews or performance dashboards. It accumulates in the form of senior time spent on decisions that should have resolved at a lower level, duplicate work produced by teams that did not know the other team was already working on the same problem, and meetings convened to establish alignment that should have been established structurally from the start.

For an organization of several hundred people, consider hypothetically how much senior calendar time in a given quarter is devoted to questions that recur because no one owns the answer. The meetings to align on those questions look individually small. Cumulatively, they represent a material drag on executive bandwidth that could otherwise focus on judgment-intensive work.

There is also a morale dimension. People who reliably inherit work no one claimed, simply because they were willing to ask about it, eventually either stop asking or leave. The most engaged and curious employees are often the most exposed to this dynamic because they are the ones who notice the gap and try to fill it.

The Distinction That Makes Ownership Meaningful

Clarity here requires separating two concepts that organizations often conflate: accountability and involvement.

Involvement means that a team or individual has a stake in the outcome and needs to contribute to the work. Multiple parties can and should be involved. Accountability means that a single named party is responsible for ensuring the work happens at the required quality and on the required timeline. Accountability cannot be shared without effectively being eliminated.

When organizations announce that a piece of cross-functional work is "jointly owned," they have usually assigned involvement without assigning accountability. The word "jointly" is doing significant work there, and it is rarely doing it well. Joint ownership sounds collaborative. In practice, it means that when the work is late or incomplete, every accountable party has a plausible explanation for why the other party is responsible.

The structure that works is straightforward even when the politics of establishing it are not: one named accountable party, with the authority to make decisions and the obligation to escalate when they cannot, plus a clear list of contributing parties who have defined obligations to that accountable owner.

How to Surface the Gaps Without a Full Organizational Redesign

Identifying where coordination gaps exist does not require a large diagnostic initiative. A practical starting point is to look for work that escalates to leadership more than twice. If the same coordination question reaches a senior leader repeatedly, the answer is not to make a better decision in the moment. The answer is to assign ownership so the decision lives at the right level permanently.

A second signal is the recurring meeting that has no clear owner and no clear output. When standing meetings exist to keep parties aligned rather than to produce a decision or artifact, they are often serving as a coordination substitute for missing ownership. Examining those meetings and asking what structural assignment would make the meeting unnecessary is a productive diagnostic exercise.

A third approach is to map the handoff points in the organization's most critical workflows and ask explicitly: at each handoff, who is accountable for the work that exists in transit between the sender and the receiver? That transit state is where coordination gaps are most commonly found, and it is also where failures tend to originate.

Assigning Ownership Is a Leadership Decision, Not an Administrative One

One reason coordination gaps persist is that assigning ownership to work that currently belongs to no one requires a leader to extend someone's accountability into territory that may feel politically sensitive. The team that currently handles a piece of work informally may resist having it formalized under a different function. The function being asked to absorb new accountability may resist without corresponding resources.

These are real tensions, and they do not resolve through memo. They resolve when a leader with authority over both parties makes a clear decision, explains the reasoning, and holds the assignment stable long enough for it to become normal.

The resistance is usually proportional to how long the gap has existed. The longer a coordination gap has been handled informally, the more entrenched the informal arrangements become and the more disruptive a formal assignment feels. That is an argument for identifying and assigning ownership early, when the gap is small, rather than waiting until a visible failure creates urgency.

Organizations that treat ownership assignment as a routine part of how they design and revise work find that the coordination tax is manageable. Organizations that treat it as the natural cost of complexity pay it indefinitely, in senior time, in duplicate effort, and in the quiet attrition of people who grew tired of filling gaps no one else would claim.