Expected Outcomes in Meetings | 5 Whys Framework
Expected Outcomes (លទ្ធផលរំពឹងទុក) are the specific decisions, solutions, agreements, or actions that a meeting should achieve by the time it ends.
The 5 Whys Framework helps identify the root causes of problems that prevent meetings from achieving those outcomes.
1. What are Expected Outcomes?
Expected Outcomes answer one key question:
Examples include:
- Decision: Approve the BOQ before submitting a quotation.
- Solution: Resolve differences between QTO measurements and drawings.
- Agreement: Confirm the project schedule and responsibilities.
- Action Plan: Assign tasks, owners, and deadlines.
- Alignment: Ensure everyone understands the next steps.
2. Apply the 5 Whys to Meeting Outcomes
Problem: Our weekly meetings do not produce clear decisions or actionable results.
Why are meetings not producing results?
Because discussions finish without decisions.
Why are decisions not made?
Because participants lack sufficient information.
Why is information insufficient?
Because required reports are not prepared beforehand.
Why aren't reports prepared?
Because preparation tasks and owners are unclear.
Why are responsibilities unclear?
Because there is no standard meeting preparation and accountability process.
◎ Potential root cause
No standardized process for meeting preparation, decision-making, and follow-up.
These are illustrative causes. A real 5 Whys analysis should validate each answer with meeting records and participant evidence.
3. Convert Root Causes into Expected Outcomes
| Root cause | Expected outcome |
|---|---|
| Unclear responsibilities | Assign an owner to each action |
| Missing preparation | Require reports before meetings |
| No decisions | Record decisions or blockers |
| No deadlines | Assign completion dates |
| Poor follow-up | Review action status in the next meeting |
4. Practical Example: BOQ and QTO Meeting
Meeting topic: Review discrepancies between BOQ and QTO.
Problem: The BOQ submission has been delayed.
After investigating the causes using 5 Whys, establish these expected outcomes:
Expected Outcomes Checklist
5. Reusable Expected Outcomes Template
Meeting Outcome Planner — 5 Whys
6. How to Integrate 5 Whys with PDCA
| PDCA | Meeting management |
|---|---|
| Plan | Define the problem, objectives, and expected outcomes |
| Do | Discuss evidence and apply 5 Whys |
| Check | Verify the root cause and compare results against expectations |
| Act | Decide corrective actions, assign owners, and establish deadlines |
7. Key Principle
Problem → 5 Whys → Root Cause → Corrective Action → Expected Outcome → Follow-up
5 Whys helps discover why a problem exists. Expected Outcomes define what the meeting must accomplish to address it.
A productive meeting is not measured by how long people discuss a problem. It is measured by the decisions reached, problems clarified or resolved, and accountable actions that follow.
Remember: A clear expected outcome should be specific, observable, realistic, and time-bound whenever applicable.