Six Sigma Kaizen logo

Calculator Library / Problem Solving

A3 Problem-Solving Builder

Fill in the nine boxes of a Toyota-style A3, watch the one-page report build live, and get flagged on the same structural pitfalls a good coach would catch.

Builder

Fill in each box

Completeness & pitfall check0/9 boxes
    Why does this matter — customer, safety, quality, cost, or delivery impact?
    The gap between actual and expected performance. No solution language.
    What direct observation and data show today.
    What success looks like, by when, and how it's measured.
    5 Whys, Fishbone, Pareto, or data analysis — tested, not assumed.
    Practical actions addressing the validated cause above.
    Actions, owners, due dates, and required support.
    Performance after implementation, compared against the target.
    What gets updated — standard work, training, audits, control plans.

    Instructions

    How to use this app

    1. Work through the nine boxes in order — background and problem statement first, root cause before countermeasures.
    2. Watch the completeness and pitfall check on the left; address any flagged warnings before treating the A3 as done.
    3. Review the live one-page preview on the right as the report takes shape.
    4. Use Load Ridgeline example to see a filled-in A3 built from the SPC guide's tool-wear investigation.
    5. Use Print / Save PDF to produce a clean one-page report once the A3 is complete.

    What This A3 Builder Does

    An A3 is a discipline, not a template — the value is in direct observation, tested root causes, and a completed PDCA loop, not a filled-in page. This builder keeps the classic nine-box Toyota structure in order, renders a live one-page preview as each box is filled in, and checks for a handful of the same structural pitfalls a good A3 coach would catch: solution language in the problem statement, countermeasures proposed before a root cause is validated, and a plan with no follow-up check.

    It pairs with the A3 Problem Solving body-of-knowledge entry, which covers the full method, examples, and common failure modes.

    The Nine Boxes

    BoxPurpose
    1. BackgroundWhy this problem matters in business terms.
    2. Problem StatementThe gap between actual and expected performance, without naming a fix.
    3. Current ConditionWhat direct observation and data show today.
    4. Target ConditionA specific, measurable definition of success.
    5. Root Cause AnalysisTested causes, not assumptions.
    6. CountermeasuresActions that address a validated cause.
    7. Implementation PlanOwners, dates, and support needed to act.
    8. Check ResultsPerformance after implementation, against the target.
    9. Standardize & Share LearningWhat gets updated so the gain holds and the lesson spreads.

    How to Interpret the Pitfall Check

    A3 Problem-Solving Builder Frequently Asked Questions

    Why does the builder warn about solution language in the problem statement?

    If a problem statement already names a fix — "implement automation," "add training" — the rest of the A3 tends to become justification for that fix instead of genuine analysis. Naming the gap without naming the solution keeps the root cause analysis honest.

    Why flag countermeasures written before a root cause is filled in?

    A countermeasure should address a validated cause, not a guess. Filling in countermeasures while the root cause box is still empty is a common sign the team jumped to a fix before finishing the analysis.

    Does this replace an A3 coaching conversation?

    No. The value of A3 thinking is in the coaching and challenge that happens around the document, not the document itself. This builder keeps the format consistent and flags a few common structural problems, but a completed template is not proof that real problem-solving happened.

    Can this be used outside manufacturing?

    Yes. A3 thinking is used in healthcare, service operations, product development, logistics, and administrative processes. The nine boxes and the underlying PDCA logic stay the same regardless of industry.

    Related Pages