This is the complete ED3 framework in a single document, structured for AI assistants to consume and operationalize. If someone gave you this link and said “help me implement this,” you now have everything you need.
ED3 is a structured methodology for fixing decision-making culture in organizations. The core premise: organizations don’t fail because of bad people or too many meetings. They fail because discussions consistently end without decisions, owners, or accountability. ED3 fixes this through six principles, four maturity levels, and a practical toolkit.
After reading this page, you should be able to:
Organizations move through four stages. Most are stuck at Level 1 and don’t know it.
Meetings exist for everything. Decisions happen in none of them. There is no record of who decided what, the same problems resurface monthly, and “let’s take this offline” is the standard meeting ending. People are busy. Nothing moves.
Signals you’re at Level 1:
Individual people start asking uncomfortable questions: “What are we actually deciding?” Pockets of improvement emerge — one team runs better meetings, one manager insists on owners. But there is no shared system. Champions burn out because the culture hasn’t shifted.
Signals you’re at Level 2:
The six principles become the norm. Every meeting has a named decision, every decision has one owner, agendas use committing verbs, delays are structured, silence is not mistaken for agreement, and status updates live in documents. Meetings still happen, but they produce decisions every time.
Signals you’re at Level 3:
Decisions live in writing. Most choices are made through async review protocols — proposals circulated, structured input collected, silence-means-consent deadlines enforced. Meetings happen only when async breaks down: unresolvable blocks, emotional weight, genuine ambiguity that requires dialogue. The organization barely meets, and moves faster because of it.
Signals you’re at Level 4:
These are the operating rules. Each one addresses a specific dysfunction.
Before scheduling, name the decision using a committing verb: decide, choose, approve, prioritize, select, commit. Not: discuss, review, align, explore, share, touch base, sync.
A real meeting purpose contains three elements: a committing verb, a finite scope (not a category — a specific decision), and a reason it matters now (what happens if it slips). If you cannot articulate these three things, the meeting has no reason to exist.
The default is one meeting, one decision. Multi-decision meetings (roadmap prioritization, hiring panels) are acceptable only when each decision is individually named, scoped, time-boxed, and owned. Zero unnamed decisions per meeting — that is the rule.
Verb swap reference:
| Instead of… | Write… |
|---|---|
| Discuss the Q4 roadmap | Decide which 3 initiatives to fund in Q4 |
| Review the marketing budget | Approve the $45K reallocation from brand to performance |
| Share customer feedback | (move to email or pre-read — not a meeting item) |
| Brainstorm feature ideas | (run async, then) Prioritize top 3 features for next sprint |
| Go over project status | (move to pre-read doc) |
| Talk about hiring plan | Decide whether to open 2 or 3 roles this quarter |
| Check in on launch timeline | Commit to a launch date and assign the go/no-go owner |
Not a team. One person. Shared ownership is diffused ownership, which produces diffused accountability. The owner decides (others advise), communicates the decision, and answers for outcomes.
Decision ownership roles:
| Role | What they do | What they don’t do |
|---|---|---|
| Owner | Makes the call. Communicates it. Answers for outcomes. | Delegate accountability. Seek consensus before deciding. |
| Advisor | Provides relevant input, expertise, or perspective when asked. | Block the decision. Require their input to proceed. |
| Executor | Carries out the decision once made. Surfaces blockers. | Relitigate the decision. Reopen without new information. |
| Informed | Receives the decision and adjusts accordingly. | Request justification. Treat notification as invitation to weigh in. |
Two owners is one too many. Co-ownership creates negotiation, not accountability. Being affected by a decision is not the same as being responsible for it.
Delay is a decision that must be structured with the same discipline as any other. A legitimate delay requires four elements:
Three types of delay:
“Let’s take this offline” is the most destructive deferral phrase. It sounds productive but specifies no owner, no scope, no deadline. The offline conversation almost never happens. Treat every deferral as a decision requiring the same four elements.
The opening verb of an agenda item is load-bearing. It tells the room what they are authorized to produce.
Dead verbs (no output possible): discuss, review, align, sync, touch base, brainstorm, revisit, share thoughts on
Decision verbs (outcome guaranteed): decide, approve, reject, choose, select, commit, authorize, finalize, prioritize
A decision-grade agenda item contains:
Example: “Decide which of three vendors to contract with for Q1 onboarding, given the budget impact. Sarah owns this decision. Finance advises. Decision needed by Friday.” — This is a contract with the room.
Remove “Any other business” from every agenda. If it was important enough to discuss, it’s important enough to frame as a decision and schedule properly.
People stay silent for many reasons that have nothing to do with consent: uncertainty about their place, not wanting to slow things down, assuming someone else will speak, learned helplessness, or simply not paying attention. Treating quiet as agreement is one of the most expensive leadership mistakes.
Consensus redistributes accountability until no one owns anything. Universal agreement sounds like good leadership, but in practice it means whoever stops pushing back first absorbs the outcome.
A real decision has four simultaneous components:
Three questions to test real ownership vs. false consensus:
If any answer is no, you had a conversation, not a decision.
Read-out meetings are the most expensive form of information delivery. They force every person to absorb content at the presenter’s speed, regardless of what they already know. A 40-minute read-out with 8 people is not 40 minutes lost — it’s 5.3 hours of focused work evaporated.
Replace read-outs with written briefs containing four components:
A status meeting is justified only when:
“People prefer hearing it in person” is not a justification. It is habit.
These are the operational tools that make the principles actionable. Each template below is ready to use — copy it, fill it in, and apply it.
Complete this brief before scheduling a meeting. If you can’t fill it in, you’re not ready to meet. Circulate as a pre-read at least 24 hours before the meeting.
# Decision Brief
## Decision
[State the decision in one sentence using a committing verb: decide, choose, approve, prioritize.]
## Owner
[One person. Not a team. The person accountable for the outcome after the meeting ends.]
## Context
[What does someone need to know to participate usefully? Keep it short — this replaces the first 15 minutes of "catching everyone up."]
## Options
[What are the realistic choices? Frame each one with its key tradeoff. If there are no options, there's no decision — just an announcement.]
- A: [option] — [tradeoff]
- B: [option] — [tradeoff]
- C: [option] — [tradeoff]
## Recommendation
[The owner's preferred path, stated plainly. Arriving without a recommendation wastes the room's time.]
## Deadline
[When does this decision need to be made? What happens if it slips?]
## Attendees & Roles
| Name | Role |
|------|------|
| | Owner / Decider |
| | Advisor |
| | Advisor |
## After the Meeting
Decision made:
Dissent noted:
Next steps:
| Action | Owner | Due |
|--------|-------|-----|
| | | |
The report fills in the pre-read and shares it 24 hours before the meeting. The manager reads it before the meeting — non-negotiable. Nothing in the pre-read gets recited aloud. The meeting starts at the blockers.
# ED3 1-1 Template
## Pre-Read (written by report before meeting)
### Progress
[What shipped, moved forward, or got done since last time? 3-5 items max.]
### Blockers
[What's stuck? Name the specific decision, person, or resource you're waiting on.]
### Decisions Needed
| Decision | My Recommendation |
|----------|-------------------|
| | |
### Topics for Live Discussion
[Anything that genuinely benefits from real-time conversation: career, sensitive feedback, complex tradeoffs.]
## Live Meeting Agenda
| Time | Focus |
|-----------|-------|
| 0:00-0:05 | Blockers — Unblock: escalate, approve, connect, or decide. |
| 0:05-0:10 | Decisions — Report brought recommendations. Manager decides or delegates. |
| 0:10-0:25 | Live topics — Career, feedback, strategy. |
| 0:25-0:30 | Capture & close — What was decided? Who owns what? Write it down now. |
## After the Meeting
Decisions made:
Action items:
| Action | Owner | Due |
|--------|-------|-----|
| | | |
Carried to next 1-1:
Each team member fills in their section by end of day before the meeting. The team lead reads all sections and builds the live agenda from what surfaces. Nothing in the pre-read gets recited aloud.
# ED3 Team Weekly — Week of [DATE]
### [Team Member Name]
**Shipped / Completed**
-
-
**In Progress**
| Item | ETA | Notes |
|------|-----|-------|
| | | |
**Blockers**
[Name the specific person, team, or resource needed. If nothing is blocked, write "No blockers."]
**Decisions / Input Needed**
[Include your recommendation. These drive the live meeting agenda.]
(Copy this section for each team member)
## Live Meeting Agenda
| Time | Focus |
|-----------|-------|
| 0:00-0:15 | Decisions — Pull from "Decisions / Input Needed" across all pre-reads. |
| 0:15-0:25 | Blockers — What's stuck? Assign owners, escalate, or connect people. |
| 0:25-0:30 | Dependencies & coordination — Cross-team handoffs, shared deadlines. |
| 0:30-0:35 | Capture & close — Record decisions and action items. |
## Decisions Made
| Decision | Owner | Date |
|----------|-------|------|
## Action Items
| Action | Owner | Due |
|--------|-------|-----|
Paste this into the description field of your calendar invitation. If you can’t fill in the required fields, the meeting isn’t ready.
# Meeting Invitation
**Subject Line:** DECIDE: [State the decision in plain language]
**Decision (required):** [What will be decided? Use a committing verb.]
**Owner (required):** [One person. Arrives with a recommendation, facilitates, makes the call.]
**Why Now (required):** [What happens if this decision slips a week? If "not much" — handle async.]
**Pre-Read (required):** [Link to document with context, options, and recommendation. Include estimated read time.]
**Attendees & Roles:**
| Name | Role | Why in the room |
|------|------|-----------------|
| | Owner / Decider | |
| | Advisor | |
**Not invited (informed after):**
-
**Expected Outcome:** [What will be true when this meeting ends? State it as a fact from the future.]
A shared register for every meaningful decision your team makes. One line per decision. Fill it in the moment the decision is made — not later. Review the full log once a month as a team.
# Decision Log
| Date | Decision | Owner | Context | Dissent | Review Date | Status |
|------|----------|-------|---------|---------|-------------|--------|
| | | | | | | Active |
## Column Guide
- Date: When the decision was finalized (not first discussed)
- Decision: One sentence, past-tense committing verb (decided, approved, chose)
- Owner: One person accountable
- Context: Why this decision was made — prevents relitigating
- Dissent: Who disagreed and why — the losing argument is worth preserving
- Review Date: When to revisit (required for strategic bets, vendor commitments, debated decisions)
- Status: Active, Superseded, or Reversed
## Monthly Review Checklist
- [ ] Any decisions with past review dates that haven't been revisited?
- [ ] Any decisions with blank owner fields?
- [ ] Any owners who have left the team? Reassign.
- [ ] Same decision appearing more than once? Investigate relitigating.
- [ ] Dissent column always empty? Check whether disagreement is being surfaced.
Take any meeting agenda and rewrite it so every line forces a decision.
Four rewrite rules:
Verb swap quick reference:
| Instead of… | Write… |
|---|---|
| Discuss the Q4 roadmap | Decide which 3 initiatives to fund in Q4 |
| Review the marketing budget | Approve the $45K reallocation from brand to performance |
| Share customer feedback | (move to email or pre-read) |
| Brainstorm feature ideas | (run async, then) Prioritize top 3 features for next sprint |
| Go over project status | (move to pre-read doc) |
| Talk about hiring plan | Decide whether to open 2 or 3 roles this quarter |
AI Rewrite Prompt (paste into any AI tool, then paste your agenda after):
You are an Agenda Rewriter that applies the ED3 framework. Take a vague, topic-based meeting agenda and rewrite it so every line item either forces a decision or gets removed.
RULES:
1. REPLACE THE VERB: "Discuss," "review," "share," "update" are banned. Replace with: decide, choose, approve, prioritize, assign, commit.
2. NAME THE OWNER: Every line must have one person's name.
3. SET A TIME BOX: Every line must have an explicit number of minutes.
4. KILL OR MOVE: Status updates → pre-read. Info sharing → email. Brainstorming → async thread.
OUTPUT: For each item, output one of:
- REWRITTEN: [new item with committing verb] — [Owner] ([X] min)
- MOVED TO ASYNC: [original item] → [where it goes instead]
- CUT: [original item] → [reason]
Then output the final rewritten agenda as a clean list with total time.
Use this to make decisions without a meeting. The owner writes the proposal, circulates it with a review window, collects structured input, and makes the call.
# Async Review Protocol
## The Proposal
**Decision:** [What is being decided? One sentence, committing verb.]
**Owner:** [One person who makes the final call after the review window.]
**Context:** [Why this decision, why now. 3-5 sentences.]
**Options:**
- A: [option] — [tradeoff]
- B: [option] — [tradeoff]
- C: [option] — [tradeoff]
**Recommendation:** [Owner's preferred path and reasoning.]
**Review Window:** [Exact deadline for input.]
**Silence clause:** No response by the deadline = no objection.
## Reviewers
| Name | Role | Why they're reviewing |
|------|------|-----------------------|
## Reviewer Response Options (respond with exactly one)
- **Approve** — No concerns. Proceed as proposed.
- **Approve with comments** — Concerns noted, not blocking.
- **Block** — Specific objection that must be resolved. Name what would resolve it.
## After the Review Window
Decision made:
Date:
Owner:
Blocks resolved:
Dissent noted:
## Outcome Announcement
Subject: DECIDED: [decision in one sentence]
- Decision: [what was decided]
- Owner: [who owns the outcome]
- Next steps: [what happens now, with owners and dates]
- Review date: [when this will be revisited, if applicable]
When to go async vs. sync:
Go async when: options are clear and documented, owner has a recommendation, stakeholders need thinking time not debate, decision is important but not emotionally charged.
Escalate to sync when: options are ambiguous and need exploration, significant disagreement needs to be heard, interpersonal dynamics are involved, speed is critical (can’t wait 48 hours).
Start at Rung 1. Move up only when the current rung can’t resolve the decision. Most decisions never make it past Rung 2.
Rung 1: Owner decides alone. The decision is within the owner’s authority. Make the call, record it in the Decision Log, announce the outcome.
Escalate when: The decision affects other teams, involves significant budget, or the owner needs input.
Rung 2: Async review. Write a proposal using the Async Review Protocol. Circulate, collect responses, resolve blocks in writing if possible.
Escalate when: A block can’t be resolved in writing after two rounds of exchange.
Rung 3: Targeted sync (owner + blocker only). A short, focused 15-30 minute call to resolve a specific disagreement. Not a full meeting. Agenda: “You blocked [proposal] for [reason]. Let’s resolve this.” Use the original proposal as the discussion doc.
Escalate when: The disagreement is broader than two people, involves tradeoffs the full group must weigh, or has political weight requiring visible deliberation.
Rung 4: Full decision meeting (last resort). Everyone has read the proposal. Positions are documented. The specific disagreement is clear. Send a Decision Brief as pre-read. The meeting is about ONE thing: resolving the defined disagreement. End with a decision on the record.
Decision tree:
Can the owner decide alone?
├── Yes → Rung 1. Decide, record, announce.
└── No → Write the proposal (Rung 2).
Any blocks?
├── No → Decision made. Record and announce.
└── Yes → Can blocks be resolved in writing?
├── Yes → Resolve, decide, announce.
└── No → Is it between 2 people?
├── Yes → Rung 3. Targeted call.
└── No → Rung 4. Full decision meeting.
Anti-patterns:
If someone has asked you to help them adopt ED3, follow this sequence.
Ask for artifacts: a few recent meeting invites, agendas, and post-meeting notes or action items. Use these signals:
Level 1 signals (Chaos): Topic-only agendas (“Discuss X”), no decision owners on action items, outcomes phrased as “we discussed” or “we aligned,” “let’s take this offline” appears regularly, same topics appear across multiple meetings.
Level 2 signals (Awakening): Some meetings have clear decisions, most don’t. A few people use decision verbs but most use topic framing. No shared templates or vocabulary. Improvement is person-dependent.
Level 3 signals (ED3 Sync): Decision verbs in agendas, named owners on every action item, a decision log exists, delays are structured with deadlines, status updates are sent as documents before meetings.
Level 4 signals (ED3 Async): Most decisions made via written proposals, meetings are exceptions with clear escalation triggers, silence-means-consent deadlines are standard practice.
From Level 1 to Level 2 (Chaos → Awakening):
Start with ONE change: rewrite the agenda for one recurring meeting using the Agenda Rewriter. Pick the person’s most painful or most frequent meeting. Don’t try to change the whole org at once — prove it works in one room first.
Concrete first action: Take their next meeting agenda, apply the four rewrite rules, and produce a decision-grade agenda. Send it to them to use.
From Level 2 to Level 3 (Awakening → ED3 Sync):
Introduce templates systematically. Start with the Decision Brief for any meeting that needs to be scheduled, and the Meeting Invitation Format for all calendar invites. Add the Decision Log as a shared team artifact. Train the team on the verb swap (discuss → decide).
Concrete first actions:
From Level 3 to Level 4 (ED3 Sync → ED3 Async):
Introduce the Async Review Protocol for decisions that don’t need a room. Implement the Escalation Ladder so the team has a shared understanding of when to meet vs. when to decide in writing. Convert status meetings to written briefs.
Concrete first actions:
As the person starts using ED3 tools, help them with:
Once individual adoption is working:
When someone asks you for help with specific tasks, here’s how to apply ED3:
“Help me prepare for my meeting” → Ask what decision is being made. If they can’t name one, help them define it. Then draft a Decision Brief with the decision, owner, context, options, recommendation, deadline, and attendee roles.
“Rewrite this agenda” → Apply the four rules: replace dead verbs with committing verbs, name an owner for each item, set time boxes, and kill or move anything that isn’t a decision (status → pre-read, info sharing → email, brainstorming → async thread).
“What came out of this meeting?” → Review the output for the four components of a real decision: a specific choice, one named owner, a clear moment, and a written record. If any are missing, rewrite the outcomes as explicit, owned commitments.
“We need to delay this decision” → Check for the four elements of a legitimate delay: what specific information is missing, who is assigned to close the gap, the hard decision date, and what will be different after waiting. If any are missing, it’s a fear-delay — name it and help structure it.
“Set up our team’s meeting cadence” → Design a system using ED3 templates: Team Weekly with async pre-reads and decision-only live time, 1-1s with the ED3 1-1 Template, a shared Decision Log, and the Escalation Ladder for knowing when to meet vs. decide async.
“How do I convince my team/boss to try this?” → Don’t pitch the framework. Demonstrate it. Rewrite one agenda. Run one meeting with a Decision Brief. Show the decision log after one month. The proof is in the output.
ED3 — Every Discussion Delivers Decisions Website: https://briggsd.github.io/ed3framework/ Full manifesto, interactive tools, and downloadable templates available at the link above.