Coordination tax
The hidden cost that kills execution — and how to eliminate it.
Most organizations don’t fail because of bad strategy or weak talent. They fail because reality outpaces the plan, and no one notices until it’s too late. Decisions happen in meetings, work happens in tools, and somewhere in the gap between the two, the shared picture of what’s actually going on quietly falls apart. Managers end up filling that gap — chasing updates, reconciling versions, re-explaining things that were already decided — doing coordination work instead of the work that actually matters.
That invisible work is the coordination tax.
It doesn’t show up on a P&L, but it consumes nearly half of every manager’s week. Meetings become about reassurance, not decisions. Plans become theater. Progress depends less on execution and more on whether everyone still believes the same story.
Meetings vanish
Decisions get made, commitments are given, risks are raised — then nothing gets written down. By next week, no one remembers.
Notes don't become plans
Someone takes notes. They sit in a doc no one reads. The plan never updates. The same questions come up again next meeting.
Manual updates burn time
Status meetings, update emails, slide decks — keeping everyone aligned takes more effort than the actual work.
The evidence
This isn't a theory. It's measurable.
58%
of the workday goes to “work about work” — status updates, searching for information, and switching between tools.
Asana · Anatomy of Work Index, 2022
103h
lost per employee per year to unnecessary meetings. 71% of senior managers say meetings are unproductive and inefficient.
Asana · Anatomy of Work, 2021 & HBR · Stop the Meeting Madness, 2017
37%
of employee time is spent in meetings making decisions — and more than half of that time is considered ineffective.
McKinsey · Decision making in the age of urgency, 2019
1.9×
higher cost and schedule overruns on projects with poor alignment. Misaligned teams waste $1M for every $1B spent.
PMI · Pulse of the Profession, 2021
Why it compounds
The tax grows with every layer.
One person
You leave a meeting with five things to update — your plan, your task tool, a shared doc, a Slack thread, and your manager's dashboard. You do three. Two drift. Nobody notices until it's a problem.
One team
Eight people in a standup. Decisions happen verbally. Someone writes half of it down. By Thursday, two people think the priority changed. One doesn't know. The plan says something else entirely.
Multiple teams
Now multiply it. Product decides to deprioritize a feature. Engineering doesn't hear until sprint planning. Sales already promised it to a customer. Finance budgeted for it. Everyone is executing a different version of reality.
The coordination tax isn't a people problem. It's a systems problem. People can't maintain a shared reality across that many moving parts. They were never supposed to.
The shift
From tax to layer.
The coordination tax exists because coordination was never designed into the system. It’s a side effect — something people do on top of the actual work, using tools that were built for something else.
Project management tools were built for the manager, not for the system. They’re reporting interfaces: you go to the tool, you type in what happened, and the tool displays it. But the tool doesn’t know what happened. It only knows what someone remembered to enter. The moment a meeting ends and no one updates the board, the tool starts lying.
The fix isn’t another project management tool. It’s a coordination layer — something that sits underneath your existing tools and meetings, and keeps the shared picture of reality current automatically.
The hidden data layer
Meetings are the most consequential data system in your organization. And none of it flows anywhere.
Consider what actually happens in meetings. A VP says “we’re pulling budget from initiative A.” A tech lead says “that timeline is unrealistic, we need three more sprints.” A product manager commits to delivering a scope review by Friday. A customer-facing team raises a risk that no one has written down yet.
These are the most consequential moments of information exchange in any organization. Decisions get made. Priorities shift. Commitments form. Risks surface. Ownership changes hands — verbally, in real time.
And then the meeting ends. Someone writes a rough summary in a shared doc. Maybe half the action items land in a task tool. The decisions themselves? They exist in the memory of whoever was paying attention. Within 48 hours, the memory starts to fragment. Within a week, different people remember different versions.
Organizations are running on a massive, invisible data layer that exists only in human memory. No system of record. No query interface. No audit trail. Just people trying to remember what was said.
This isn’t a meeting problem. It’s an information architecture problem. Every organization has two information systems: the formal one (tools, documents, dashboards) and the real one (meetings, conversations, Slack threads). The formal system is structured, queryable, and mostly out of date. The real system is current, rich, and completely inaccessible.
The coordination tax is what people pay to bridge that gap — manually translating from the real system into the formal one, over and over, every day.
Architecture
What a coordination layer actually is.
A coordination layer is infrastructure, not an application. Think of it like TCP/IP — it doesn’t replace the applications above it. It sits underneath them and makes them work together. Your meetings still happen. Your tools still exist. The coordination layer connects them.
A coordination layer does six things:
Listens
Joins every meeting as a passive observer. Captures the full conversation — not just what someone chose to write down.
Extracts
Identifies structured signals from unstructured conversation: decisions, commitments, ownership assignments, risks, priority changes, dependencies.
Maintains state
Keeps a continuously updated model of what’s actually true — not what someone last entered into a tool, but what was last said, decided, and committed to.
Propagates
Pushes changes to connected tools automatically. When a decision is made in a meeting, the task board, the plan, and the stakeholder view all update. No human relay required.
Detects drift
Compares what was planned against what’s actually happening. Flags divergence in real time, not at the next review meeting.
Recalculates
Adjusts priorities and surfaces implications based on new information. When something changes, the system understands what else is affected.
The primary input is conversation, not data entry. It doesn’t wait for someone to type something into a form. It listens to what’s already happening, structures it, and acts on it. The coordination layer meets the organization where it already operates — in meetings.
The structural gap
Why your PM tool can’t be the coordination layer.
The first instinct is always: “Can’t we just get better at updating our existing tools?” The answer is no — not because people are lazy, but because the tools are architecturally wrong for this job.
Every project management tool — Jira, Asana, Monday, Linear, Notion — operates on the same fundamental model: a human writes data into the tool, and the tool displays it. The tool is a database with a user interface. It knows exactly what was entered, and nothing else.
A coordination layer operates on a fundamentally different model: the system listens to what’s happening and updates itself. The input isn’t a form field. It’s a conversation.
Project management tools
- Write-first: Humans update the tool
- Point-in-time state: Shows what someone last entered
- Single-source: One tool, one view of reality
- Static: The tool waits for you to tell it something changed
- No memory: Doesn’t know why anything changed
Coordination layer
- Listen-first: The system updates itself from meetings
- Continuous state: Shows what’s actually true right now
- Multi-source: Meetings + tools + communications, unified
- Proactive: Detects drift and recalculates without being asked
- Full memory: Knows the decision, the context, and who was in the room
“Better discipline” never works. The problem isn’t that people won’t update their tools. It’s that the tools require a parallel manual process — listening, interpreting, translating, typing — that runs alongside the actual work. That parallel process is the coordination tax. No amount of process improvement makes it go away. Only a different architecture can.
The compound effect
A layer that gets smarter the more you use it.
What separates a coordination layer from a notetaker or meeting summarizer: it accumulates.
A typical AI notetaker gives you a summary of today’s meeting. Tomorrow, it gives you another summary. There’s no connection between the two. No memory. No arc. Each meeting is an island.
A coordination layer builds a growing model of your organization’s execution state. Every meeting adds to it. Over time, the system accumulates:
Decision history across scopes
Not just “what was decided today” but the full chain of how priorities evolved, who changed what, and why. A queryable institutional memory.
Behavioral patterns
Which commitments always slip. Which meetings consistently produce decisions versus which are performative. Where the real dependencies live versus where the org chart says they should.
Cross-scope visibility
Dependencies and conflicts that no single person can see. When Team A’s decision affects Team B’s timeline, the layer knows — even if no one in Team B was in the meeting.
Predictive signals
Enough accumulated context to move from reactive (“this drifted”) to predictive (“based on the pattern, this is about to drift”). The system starts seeing problems before people do.
Organizational continuity
Knowledge that persists beyond any individual’s tenure. When someone leaves, the decisions they made, the context they held, and the commitments they owned don’t leave with them.
A coordination layer doesn’t just save time. It builds an asset. Every meeting that flows through makes the system’s model of reality more accurate and more predictive. The organization gets smarter at coordinating — structurally, not just behaviorally.
The trajectory
Layer → memory → intelligence.
Once you have a coordination layer that listens, extracts, and accumulates, something else becomes possible: execution intelligence. Not dashboards that show you what happened. Intelligence that tells you what’s about to happen, and what to do about it.
1
Capture
The AI notetaker joins meetings and captures decisions, commitments, and ownership.
Free
2
Coordination
Captured signals update the living plan. Drift detection, priority recalculation, tool sync.
Living Plan
3
Intelligence
Enough accumulated context to predict, advise, and generate. Stakeholder reports, risk models, decision velocity.
Coming soon
Each stage requires the one before it. You can’t have intelligence without memory. You can’t have memory without capture. And you can’t have reliable capture without a system that listens to meetings — the place where the real information actually lives.
In Parallel starts with a free AI notetaker. The notetaking isn’t the product — listening is the foundation of the entire coordination layer. Every meeting that flows through makes the layer more accurate and more useful.
The result
In Parallel is the coordination layer.
It joins your meetings. It listens. It captures every decision, ownership change, and commitment. Then it updates your plan and pushes changes to your connected tools — automatically.
Nobody writes a status report. Nobody chases anyone for updates. The plan is current, the tools are in sync, and everyone sees the same thing.
Get the full picture
How the best teams run. What breaks at scale. One email per week.
By subscribing you agree to our Privacy Policy. Unsubscribe anytime.
Stop paying the tax.
See how In Parallel turns coordination from overhead into advantage. 30-minute demo.