When async breaks down and a meeting is the right call. A structured path from document to room — with clear triggers at every step.
ED3 is not anti-meeting. It's anti-unnecessary-meeting. The goal is not to eliminate every synchronous conversation — it's to make sure that when a meeting does happen, it has earned its place. The Escalation Ladder gives teams a structured path from async to sync, with clear triggers at each step. If the decision can be resolved in writing, it stays in writing. If it can't, the ladder tells you exactly when — and how — to convene a room.
Without an escalation path, teams fall into one of two failure modes. The first: they default to meetings for everything, because calling a meeting feels productive. The second: they force async when it's clearly not working, letting decisions stall in unresolved comment threads. The ladder prevents both. It gives teams permission to meet — but only after they've exhausted the faster, quieter alternatives.
"The meeting you call after async fails is the most productive meeting you'll ever run — because everyone already knows what's at stake."
The Escalation Ladder bridges Level 3 (ED3 Sync) and Level 4 (ED3 Async). At Level 3, your meetings are good — they have decisions, owners, and agendas. At Level 4, most decisions don't need meetings at all. The ladder is the mechanism that lets teams operate at Level 4 by default while preserving a clean, guilt-free path back to sync when the situation demands it.
The key insight: escalation is not failure. An async proposal that surfaces a genuine disagreement has done its job — it identified exactly where the real tension lives. The meeting that follows isn't starting from scratch. It's starting from a well-defined conflict with documented positions. That's not a meeting about a topic. That's a meeting about a specific unresolved question. The best kind.
Start at Rung 1. Move up only when the current rung can't resolve the decision. Most decisions never make it past Rung 2.
Owner decides alone
The simplest path. The decision is within the owner's authority, the options are clear, and no one else's input is needed. The owner makes the call, records it, and announces it. No circulation, no review window. This covers more decisions than most teams realize — if the owner has been properly empowered.
Escalate when: The decision affects other teams, involves significant budget, or the owner genuinely needs input to make a good call.
Async review
The owner writes a proposal and circulates it using the Async Review Protocol. Reviewers respond in writing within the review window. If there are no blocks, the decision is made. If blocks are raised but can be resolved in writing (a revised proposal, a clarifying question, a concession), resolve them async and close it out.
Escalate when: A block can't be resolved in writing — the blocker and the owner have fundamentally different views that need real-time exploration.
Targeted sync — owner + blocker(s) only
A short, focused call between the decision owner and the specific person(s) who blocked the proposal. Not a full meeting — a direct conversation to resolve the specific disagreement. The agenda is already defined: "You blocked the proposal for [reason]. Let's resolve this." Come in with the proposal as context. Leave with either a resolution or a revised proposal to re-circulate.
Escalate when: The disagreement is broader than two people — it involves tradeoffs that require input from the full stakeholder group, or the decision has political weight that demands visible deliberation.
Full decision meeting
The last resort — and the most productive meeting you'll have. By the time you reach Rung 4, everyone has read the proposal, positions are documented, and the specific point of disagreement is clear. The meeting is not about context or options — it's about resolving one defined conflict. Use the Decision Brief. Use the ED3 Meeting Invitation. Apply all six principles. And end with a decision on the record.
After the meeting: Log the decision, announce the outcome, and update the original proposal. The async trail becomes the decision's permanent record.
These are the specific signals that tell you to move up a rung. If you're unsure whether to escalate, check this list. If none of these apply, stay where you are.
A block can't be resolved in writing. — The blocker and the owner have exchanged two rounds of written responses and the disagreement hasn't moved. Time to talk.
The comment thread is growing, not converging. — More than 3 people are weighing in and the positions are multiplying rather than narrowing. A room can converge faster than a thread.
The decision is time-sensitive and the review window is too slow. — Something changed and the original deadline no longer works. Call a meeting for today, but send the proposal as the pre-read anyway.
There's emotional weight that text can't carry. — A decision that affects people's roles, a contentious reorg, or a high-stakes bet where people need to be heard, not just read. These are rare — but they're real.
Silence is suspicious, not consenting. — Key stakeholders haven't responded and you suspect it's avoidance, not agreement. Reach out directly. If that doesn't work, bring them into a room.
The ladder only works if teams resist the temptation to skip rungs. These are the most common ways teams bypass the protocol — and why each one is expensive.
Jumping straight to Rung 4. — "Let's just get everyone in a room." This skips the writing, skips the structured input, and produces the same unfocused meeting the protocol was designed to prevent. The room has no pre-read, no defined disagreement, and no proposal to evaluate.
Staying stuck at Rung 2. — The comment thread is 30 messages deep and no one will escalate because "we should be able to figure this out async." Async is a tool, not a religion. If it's not converging, escalate.
Skipping Rung 3. — Going from a broad async review straight to a full meeting, when the disagreement is actually between two people. A 15-minute call between the owner and the blocker would have resolved it without pulling six others into a room.
"This adds friction to calling a meeting." — Yes. That's the point. Meetings should have friction. The current system makes it frictionless to consume other people's time — and that's the most expensive process failure in modern organizations.
"Sometimes you just need to talk it out." — Sometimes you do. And the ladder says exactly when: when async has been tried and the specific point of disagreement is clear. "Just talk it out" without that foundation is how you get 60-minute meetings that produce another meeting.
"This is too formal for our culture." — The ladder isn't bureaucracy — it's a mental model. You don't need to announce "I'm on Rung 2." You need to ask yourself: "Can I resolve this in writing? If not, who specifically do I need to talk to?" That's all the ladder is.
Download the ladder
The complete Escalation Ladder — four rungs, trigger conditions, and anti-patterns. Print it, pin it, or paste it into your team wiki.