The Coordination Tax: Why Your Team Spends More Time Catching Up Than Moving Forward
Most team slowdowns aren't caused by slow work — they're caused by the invisible cost of keeping everyone informed. Here's how to diagnose and cut it.
Picture Monday's standup. Eight people on the call, twenty-five minutes blocked. The intention is simple: a quick touch-base before everyone goes heads-down. Instead, the first ten minutes are someone asking "wait, when did that change?", followed by another five of "I thought we decided differently last week", then a detour to find the right document, then a promise to "follow up async."
Nobody wasted that time on purpose. And nobody logged it anywhere.
That's what makes coordination overhead so costly: it doesn't appear in your sprint board, your project tracker, or your time-tracking tool. It shows up instead in the Slack thread that should have been a document, the ad hoc call that should have been a shared status, the context-setting that gets repeated to every person who wasn't in the original conversation.
According to Asana's Anatomy of Work Index, 60% of a knowledge worker's day is spent on "work about work" — coordination, communication, and status-chasing — rather than skilled output. Across a year, that amounts to 352 hours per person just talking about work rather than doing it.
Most teams feel the weight of this without being able to name it. This article gives it a name — and a way to reduce it.
- What coordination overhead actually is
- Where the tax hits hardest
- Why it never shows up on any dashboard
- The compounding effect: what it costs at team scale
- How to audit and reduce your coordination overhead
- Frequently asked questions
What coordination overhead actually is
Coordination overhead is the time your team spends keeping each other synchronized — and it's broader than your meeting schedule.
It includes:
- The Slack message asking "what's the status on X?" that triggers a ten-message thread
- The call booked because a document wasn't findable
- The repeated context-setting every time someone new joins a project
- The "quick question" that takes thirty minutes to answer properly
- The Friday afternoon update email that gets written because nobody checked the tracker
Individually, none of these feel significant. Collectively, they're where most of your team's coordination budget goes — and unlike meetings, they're largely invisible to anyone reviewing calendars or sprint boards.
The core problem is information lag: there's a gap between when something happens or gets decided and when everyone who needs to know actually finds out. Coordination overhead is what teams do to close that gap manually. Every workaround — a ping, a call, a catch-up meeting — is evidence of an information gap that wasn't closed automatically.
This is worth distinguishing from "bad meetings" or "too many tools." Those are symptoms. Coordination overhead is the underlying condition.
Where the tax hits hardest
Not all coordination overhead is equal. Four patterns generate the majority of it on most teams:
- Project handoffs. When work moves between people or teams, context rarely travels with it. The receiving end has to reconstruct it — through questions, catch-up calls, or trial and error. Research shows this is often the single slowest part of any project: not the work itself, but the transition between stages.
- Decisions made in small groups. When three people align on something in a Zoom call, the other eight who need to act on it still need to find out. Documentation is the exception; re-broadcasting is the rule.
- Async information gaps. In remote and hybrid teams, people naturally fall out of sync. Without a reliable way to surface what changed while someone was offline, the default is asking someone — which costs both parties' attention.
- Unclear ownership. When it's not obvious who holds context on a given topic, everyone becomes a coordination bottleneck for someone else.
The table below shows how each pattern tends to manifest — and what a lower-overhead alternative looks like:
| Pattern | High-overhead behavior | Lower-overhead alternative |
|---|---|---|
| Project handoffs | Handoff call + follow-up questions | Shared context updated automatically at each stage transition |
| Decisions in small groups | Re-broadcast via chat, separate briefings | Decision logged with rationale and tagged stakeholders |
| Async information gaps | "Catch me up" messages, ad hoc calls | Digest of changes surfaced in existing channels automatically |
| Unclear ownership | Thread of "who knows about X?" pings | Explicit project ownership visible at a glance |
Why it never shows up on any dashboard
The reason coordination overhead accumulates so reliably is that it's structurally hard to observe. Meetings get logged. Tasks get tracked. But the ambient layer — the three-minute "quick check" that cost twenty minutes of context recovery afterward, the Slack thread that branched into two separate conversations — doesn't appear on any report.
Atlassian's survey of 12,000 knowledge workers found that teams waste 25% of their time just searching for answers. That's one full workday out of four spent trying to locate information that should already be accessible.
Microsoft's Work Trend Index adds texture to this: 57% of meetings are ad hoc — unscheduled, unlogged, called because someone needed an answer and couldn't find it another way. Employees are interrupted roughly every two minutes during peak working hours.
The coordination tax doesn't show up on any dashboard. It shows up in the tired faces at the end of a "busy" week where nobody can quite explain what they were so busy doing.
This invisibility is itself the problem. What you can't see, you can't manage. Teams end up optimizing meeting hygiene — shorter standups, better agendas — while the real overhead continues in the spaces between scheduled events.
The compounding effect: what it costs at team scale
Individual overhead feels tolerable. At team scale, it becomes a structural drag.
Consider an eight-person team where each person loses 90 minutes daily to coordination overhead: catch-up threads, status questions, repeated briefings. That's 12 hours per day — effectively one and a half full-time roles consumed entirely by synchronization work.
The problem compounds through cognitive cost too. Coordination work doesn't just consume time; it consumes attention. Switching into a status question and back out of deep work carries a recovery cost — often five to twenty minutes before focus is fully restored. A brief interruption isn't free; it resets the clock.
This is why 48% of employees in Microsoft's research described their work as feeling "chaotic and fragmented." The problem isn't a lack of intelligence or effort — it's that every individual is operating with slightly out-of-date information, and compensating through constant re-synchronization.
The deeper issue is that coordination overhead scales with team size. A solo contributor has no coordination tax. A two-person team has minimal overhead. By the time a team reaches eight to twelve people, the total number of information flows to manage grows faster than the team's capacity to manage them manually.
And yet most teams add tools and processes without ever auditing the synchronization layer underneath.
How to audit and reduce your coordination overhead
The goal isn't to eliminate coordination — it's to make information flow automatically where it can, so human attention is reserved for things that actually require judgment.
Start with a diagnostic pass.
Four questions to locate your overhead
- What questions does your team ask repeatedly? If "what's the status on X?" appears more than twice a week in any channel, the status isn't self-serve.
- When someone joins a project late, what do they do? If the answer is "they book a call with whoever's been on it longest," you're paying a briefing tax every time.
- Where do decisions live after they're made? If the honest answer is "in the head of whoever was in the meeting," expect those decisions to be revisited — repeatedly.
- How long after a significant update does it take for everyone who needs to know to find out? If the answer is "it depends on who happens to check Slack that day," you have an async information gap.
Three ways to reduce it
Separate push from pull. Some information needs to be actively pushed to specific people. Most information can be made pull-accessible — findable on demand, without someone needing to relay it. The question is: where are you pushing information that could just as easily be searchable?
Surface status automatically. The "what's the status on X?" ping is a failure mode, not a communication style. If project status is updated automatically from team conversations and commitments — rather than requiring someone to write a status report — the question becomes unnecessary.
Make context self-serve at onboarding points. Every time a project gains a new stakeholder or a team member returns after absence, there's a briefing cost. Reducing that cost means ensuring context — decisions made, blockers cleared, direction set — is accessible without requiring a dedicated call. Context loss is the root cause of most unexpected rework; preventing it at transition points is the highest-leverage place to start.
Quick-start coordination audit checklist
- List the five most frequent "quick questions" your team asks each other in Slack or chat
- Identify which of these questions has a findable, written answer somewhere — and which doesn't
- Find your last three major project decisions. Where are they documented? Can a team member find them without asking?
- Count your unscheduled calls from the last two weeks. What triggered each one?
- Ask two or three team members: "How do you currently find out about significant project changes?" If their answer is "someone tells me," that's your gap.
The shift that matters
Most productivity work focuses on the visible layer: meeting hygiene, task management, time blocking. The coordination tax lives beneath that — in the informal, unlogged work of keeping everyone synchronized.
The teams that reduce it most effectively don't do so by working harder at coordination. They reduce the coordination surface itself — by making information flow automatically, by documenting decisions where they're made, by treating "someone needs to be briefed" as a design flaw rather than a normal cost of doing business.
Good tooling earns its place here precisely because the problem is structural. When project updates surface in the channels where work is already happening, the catch-up call becomes unnecessary — not because people communicate better, but because they don't have to.
Frequently asked questions
What's the difference between coordination overhead and meeting overhead?
Meeting overhead is one component of coordination overhead. The broader term includes all the informal synchronization work that happens outside of scheduled meetings: Slack threads, ad hoc calls, repeated status questions, and context-setting conversations. Many teams optimize their meetings while leaving the informal coordination layer untouched — and that's where most of the overhead actually lives.
How much coordination overhead is normal?
Some coordination is inevitable and valuable — teams need shared context to make good decisions. A rough benchmark: if less than 50% of a knowledge worker's day is available for focused, skilled work, the coordination layer is likely too thick. Asana's research suggests the average team is already there, with 60% of time consumed by work about work. The target isn't zero; it's moving more of that 60% to the pull-accessible, automatic layer rather than the manual, reactive one.
How do you measure coordination overhead?
Precisely is hard. Directionally is easier: track the volume of ad hoc messages and calls in a given week, run a brief survey asking team members how much time they spend catching up versus making progress, and count repeated questions in team channels. The goal isn't a perfect number — it's identifying the highest-friction coordination patterns so you can address them specifically.
Is this just a remote work problem?
No — though it's more visible in remote and hybrid settings. Co-located teams have their own coordination overhead; it often manifests as shoulder-taps, impromptu hallway conversations, and interruptions that don't get counted. The root cause is the same in both contexts: information doesn't flow automatically, so people fill the gap manually.