The Coordination Tax: Why Teams Lose More to Talking About Work Than Doing It
What is the coordination tax?
The coordination tax is the time and attention a team spends keeping work aligned instead of doing the work itself. It's the "any update?" pings, the status meeting that exists to sync everyone, the half-hour spent hunting for a doc that already exists, the message you send three times before someone replies. None of it is the work. All of it is the cost of doing the work together.
Every team pays it. Most never measure it. And because it's spread across everyone's day in five-minute increments, it hides in plain sight—it never shows up as a line item, so no one owns reducing it.
Why it scales faster than headcount
Here's the uncomfortable math. Work doesn't scale with the number of people; coordination scales with the number of connections between them. Add a tenth person to a team of nine and you haven't added one more relationship—you've added nine. The communication paths grow roughly with the square of team size.
So a team that doubles in size doesn't double its coordination overhead. It more than quadruples the ways information has to travel, the hand-offs that can drop, and the people who need to be kept in the loop. This is why teams often feel slower right after they grow: the new capacity gets eaten by the new coordination tax before it ever reaches the work.
Where the tax actually gets paid
- Chasing. Messages whose only purpose is to nudge work forward—"any update?", "did you see this?", "still waiting on X."
- Context-hunting. Re-reading threads, digging through docs, and re-asking for information that already exists somewhere.
- Status syncs. Meetings that exist mostly so everyone can find out what everyone else is doing.
- Hand-off friction. The work is 80% done by a tool or a teammate, and someone spends real time stitching the last 20% across the gap.
- Waiting. Approvals, reviews, time zones—work sitting idle in a queue no one is actively watching.
Why AI hasn't fixed it (yet)
The hope was that AI would absorb this overhead. Mostly, it has relocated it. Individual tasks get faster, but the coordination work doesn't disappear—it moves into the seams between your tools, where it's even harder to see. We've written about how this accumulates as [AI workflow debt](/blogs/ai-workflow-debt), and why AI speed-ups so often fail to show up at the team level in [how much time AI really saves](/blogs/ai-productivity-truth-time-savings).
The pattern is consistent: AI makes individuals faster, but teams still move at the speed of their coordination. Until the coordination layer itself is automated, the tax stays on the books.
How to shrink the coordination tax
- Measure it first. For one week, count the time that isn't the work: status meetings, nudge messages, context searches, idle waiting. Naming the number is what makes it a priority.
- Make context travel with the request. When the background arrives with the ask, no one has to reconstruct the story before they can act—most re-asking simply disappears.
- Route to the owner, not the room. Decisions should reach whoever actually owns them, with enough context to answer quickly, instead of being broadcast to everyone.
- Make waiting visible. Treat silence as a state to follow up on, not a success. Work shouldn't stall quietly in an inbox.
- Automate the chasing. The follow-ups and status-nudging are routine and rules-based—exactly the kind of coordination that shouldn't need a human at all.
Coordination should be infrastructure, not everyone's side job
Right now, coordination is a tax every person on the team pays out of their own attention. It doesn't have to be. The teams that pull ahead treat coordination as something the system handles—context that moves on its own, decisions that reach the right person, follow-ups that happen without anyone remembering to send them.
That's exactly what we're building at Alknoma: a coordination layer that automates how teams communicate and align, so the tax shrinks and the work gets the attention instead. If your team feels slower than its size should allow, the coordination tax is usually where the time went—and it's the problem we'd love to take off your plate.
Deciding between an autonomous agent and a coordination layer? We compare the two approaches in [AI coworkers vs coordination layers](/blogs/ai-coworkers-vs-coordination-layers).
Frequently asked questions
- What is the coordination tax?
- The coordination tax is the share of a team's time and attention spent keeping work aligned rather than doing the work itself: chasing updates, hunting for context, status meetings, hand-offs, and waiting on replies. It's the overhead of working together, and it's paid by everyone, every day.
- Why does the coordination tax grow as teams scale?
- Because communication paths grow faster than headcount. Add people and the number of connections between them rises roughly with the square of team size, so every new hire adds more coordination than the last. A team twice the size doesn't have twice the overhead—it has far more.
- Hasn't AI reduced the coordination tax?
- Not yet—mostly it relocates it. AI speeds up individual tasks, but the chasing, context-hunting, and follow-ups move into the seams between tools, where they're harder to see. Unless the coordination layer itself is automated, individual speed-ups get absorbed by overhead.
- How do you measure the coordination tax?
- Track where time goes that isn't the work: hours in status/update meetings, messages sent purely to nudge or ask for status, time spent searching for context that already exists, and idle time waiting on a reply or approval. Most teams are surprised how much of the week this adds up to.
- How can a team reduce the coordination tax?
- Make context travel with the request instead of being chased, route decisions to the specific owner rather than broadcasting, make waiting visible so nothing stalls silently, and automate the routine chasing and follow-ups. The goal is to spend less attention on aligning work and more on doing it.
Keep reading
AI Workflow Debt: The Hidden Tax Slowing Your Team Down
AI workflow debt is the accumulated drag of half-finished automations, brittle prompt chains, and tools that don't talk to each other. Like technical debt, it compounds quietly—until coordination, not capability, becomes the bottleneck. Here's how to recognise it and pay it down.
AI Coworkers vs Coordination Layers: Two Very Different Bets on Team AI
Most AI-for-teams products make one of two bets: build an AI coworker that does the work like an extra headcount, or build a coordination layer that automates how work moves between the people you already have. They solve different problems. Here's how to tell which one your team actually needs.
The Gap Between Individual AI Gains and Team Performance
AI can make one person faster very quickly. It does not automatically make the team move faster. The bottleneck usually isn't the writing — it's the coordination around the work.