Coordination Debt

Organizations accrue coordination debt when AI tools multiply handoffs faster than anyone redesigns who decides what happens next.

The familiar complaint sounds like a pace problem. Everyone feels busier the faster the work moves. What is actually rising is unfinished judgment: each new tool, each nearly ready artifact, each “we can film that” request creates a handoff that still needs a human commit. Speed feeds the queue. It does not clear it.

When the Shot List Arrives Before the Decision

We were sponsoring a technology conference with a real booth presence: demos, video, the full show-floor stack. In parallel, the organization was hosting a competitive event open to attendees. Both workstreams asked creative and AV for on-site support.

The competitive event side moved fast. They produced an AI-generated run of show and a shot list for a live videographer. What they did not have was a creative output in mind, or an amplification campaign that would use the footage. The brief landed on the creative team anyway: film everything, figure out later.

Meanwhile the booth team had its own needs. The two requests were not coordinated. There was no shared treatment for how the footage would be used. The venues sat so far apart that the same staff could not adequately cover both.

Nobody lacked energy. What was missing was a named owner for the decision that turns surplus production into a usable next step. AI made the plan look ready. Judgment about purpose and priority never caught up. That gap is Coordination Debt: the accumulated cost of handoffs, syncs, and orphaned outputs when tools add interfaces faster than anyone redesigns who decides.

Agent Sprawl named unmanaged proliferation. This is the metabolism tax that follows: more work objects in motion, no clearer commit rights.

Ethan Mollick’s Centaurs and Cyborgs maps the jagged frontier at the level of who does which task: person, machine, or a blend. That is the production question. Coordination Debt is the absorption question that comes next: once the shot list exists, who can commit what it is for, who reviews, and who can override when two workstreams collide.

The collision itself is familiar from When Every Job Becomes an IT Job. Creative, AV, booth, and event ownership already sit on a hybrid spectrum. AI does not invent that spectrum. It floods it with nearly ready artifacts before anyone redraws the commit line.

Five Questions for Your Next Staff Meeting

Answer yes or no. Yes means debt is present.

1. Since your last AI tool adoption, has meeting or status load risen before decisions got faster?
2. Is there at least one weekly AI-assisted handoff where you cannot name one person who can commit without a sync?
3. Do AI-generated outputs regularly become new work for others before anyone has accepted ownership of the next decision?
4. Are any critical handoffs owned by “the team,” a committee, or an empty role rather than a named person?
5. If you empowered more people to decide tomorrow, would that create conflicting authorities before it cleared the backlog?

How to Read Your Score

0–1 yes. Local friction. Map the one weak handoff this week.

2–3 yes. Coordination Debt is accruing. Before you add another tool or another standing meeting, build a Decision owner map for your top AI-assisted workflows: who commits, who reviews, who can override.

4–5 yes. Pause new rollouts. Name commit, review, and override on the worst handoff before you invent more interfaces.

The instinct after a scene like the conference is to empower more people so work does not bottleneck. Empowerment without a judgment map redistributes ambiguity. Clarity of who has the judgment to decide comes first. Then empowerment reduces debt instead of compounding it.

More interfaces are not the same as more decisions. The Decision owner map is the thin fix: one page per recurring AI-assisted workflow, three names, no theater. In Knowledge as Code terms, that is System-layer governance for the handoff: the fields have to exist before the next tool can claim to help.

Which handoff on your team has no owner, and who pretends that is fine?

Madam I’m Adam

This continues the thread from Agent Sprawl as an Organizational Risk, where unmanaged proliferation was the inventory failure. Coordination Debt names what that proliferation costs in meetings, stalls, and orphaned outputs before anyone reaches a decision.