Guide: A3 Problem Solving

Master Toyota’s A3 method step-by-step. See examples, compare A3 vs DMAIC, and

download a useable excel template to start solving problems on one page.

📝 A3 Problem-Solving TL;DR – read in 60 s

A3 Problem-Solving compresses the PDCA cycle onto a single A3-size sheet. Teams
define the problem, map the current condition, pinpoint root causes, set
countermeasures, and verify results—creating a living storyboard for coaching
and continuous improvement.

 Origin: Toyota, late 1960s

 Paper size: ISO A3 — 297 × 420 mm (11 × 17 in)

 Framework: 5-section PDCA flow

 Best for: Medium-complexity, recurring problems

 Free template: A3 Problem-Solving Excel Template

What Is an A3 Report?

Born inside Toyota in the late-1960s, an A3 report started out as nothing more exotic
than an A3-size sheet of paper (297 × 420 mm | 11 × 17 in). Engineers found the
format large enough to fit charts, sketches, and handwritten notes—yet small enough
to pin on an Obeya wall or carry to the gemba. Over time, that humble page evolved
into a full-blown problem-solving discipline and, eventually, a leadership practice
for developing people.

Today the term “A3” carries three intertwined meanings:

 1. The Paper Size – A practical constraint that forces clarity. You must tell the
entire story—problem, evidence, root causes, countermeasures, and follow-up—
without spilling onto a second page.

2. The Thinking Process – A structured, PDCA-based flow that guides teams

through five core sections: Problem & Background → Current Condition → Root-
Cause Analysis → Countermeasures & Targets → Follow-Up. The template is
simply a scaffold for that logic.

3. The Coaching Storyboard – A living visual that invites questions from

mentors and peers. Leaders review drafts, probe for deeper “Why?” layers, and
strengthen the author’s critical-thinking muscles. The sheet becomes a dialogue
in ink.

Because all data, analysis, and actions live side-by-side, gaps in logic stand out
instantly: if the root cause doesn’t link to a countermeasure, the page exposes it; if
results aren’t checked, the blank Follow-Up box reminds the team to verify. In this
way, an A3 report is both artifact and feedback loop—a single piece of paper that
aligns stakeholders, accelerates learning, and captures organisational memory long
after the ink dries.

Why Use A3 Thinking?

A3 thinking isn’t just a template—it’s a miniature operating system for

continuous improvement. Here’s why teams in manufacturing, healthcare,
software, and even HR keep reaching for that single sheet:

1. Cuts Through Noise & Waste

Limiting the story to one page forces you to separate signal from clutter.
Extraneous charts, pet theories, and “nice-to-haves” simply won’t fit. What
remains are the facts that matter—making non-value-adding steps, delays, and
hand-offs painfully obvious.

2. Builds a Coaching Culture

Because the sheet is public and iterative, leaders don’t “approve” it so much
as coach it. They ask Socratic questions (“Where did you observe this?” “Which
KPI will prove success?”*) that sharpen the author’s thinking. Over time, the
organisation gains more problem-solvers, not just more reports.

3. Creates a Shared Visual Language

Engineers, operators, accountants, and executives can all stand around the
same page and follow the flow left-to-right: problem → evidence → causes →
actions → results. No lengthy slide decks, no hunting for the latest revision—just
one living storyboard everyone can read in minutes.

4. Accelerates PDCA Loops

 With the entire Plan-Do-Check-Act cycle visible at a glance, teams feel the urge
to close the loop quickly. Follow-up boxes left blank are an eye-level reminder
that learning isn’t finished until results are verified and standard work is
updated.

5. Locks in Organisational Memory

Finished A3s become bite-sized case studies—pin them on an Obeya wall or

save them in a digital gallery. When a similar issue crops up months later, the
solution (and the thinking behind it) is already documented, sparing the team
from reinventing the wheel.

In short, A3 thinking replaces sprawling reports and siloed problem-solving with a

