A3 Coaching Quick Reference & Facilitation Checklist

Welcome

This quick reference helps coaches and facilitators guide A3 problem solving so teams stop treating symptoms, document learning, and verify that countermeasures actually work. Use it during A3 development sessions, peer reviews, and follow-up verification meetings. Keep it at hand when you prepare, facilitate, or evaluate an A3.

Why this matters

An effective A3 creates a clear problem statement, shows evidence of the current condition, identifies a measurable target, surfaces root causes, captures countermeasures linked to causes, and defines a plan with owners and verification. Coaching keeps the team honest: evidence-driven, specific, and measurable.

How to use this guide

Use the section-by-section cues to prepare and to nudge the discussion. Use the facilitation checklist and timeline to run efficient review meetings. Use the verification checklist when closing an A3 to ensure countermeasures are validated and learning is captured.

Section-by-section coaching cues

Background

• Purpose: Ask the team to explain why this problem matters to the business or customer in one or two sentences.
• Coach prompts: "Who is affected?" "What value or risk is at stake?" "Why now?"
• Tip: Discourage long histories—capture context that relates to the problem, not the full story.

Current condition

• Purpose: Show evidence—numbers, visuals, process steps, timelines, photos.
• Coach prompts: "What does the data say?" "Where is the waste or defect?" "Can you walk me through the process where the issue occurs?"
• Verification cue: Request data sources and recent timestamps. Avoid anecdote-only descriptions.

Target (Goal)

• Purpose: A specific measurable target and timeframe (e.g., reduce defect rate from 4% to 1% in 90 days).
• Coach prompts: "How will you measure success?" "Is this stretch but achievable?"
• Tip: Favor percent, rates, lead/lag indicators, and explicit deadlines over vague aims.

Analysis / Root cause

• Purpose: Show why the problem happens. Use fishbone, process maps, and 5 Whys as evidence-oriented tools.
• Coach prompts: "What evidence supports each root cause?" "Which causes most directly link to the data in the current condition?"
• Prompt to quantify: Estimate impact of each cause where possible to prioritize countermeasures.

Countermeasures

• Purpose: Actions that directly address identified root causes.
• Coach prompts: "Which countermeasure is linked to which cause?" "How will this prevent recurrence?" "What is the smallest effective countermeasure to test first?"
• Verification cue: Specify leading indicators to track during implementation and a measurement plan for final verification.

Plan (who/what/when)

• Purpose: Clear responsibilities, deadlines, and resources.
• Coach prompts: "Who owns implementation, who verifies, and when will status be reviewed?" "What are the minimum steps to get a quick test running?"
• Tip: Use small experiments with clear acceptance criteria before wide rollout.

Follow-up / Verify

• Purpose: Confirm the countermeasure solved the root cause and did not create worse side effects.
• Coach prompts: "What evidence will indicate success?" "When will we declare the A3 closed and what learning will be recorded?"
• Verification cue: Define both leading and lagging metrics, sample sizes, and review dates.

Common coaching pitfalls and how to nudge back

• Rushing to solutions: Ask for data that shows the gap before discussing fixes.
• Blaming individuals: Reframe to ask what in the system allowed the failure.
• Vague countermeasures: Require a testable hypothesis and measurable outcome.
• No verification plan: Insist on at least one leading metric and a verification date before approving closure.
• Too many countermeasures: Prioritize 1–3 experiments; keep the rest as backlog items.

Facilitation timeline (example for a 60–90 minute A3 review)

1. (5 min) Quick framing: Purpose and meeting objective.
2. (10–15 min) Current condition & data review (ask for evidence).
3. (15–20 min) Root cause analysis summary—confirm logic and evidence.
4. (10–20 min) Countermeasures & plan—ensure linkage to causes, owners, and measures.
5. (5–10 min) Verification plan and next steps—confirm dates and follow-up meeting.
6. (5 min) Close: Capture decisions and any immediate actions.

Verification & evidence checklist

• Current condition: Data sources cited and recent.
• Root causes: Each cause has supporting evidence or mapping to the process.
• Countermeasures: Each countermeasure lists the specific cause it addresses.
• Plan: Owners named, deadlines set, and resources identified.
• Metrics: Leading indicator(s) and final measure defined with baseline and target.
• Follow-up: Verification date and responsible verifier scheduled.

Quick facilitation checklist

• Has the team shown the data for the current condition?
• Is the target specific and measurable?
• Do root causes tie to evidence, not assumptions?
• Are countermeasures mapped to causes and set up as experiments?
• Are owners and verification steps explicitly assigned?
• Is there a scheduled follow-up to review effectiveness?

Sample coaching questions (practical prompts)

• "Show me the data that led you to this problem statement."
• "If this cause did not exist, how would the current condition change?"
• "What is the smallest change we can test to see if this cause is addressed?"
• "How will you detect a successful countermeasure within 2 weeks?"

Capturing countermeasures & measuring effectiveness

Record each countermeasure with: owner, start date, expected outcome, leading indicator(s), lagging metric(s), verification date, and lessons learned. After verification, update the A3 to show evidence of change or a reason to iterate.

Roles & responsibilities

• Coach/Facilitator: guide evidence-based questions, keep time, prevent scope creep.
• Owner (A3 author): prepare evidence, present analysis, drive experiments.
• Verifier: independent check of measurements and confirmation that the countermeasure worked.

Next steps template (short)

After the review, capture: (1) Immediate actions (who/what/when), (2) Experiment to run (hypothesis, metric, duration), (3) Verification meeting date, (4) Where the A3 will be stored and who will update it.