THE FOUR-QUESTION FRAMEWORK
Elite teams (Wall Street traders, Seal Team Six, championship sports teams) structure post-mortems around four simple questions. Use this framework for every post-mortem discussion.
The Framework
Question 1: What Was Supposed to Happen?
Establish the objective. What was the intended process, timeline, and outcome?
Question 2: What Actually Happened?
Document reality using objective data (the "game tape"). What actually occurred?
Question 3: Why Was There a Difference?
Identify root cause. Issue category's include:
- Process Issue: The workflow itself is flawed
- Step Coverage Issue: The process is correct, but guidance is unclear
- Human Error: Process is correct, but execution failed (ask: what environmental design would have prevented this?)
- External Factor: Something outside the team's control
Question 4: What Will We Do Differently Next Time?
Define the specific fix. Assign an owner. Set a timeline. Define success metric.
Example Walk-Through
Scenario: Client onboarding took 9 days instead of 5.
Q1: What was supposed to happen?
"Onboarding should complete in 5 days with all documents collected by Step 3."
Q2: What actually happened?
"Onboarding took 9 days. We didn't request documents until Step 6, causing a 4-day delay."
Q3: Why was there a difference?
Root Cause Category: Step Coverage Issue
"Step 3 didn't clearly indicate when to request documents."
Q4: What will we do differently?
Fix: "Add automated 24-hour reminder at Step 2 to request documents."
Owner: Sarah (Process Owner)
Timeline: Implemented by end of day
Success Metric: Next 10 onboardings complete in 5 days or less
When to Use This Framework
80% of issues → Quick Fix (5 minutes, no meeting)
- Wrong form in workflow
- Typo in instructions
- Broken link
- Process owner reviews feedback, fixes immediately
15% of issues → 15-30 Minute Discussion
- Step consistently takes longer than expected
- Multiple people report same friction
- Use four-question framework with 2-4 people
5% of issues → Full Investigation (60 minutes)
- Complex root cause
- Systemic problem affecting multiple workflows
- Requires deep analysis
TEMPLATE 1 - QUICK FEEDBACK FORM
Use this immediately after execution. Distribute via Slack, email, or embed in workflow system.
2-Minute Feedback Form
```
WORKFLOW: _________________________________
DATE: ____________
EXECUTED BY: _______________
---
1. Did you encounter any friction during this workflow?
☐ Yes ☐ No
If yes, where?
_________________________________________
_________________________________________
---
2. Do you have a tip for others executing this workflow?
_________________________________________
_________________________________________
---
3. Any case-specific notes for this execution?
_________________________________________
_________________________________________
---
4. Should we conduct a full post-mortem?
☐ Yes ☐ No
If yes, why?
_________________________________________
_________________________________________
---
☐ Submit anonymously (optional)
[SUBMIT] [SKIP]
```
Implementation Tips
Make it easy:
- One-click access after workflow completion
- 2-minute timer
- Anonymous option for teams building psychological safety
Emphasize purpose:
"This feedback directly improves the process for everyone. This is for learning, not blame."
Act on feedback visibly:
When you make a change based on feedback, announce it: "Based on Marcus's feedback, we've updated Step 3 to include..."
TEMPLATE 2 - FOUR-QUESTION DISCUSSION GUIDE
Print this and bring to your 15-30 minute post-mortem discussion.
Post-Mortem Discussion Guide
PROCESS: _______________________________
DATE: ______________
FACILITATOR: _______________
PARTICIPANTS: _____________________________________
QUESTION 1: What Was Supposed to Happen?
[Describe intended process, timeline, outcome]
____________________________________________
____________________________________________
____________________________________________
QUESTION 2: What Actually Happened?
[Use "game tape"—objective data showing actual execution]
____________________________________________
____________________________________________
____________________________________________
QUESTION 3: Why Was There a Difference?
Root Cause Category (select one):
☐ Process Issue (workflow is flawed)
☐ Step Coverage Issue (guidance unclear)
☐ Human Error (what environmental design would have prevented this?)
☐ External Factor (outside our control)
Explanation:
____________________________________________
____________________________________________
____________________________________________
QUESTION 4: What Will We Do Differently?
Specific Fix:
____________________________________________
____________________________________________
Owner: ________________ Timeline: ____________
Success Metric (how will we know it worked?):
____________________________________________
____________________________________________
Facilitation Checklist
Before meeting:
☐ Pull audit report (the "game tape")
☐ Review feedback forms submitted independently filled in
☐ Identify participants (who was involved?)
During meeting:
☐ Frame as learning, not blame
☐ Focus on facts, not opinions
☐ Push for specific fixes (not vague "we'll do better")
☐ Get agreement on owner and timeline
After meeting:
☐ Process owner implements fix immediately
☐ Document summary
☐ Share with team: "Here's what we learned and changed"
30-DAY IMPLEMENTATION PLAN
Follow this week-by-week plan to prove real-time post-mortems work in your organization.
WEEK 1: Select Your Pilot Process
Goal: Choose one high-volume process to pilot.
Action Steps:
☐ List your top 5 operational processes
☐ For each, assess:
- Volume (executed at least 10x/week?)
- Known friction (suspected improvement opportunities?)
- Clear ownership (one leader can update?)
☐ Select highest-scoring process
☐ Document baseline:
- Average execution time: ____ minutes
- Current error rate: ____%
- Known friction points: [List 3-5]
☐ Communicate to team:
"Starting next week, we're piloting real-time feedback for [Process]. You'll see 2-minute forms after execution. This is for learning and improvement, not blame."
Deliverable: One pilot process selected + baseline documented
WEEK 2: Set Up Immediate Feedback Capture
Goal: Build the mechanism to capture feedback immediately.
Action Steps:
☐ Option 1: Configure LivPro 2-minute feedback forms
☐ Option 2: Create Google Form with Template 1, set up Slack trigger
☐ Test with 2-3 team members
☐ Make adjustments based on feedback
☐ Go live with full team
☐ Monitor submission rate (target: 60%+)
☐ Remind team in standup: "Please submit feedback after completing [Process]"
Deliverable: Feedback mechanism live + capturing data
WEEK 3: Conduct Your First Real-Time Post-Mortem
Goal: Run one full post-mortem using four-question framework.
Action Steps:
☐ Day 1: Select recent execution where issue occurred
☐ Day 2: Pull audit report (who did what when, timeline, duration)
☐ Day 3: Gather 2-4 participants, use Template 2:
- Question 1: What was supposed to happen?
- Question 2: What actually happened?
- Question 3: Why was there a difference?
- Question 4: What will we do differently?
☐ Day 4: Process owner implements fix, update goes live
☐ Day 5: Share summary with team:
"Here's what we learned: [Issue]. Here's what we changed: [Fix]. Next execution should be [X] faster/better."
Deliverable: One post-mortem completed + one improvement integrated
WEEK 4: Measure the Impact
Goal: Quantify results.
Action Steps:
☐ Track next 10 executions of improved process
☐ Measure same metrics as Week 1 baseline:
- Average execution time
- Error rate
- Team feedback sentiment
☐ Compare to baseline:
| Metric | Week 1 | Week 4 | Change |
| Avg time | ___ min | ___ min | __% |
| Error rate | ___% | ___% | __% |
☐ Create one-page summary:
- What we improved
- Measurable impact
- Why real-time feedback matters
☐ Share with team and leadership
Deliverable: Proof that real-time post-mortems produce measurable results
Expected Results After 30 Days
Quantitative:
- 1-3 process improvements integrated
- 15-30% reduction in execution time or errors
- 60-80% feedback capture rate
Qualitative:
- Team feels "heard" (feedback leads to real change)
- Process owner has clear visibility into friction
- Culture shift: Errors seen as improvement opportunities
Next Steps After Pilot Success
Month 2: Expand to 2 more processes
Month 3: Expand to 2 more processes
Month 6: All critical workflows have real-time post-mortems
QUICK FAQ + NEXT STEPS
Top 6 Questions Answered
Q1: Won't this create meeting overload?
A: No. 80% of feedback is captured in 2-minute forms and fixed by process owner (no meeting). Only 15% need short discussions. Only 5% need full meetings.
Q2: What if team members don't provide honest feedback?
A: Three strategies: (1) Enable anonymous submission, (2) Leader models honesty first, (3) Show visible action when feedback leads to change which builds trust over time.
Q3: How do I prioritize which feedback to act on first?
A: High-frequency issues first (they compound). Use this matrix:
| High Frequency | Fix immediately | Fix when time allows |
| Low Frequency | Fix strategically | Document but defer |
Q4: What if the same issue keeps appearing despite fixes?
A: You likely misidentified the root cause category. If you assumed "human error," it's probably a process or step coverage issue. Run a deeper analysis.
Q5: How long should we pilot before rolling out broadly?
A: 30 days on one process is enough to prove the concept, build trust, and refine your approach. Then expand to 2-3 processes per quarter.
Q6: Can real-time post-mortems replace quarterly retrospectives?
A: No, they're complementary. Real-time post-mortems handle day-to-day improvements. Quarterly retrospectives handle bigger-picture strategic improvements. Run both.
Unlock this Guide
Enter your details to access the full guide and resources.