concise, visual discipline that reduces waste, grows people, and spreads know-how
across the enterprise.

The Standard 5-Step Flow

Although different companies draw their A3 sheets in landscape or portrait—and may

number the boxes 7, 8, or even 9—the logical backbone is always the same five-
step PDCA flow. Think of it as a left-to-right storyboard: you first set the scene (Plan),
then gather facts (Do), test your logic (Check), and finally lock in the gain (Act).
Mastering these five boxes is 80 % of A3 success.

1 Problem & Background

Purpose: Establish why this matters, now—in one or two sentences.

 Start with the voice of the customer or KPI shift. “First-pass yield on Line
B has slipped from 97 % to 92 % since 1 April 2025.”

 Quantify the impact. Money lost, hours delayed, safety risk—pick the metric
leadership already cares about.
  Give essential context only. If new software went live last month, note it; if
the scrap trend dates back three years, mention the baseline. Resist writing the
company’s entire history.

✏️ Tip: Ask “Would a colleague from a different plant instantly grasp the pain?” If not,
tighten the wording.

2 Current Condition

Purpose: Paint an evidence-based snapshot of reality. No guessing allowed.

Go to the gemba. Stand where the defect appears, follow material flow, watch the
operator’s motion.

 Show, don’t tell. Use a clear photo, time-series chart, or spaghetti diagram.
One powerful visual beats four paragraphs.

 Quantify variation. Note frequency, trend, or location of the problem. E.g.,

“80 % of defects occur on the night shift.”
  Avoid causes here. Describing “why” too early contaminates the data with
opinion.

📸 Common formats: Pareto bar of defect codes, run chart of downtime, annotated
workstation photo.

3 Root-Cause Analysis

Purpose: Expose the real mechanism driving the gap—not just the first-order
symptom.

1. Apply the 5 Whys. Start with the problem statement; ask “Why?” until you hit
a controllable process factor.

2. Map contributory branches. Use a Fishbone/Ishikawa diagram (Man,

Machine, Method, Material, Measurement, Environment) to avoid tunnel vision.

3. Verify each link with data or direct observation. Correlate torque-gun

calibration records with the spike in loose fasteners; confirm procedure steps
missed via time-study video.

4. Converge on a single root cause or a primary causal chain. Multiple weak

theories dilute action and stall momentum.

🚫 Red flag: If your 5th Why answer is “operator makes mistake,” you have not
reached root cause—keep going until you find a systemic factor you can change
(fixture design, software logic, unclear work standard).
4 Countermeasures & Targets

Purpose: Translate causes into concrete, testable actions and desired future metrics.

 One countermeasure per root cause. Traceability keeps the narrative tight.

 Define owner, deadline, and expected KPI shift. E.g., “Install torque-gun
auto-shutoff; Maintenance; 15 Aug 2025; target FPY back to ≥ 97 %.”

 Classify impact vs effort. Quick wins first; structural fixes next.

 Pilot whenever sensible. A 2-day trial on one shift de-risks the full rollout.

 Set numeric targets. “Reduce defect PPM by 50 %” is clearer than “improve

quality.”

📊Mini-matrix: Countermeasure | Owner | Due | Cost | Predicted KPI.

5 Follow-Up / Check & Act

Purpose: Close the PDCA loop, prove effectiveness, and hard-wire the learning.
 1. Collect post-implementation data. Same KPI, same sampling method;
compare before/after.

2. Visualise results on the A3. A second run chart with the new data or a
green/red status icon keeps the story self-contained.

3. Decide:

 Hit target? → Standardise: update work instructions, train operators, audit

at 30- and 90-day marks.

 Missed target? → Return to Step 3—your root-cause theory was

incomplete.

4. Capture lessons learned. Why did this countermeasure work (or not)? Record
so the next team can reuse or refine.

