The Coordination Tax Index
What is the coordination tax?
Every knowledge-work team pays it. Most teams can't name it. The coordination tax is the cumulative cost of keeping people aligned — the meetings that could have been a decision, the context you re-explain to every latecomer, the hour you spend searching for something that was agreed three weeks ago.
The definition
Three things. One tax.
The coordination tax has three components. They compound. Each one is, on its own, a manageable nuisance. Together, they account for nearly a fifth of a typical knowledge worker's week.
Status and sync meetings
Standups, project reviews, all-hands catch-ups where the primary purpose is transferring state that should already be shared. The meeting isn't doing creative or decision-making work — it's correcting for a gap in shared context.
Re-explaining context
Every time someone new joins a project, every time you ask your AI assistant a question it should already know the answer to, every time you brief a colleague on a decision that was made in a meeting they missed. Re-explaining context isn't work — it's a tax on having done work before.
Hunting for past decisions
Searching Slack, email, meeting notes, Confluence, Notion, and four other tools for something that was definitely decided somewhere. The more tools a team uses, the worse this gets. The longer the team has existed, the worse this gets. The higher the turnover, the worse this gets.
The calculator
Calculate your team's coordination tax
Adjust the sliders to match your team's reality. The annual cost figure uses salary cost only — it excludes the harder-to-quantify losses: slower decisions, frustrated senior hires, and the opportunity cost of good ideas that never got captured.
Coordination Tax Calculator
How much is your team paying?
Hours per person / week
Your coordination tax
Industry average: 19% · Source: In Parallel Coordination Tax Index 2026
Benchmark based on In Parallel's 2026 Coordination Tax Index baseline study. Hourly rate derived from annual salary ÷ 2,080 working hours. Results are estimates — your actual tax depends on team structure, tooling, and culture.
The compounding problem
Why the coordination tax is rising
More tools, more context gaps
The average knowledge worker uses 9–12 SaaS tools daily. Each new tool creates a new silo. Decisions made in Slack don't surface in Notion. Meeting notes in Teams don't connect to the project plan in Linear. Every tool added to the stack adds surface area for context to disappear into.
Remote work removed the ambient context layer
In an office, you passively absorb context: the conversation across the room, the whiteboard from yesterday's session, the fact that two colleagues have been in a room together for two hours. Remote and hybrid teams lost this ambient layer. Nothing replaced it — which means every piece of context now requires an explicit, effortful transfer.
AI tools are stateless by default
Every AI assistant your team uses starts each conversation knowing nothing about your organisation, your decisions, or your context. The result: a new category of coordination tax. You brief your AI the same way you brief a contractor who just started. Every session. Every person. Every tool.
Eliminating it
The coordination tax has a structural cause. It needs a structural fix.
Reducing the coordination tax requires making context persistent, searchable, and automatically available — to your team, and to the AI tools they use.
That means three things working together:
- 1.
Automatic capture — context should be captured where work happens, not manually transferred after the fact. Meeting decisions, action items, and project updates should flow into shared memory without anyone having to do it.
- 2.
Shared access — context shouldn't live in one person's notes. It should be available to everyone on the team, at the level of permission that's appropriate.
- 3.
AI connectivity via MCP — every AI tool your team uses should be able to query the shared context layer directly. That's what the Model Context Protocol enables: a standard interface so AI tools can ask "what do we know about this project?" and get a real answer.
Methodology
About the Coordination Tax Index
The 2026 Coordination Tax Index baseline is derived from In Parallel's analysis of meeting patterns, time-tracking data, and team survey responses collected from knowledge workers across Europe between January and June 2026.
The benchmark figure (7.7 hours/week, approximately 400 hours/year) represents the median across respondents when asked to estimate time spent on status meetings, context re-explanation, and information retrieval for past decisions.
The index will be expanded with quantitative survey data from a structured study of 200–300 knowledge workers across job functions, company sizes, and industries. Results will be published as an annual benchmark. If you'd like to contribute to the next edition or access the full dataset, contact us.
research@in-parallel.com →Frequently asked
Questions about the coordination tax
Is the coordination tax the same as meeting overload?
Partly. Status and sync meetings are one component, but the coordination tax includes time that doesn't appear in calendars: the hour searching for a decision in old Slack threads, the ten minutes at the start of every AI chat re-explaining the project. Reducing meeting load helps — but it doesn't eliminate the other two components.
Does better documentation fix it?
Documentation helps with information retrieval but doesn't reduce the upkeep cost. If documentation requires manual effort to maintain — and it almost always does — it becomes a tax on top of a tax. Teams stop maintaining it. It rots. Then you're back to searching.
Why is the coordination tax relevant to AI adoption?
Every AI assistant your team adds starts with zero context about your organisation. Teams are essentially training a new contractor on every chat session. Until AI tools can access shared organisational context — via standards like MCP — adding AI to the stack increases the coordination tax before it reduces it.