A3 Coaching Guide & Facilitation Agenda
A facilitator-friendly, practical guide to coaching A3 authors and running a focused A3/RCA review meeting. Includes a timeboxed agenda, pre-meeting checklist, facilitation cues, targeted coaching questions for each A3 section, data-validation tips, SMART verification criteria, red flags, and a simple follow-up protocol to ensure A3s are validated and executed.
Purpose
This guide helps coaches and facilitators improve the quality, rigor, and follow-through of A3 problem solving and structured root-cause analysis. Use it to run focused A3 review meetings, coach authors toward better evidence and logic, and ensure countermeasures are testable and verified.
Meeting objective
Validate the A3: confirm the problem is well-defined, the current condition is evidence-backed, root-cause reasoning is defensible, countermeasures are likely to close the gap, and owners, deadlines, and verification steps are agreed and practical.
Standard facilitation agenda (60 minutes)
- Welcome & meeting purpose (5 min) — quick alignment on scope and desired outcome.
- Background & goal (10 min) — confirm scope, business impact, and target condition/goal.
- Current condition walk-through (10 min) — review evidence, data, and process maps.
- Root-cause logic probe (15 min) — test cause-effect links and challenge assumptions.
- Countermeasure review & success criteria (10 min) — make countermeasures specific and testable.
- Agree actions, owners & verification (10 min) — assign tasks, timelines, and verification methods; confirm next check-in.
Note: keep strict timing. If deeper investigation is needed, capture issues and schedule a follow-up workshop rather than letting the meeting drift.
Pre-meeting checklist for the A3 author
- Attach supporting data: charts, timelines, process maps, photos, samples.
- Highlight key metrics (baseline, recent trend, desired target) with sources and timeframes.
- Annotate any assumptions and known data gaps.
- Propose candidate root causes and countermeasures with estimated impact and costs.
- Prepare a clear, concise problem statement and a one-line goal statement.
Facilitator checklist
- Set a collaborative tone: coach, don’t police.
- Focus on evidence and logic, not personalities.
- Keep questions specific and time-boxed; prevent long tangents.
- Call out missing evidence and request concrete follow-up items rather than vague statements.
- Ensure owners and deadlines are realistic; avoid passive language like “monitor” without a method.
Coaching prompts & example questions (by A3 section)
Background & Goal
- What business outcome improves if this is solved? How was that quantified?
- Is the goal time-bound and measurable? (If not, restate it.)
- Who needs this outcome to be true—customers, operations, finance?
Current Condition
- Show the evidence that supports each claim. Where did the data come from?
- How frequently are these measurements taken and by whom?
- Are there process maps or photos that clarify the condition? If not, what should we capture?
Root Cause
- How does each proposed cause lead to the observed effects? Ask for a short causal chain.
- What data supports or contradicts this cause? Could there be other explanations?
- Have simple tests or experiments ruled out alternative causes? If not, what quick test could we run?
Countermeasures & Implementation
- Are countermeasures aimed at the root cause (not symptoms)? Explain how.
- What are the specific actions, who will do them, and by when?
- What resources or approvals are required? Are they available?
Verification & Follow-up
- How will we know the countermeasure worked? Define measurable indicators and data sources.
- What is the acceptance criteria for success? (See SMART checklist below.)
- When is the verification scheduled and who will own it?
SMART verification checklist
Verification steps should be:
- Specific — what will be measured and how.
- Measurable — numeric target or clear pass/fail.
- Assignable — named owner for measurement and reporting.
- Realistic — feasible with available data and methods.
- Time-bound — date for initial check and follow-up checks if needed.
Common red flags to call out
- Vague problem statement without business impact or baseline data.
- Current condition described without primary evidence (relying on anecdotes).
- Root causes stated as symptoms or solutions disguised as causes.
- Countermeasures that are one-off firefighting actions with no verification plan.
- No named owner or unclear timeline for follow-up.
Practical facilitation tips
- Use the A3 as the meeting script — follow its flow and annotate it live.
- Ask the author to present for a short, structured time, then open targeted questions.
- When disagreement arises, ask what test could resolve it and agree to run the test.
- Capture decisions and actions in the A3 (or a linked action log) during the meeting.
Post-meeting follow-up
- Record agreed actions, owners, and deadlines in the A3 or shared action tracker within 24 hours.
- Author updates the A3 with any data or evidence requested during the meeting before the next check-in.
- Schedule a verification check (date and owner) and a follow-up coaching touchpoint if implementation is complex.
- Close the loop: when verification confirms effectiveness, record lessons learned and standardize if appropriate.
When to escalate
Escalate if the A3 identifies safety-critical risks, requires cross-functional resources that are blocked, or if repeated attempts to verify fail and the problem persists with significant business impact.
Suggested templates & artifacts to include
- Data snapshots: trend charts, Pareto, run charts (with sources noted).
- Process maps, spaghetti diagrams, photos of the work area.
- Small experiment plans (PDCA) for testing countermeasures.
- Action tracker with owner, due date, status, and verification result.
Closing note
High-quality A3s blend clear evidence, defensible root-cause logic, practical countermeasures, and rigorous verification. As a coach, your job is to surface gaps, encourage simple tests to resolve uncertainty, and make implementation and verification concrete and owned — not to produce perfect answers on the spot.
Discussion
Comments and conversation will live here.