5. Share and archive. Pin the signed-off A3 to an Obeya wall or save in a digital
gallery for future reference and onboarding.

🔁 Reminder: An unchecked Follow-Up box is a silent backlog item; schedule the

review date at the start to keep momentum.

When you discipline yourself to walk through these five boxes in order—no skipping,
no shortcuts—the A3 sheet stops being just a form and becomes a compact engine for
learning. Problems shrink, teams grow, and each finished page adds another brick to
your organisation’s knowledge wall.

Step-by-Step How to do an A3

Below is a step-by-step guide on how to do an A3, what tools you need and how long
you should expect it to take.
 Prep the Canvas

Print blank A3 sheets or open a shared

digital board; gather baseline KPIs and
relevant photos.

Time: 30 min

Tools: A3 template, latest KPI charts

1.

Walk the Gemba

Observe the process where the issue

occurs, capture photos/video, and
interview frontline staff.

Time: 30 min
2.
Tools: Camera, notebook

Draft Problem & Current Condition

Co-write a one-sentence problem

statement and paste key visuals into
the Current-Condition box.

Time: 30 min
Tools: Whiteboard markers, printed
3. photos

Run Root-Cause Workshop

Facilitate 5 Whys and a Fishbone

diagram; verify each causal link with
data or observation.

Time: 60 min
4. Tools: Fishbone template, data print-
outs
 Prioritise Countermeasures &
Targets

Link each root cause to a

countermeasure; assign owner, due
date, cost band, and expected KPI shift.

Time: 45 min

5. Tools: Impact-Effort matrix, dot-votes

Coach, Approve & Schedule Follow-

Up

Mentor probes logic, signs off the sheet,

and sets a review date in the Follow-Up
box before adjournment.

Time: 30 min

6. Tools: Calendar invite, A3 gallery

Conclusion

A3 problem-solving isn’t just a form—it’s a disciplined habit that fuses data, dialogue,
and decisive action onto a single, shareable page. By walking the gemba, visualising
root causes, and locking each counter-measure to a measurable target, you transform
nebulous “issues” into clear experiments that build both capability and confidence
across your team. The finished sheet becomes corporate memory you can pin on an
Obeya wall, reference in audits, or use to onboard new colleagues—evidence that
learning is happening every day.

If this guide has shown one thing, it’s that speed and rigour can coexist: you can
draft an A3 in a morning and still meet ISO or customer requirements—no bloated
slide decks required. Start small: pick a chronic nuisance, download the template, and
run the six-step session. In a week you’ll have hard numbers, tighter teamwork, and
the momentum to tackle the next challenge.

Continuous improvement begins with a single page—make yours count.

References

1. Arthur, B. (2021). Reducing nightly data-warehouse batch times with A3

problem-solving (A3 report). Lean Enterprise Academy. [Link]

2. Dennis, P. (2006). Getting the Right Things Done: A Leader’s Guide to Planning
and Execution. Lean Enterprise Institute.

3. Liker, J. K. (2004). The Toyota Way: 14 Management Principles from the World’s
Greatest Manufacturer. McGraw-Hill.
4. Newsome, R., Cunningham, J., & Kincaid, C. (2019). Decreasing Falls in the
Emergency Department (Lean A3 poster). Moses Cone Health
System. [Link]

5. Pereira, A., Silva, C., & Lopes, I. (2019). Application of the A3 methodology for
the improvement of an assembly line. Procedia Manufacturing, 38, 447–
454. [Link]

6. Rother, M., & Shook, J. (2003). Learning to See: Value-Stream Mapping to Add
Value and Eliminate MUDA (2nd ed.). Lean Enterprise Institute.

7. Shook, J. (2009). Managing to Learn: Using the A3 Management Process to

Solve Problems, Gain Agreement, Mentor and Lead. Lean Enterprise Institute.

8. Womack, J. P., Jones, D. T., & Roos, D. (1990). The Machine That Changed the
World. Free Press.