The Coordination Stack: Why Coordination Problems Are Almost Never Communication Problems
- May 8
- 6 min read
A team has a coordination problem. Deadlines slip. Handoffs get fumbled. The same issue gets discussed in three different meetings, and somehow no one is sure where it landed. The reflex, in almost every organization, is the same: we need to communicate better.
So the team adds a standup. Then a Slack channel. Then a weekly sync. Then a project review. Then a status update template. Then a follow-up to the status update. Communication volume goes up. Coordination doesn't.
The reason is structural. The team didn't actually have a communication problem. It had a coordination problem — and coordination is not the same thing as communication.
The Coordination Stack™ is the Work Management Institute's framework for understanding what coordination really is, where it actually happens, and why most attempts to fix it miss the layer where it's broken.
What Coordination Actually Is
The Work Management Institute defines coordination as:
The act of aligning people, timing, responsibilities, and execution so work moves toward the intended outcome without confusion, delay, or drift.
Coordination is not collaboration. Collaboration is social — people working together toward a shared goal. Coordination is systemic — the alignment that lets that work integrate cleanly across people, teams, and time.
A team can collaborate constantly and still be poorly coordinated. They can communicate all day and still produce duplicated work, missed handoffs, conflicting priorities, and quiet drift. Communication is one input into coordination. It is not coordination itself.
This is the misdiagnosis the Coordination Stack exists to correct.
The Five Layers
Coordination doesn't happen in one place. It happens across five distinct layers — each answering a different question about how work moves. The Coordination Stack names them as Why, What, Who, When, and How.
When all five are clear, work flows. When any one is weak, the others have to compensate — and that compensation almost always shows up as friction somewhere else.
1. Why — Purpose & Intent
Why does this work exist? What outcome is it meant to achieve?
The Why layer establishes purpose. It includes desired outcomes, success criteria, strategic intent, and the underlying problem the work is trying to solve.
When the Why is weak, teams stay busy but optimize for the wrong goal. Work gets done, hours get logged, deliverables ship — and the value erodes anyway because the effort was never connected to a clear outcome. Misdiagnosis: "We need better prioritization." Real issue: no one ever defined what success would look like.
2. What — Work Definition & Scope
What exactly needs to be done? What does "done" actually mean?
The What layer translates intent into clearly defined work — tasks, deliverables, scope boundaries, acceptance criteria, definitions of done.
When the What is weak, every contributor interprets the work differently. Two people build the same thing in two different ways. Reviewers reject deliverables on criteria the builders never knew about. Misdiagnosis: "We have a quality problem." Real issue: no one agreed on what the work was.
3. Who — Ownership & Responsibility
Who owns the work? Who contributes? Who decides?
The Who layer establishes accountability — owners, assignees, decision-makers, reviewers, contributors. It answers a deceptively simple question: when the work needs to move forward, whose name is on it?
When the Who is weak, responsibility diffuses. Everyone assumes someone else is handling it. Decisions stall because no one has authority. Work sits in queues that have no owner. Misdiagnosis: "Our team isn't proactive." Real issue: the architecture never assigned ownership in the first place.
4. When — Timing & Dependencies
By when does this need to happen? In what order? What depends on what?
The When layer governs the flow of work over time — deadlines, milestones, dependencies, sequencing, cadence. It is the temporal architecture of the work.
When the When is weak, work becomes reactive. Teams discover dependencies the day they block them. Sequencing happens in retrospect rather than design. Commitments slip because timing was never coordinated, only assumed. Misdiagnosis: "We have a delivery problem." Real issue: no one ever sequenced the work.
5. How — Execution & Alignment
How is the work carried out? How do people stay aligned as it progresses?
The How layer defines the execution environment — communication practices, collaboration norms, update cadences, decision protocols, the workflow itself. It is the connective tissue that keeps the other four layers aligned as work moves.
When the How is weak, even work with clear purpose, scope, ownership, and timing can still become chaotic in practice. People do the right work, on the right things, owned by the right people, on the right schedule — and still produce friction because the execution environment never got designed. Misdiagnosis: "Our culture is broken." Real issue: no one designed the operating rhythm.
The Compensation Principle
Here is the most useful single insight from the Coordination Stack:
When any one layer is weak, the other layers have to compensate — and that compensation almost always shows up as friction in a different layer.
A weak Why creates pressure on the What — teams try to define the work without knowing what it's for. A weak What creates pressure on the How — teams try to coordinate execution around something whose scope is undefined. A weak Who creates pressure across every other layer because there is no one to anchor decisions.
This is why coordination problems are so often misdiagnosed. The friction shows up where the compensation is happening, not where the break is. The team experiences the symptom — endless meetings, status thrash, vague Slack threads — and assumes the symptom is the disease. So they treat the symptom. And the disease keeps producing new symptoms.
The Coordination Stack reframes the diagnostic question. Instead of asking "where is the friction?", it asks "which of the five layers is forcing the others to compensate?" Those are not the same question — and they rarely have the same answer.
How to Use the Coordination Stack
The Stack is designed to be applied. Three common applications:
As a diagnostic. When something feels broken, walk a specific workflow or initiative through all five layers. Score each as Strong, Partial, or Missing. The pattern tells you where the structural break is — usually upstream of where the friction actually shows up.
As a design checklist. When kicking off new work, use the five layers as a launch gate. Before the work starts, the team should be able to answer all five questions in plain language. If any answer is vague, the work isn't ready to begin — it's ready to generate friction.
As a shared vocabulary. Once a team adopts the Stack, conversations change. "I think this is a Who problem, not a How problem." "We don't have a communication issue — we have a What issue." The vocabulary makes the diagnostic itself faster.
The Stack is most powerful as a habit, not an artifact. Used regularly, it changes the questions teams ask before they reach for another meeting.
Coordination vs. Collaboration: Why This Distinction Matters
Most modern work platforms — Slack, Teams, Zoom, email — are collaboration tools. They make it easier for people to interact. They do not, on their own, coordinate work.
This is one of the central observations behind WMI's positioning: organizations have over-invested in collaboration tools and under-engineered coordination structures. The result is teams that talk constantly and execute unevenly. They are richly collaborative and structurally uncoordinated.
The Coordination Stack is the architecture that closes that gap. It does not replace collaboration tools — it gives them something to actually coordinate around.
Where the Stack Sits in Work Management
The Coordination Stack is one of WMI's foundational frameworks within the broader discipline of Work Management. It connects directly to several other elements of the WMI body of knowledge:
The C4 Flywheel describes how Clarity, Coordination, and Completion compound across an organization, powered by Collaboration. The Coordination Stack defines what the Coordination in that flywheel actually consists of.
Workflow Architecture is the practice of intentionally designing how work flows. The Coordination Stack is the diagnostic that tells you whether a given workflow can actually be coordinated as designed.
The Coordination Maturity Model describes how organizations evolve from ad hoc coordination toward systematic, optimized, and ultimately autonomous coordination. The Stack provides the layers that maturity is measured across.
Together, these frameworks form a coherent architecture for diagnosing, designing, and improving how work actually moves through modern organizations.
The Bottom Line
Most coordination problems in modern organizations are not communication problems. They are structural — and they live in one of five places.
More meetings won't fix a workflow with no clear owner. More Slack won't fix a deliverable with no definition of done. More check-ins won't fix work whose purpose was never defined.
The Coordination Stack tells you where the actual break is. The work — the harder, more durable work — is fixing it there.
