A3 Problem Solving: The Complete Toyota Guide (2026)

The A3 report is Toyota’s one-page problem-solving canvas. It forces background, current condition, goal, root cause, countermeasures, implementation plan, and follow-up onto a single A3-sized sheet (297 × 420 mm) so the whole story stays visible at once. The paper size is the constraint; the PDCA logic underneath is the method. The form is strict, so the thinking can be rigorous.

Outside Toyota, A3 became the standard Lean problem-solving artefact in the early 2000s. It is now the internal sibling of 8D: where 8D is a customer-facing corrective-action document, A3 is an internal thinking canvas and a coaching tool. This guide walks each of the seven canonical A3 sections, explains what good looks like in each, and names the three habits that kill most first-draft A3s.

What is an A3 report?

An A3 report is a structured, one-page document that tells the complete story of a problem-solving effort using a fixed sequence of sections. The “A3” refers to the ISO A3 paper size on which Toyota originally wrote these reports. The name stuck even as digital versions became the norm.

The point of the A3 is not the paper, the template, or even the problem itself. It is the discipline imposed by the one-page constraint: if your background, analysis, countermeasure, and plan do not fit on a single sheet, you have not yet understood the problem well enough to act on it. The constraint is the rigor.

An A3 is also, deliberately, a coaching artefact. The author writes; a coach (sensei, senior engineer, manager) reads and asks questions. The draft visibly exposes weak spots — missing baseline numbers, jumping to solutions, vague ownership — so the coaching loop can happen in public and improve over cycles.

Brief history: Toyota, Ohno, Cho, Shook

A3 emerged inside Toyota during the 1960s and 70s as an extension of Taiichi Ohno’s problem-solving practice and the PDCA cycle he inherited from W. Edwards Deming. Fujio Cho — who later became Toyota’s president — formalised the one-page discipline as a company-wide expectation. Every manager, every engineer, every problem: one A3, one story, one evolving draft.

Outside Toyota, A3 was opaque for decades. It broke into the wider Lean community through Durward Sobek II and Art Smalley’s Understanding A3 Thinking (2008) and John Shook’s Managing to Learn (2008), both of which reframed the A3 as a thinking habit rather than a reporting format. That reframe is why the A3 spread well beyond automotive into software, healthcare, logistics, and services in the 2010s.

When A3 is the right tool

A3 fits well for:

• Internal Lean improvement where the team owns both the problem and the remedy.
• Cross-functional escalations inside a single organisation.
• Engineering root cause on problems too big for a 30-minute 5 Whys session.
• Coaching — training the next layer of managers and engineers to think with structure.

A3 is the wrong tool for:

• Customer-facing formal corrective action — use 8D (the Ford AIAG format).
• Regulatory investigations (FDA, OSHA, FAA) that mandate specific report formats.
• Pure data-mining problems where the right tool is a Pareto chart or FMEA, not a narrative canvas.

The canonical 7-section layout

A3 templates vary slightly between Toyota divisions and Lean consultancies, but the canonical layout used by the Lean Enterprise Institute and Toyota Supplier Support Centers has seven sections, split across the sheet left-to-right along the PDCA cycle:

Section	PDCA	Purpose
1. Header	—	Title, author, coach, date, revision.
2. Background	Plan	Why this problem matters, to whom, and what strategic goal it ties to.
3. Current Condition	Plan	The baseline, with data and a simple visual of the process.
4. Goal / Target	Plan	The measurable target and deadline: “from X to Y by Z.”
5. Root Cause Analysis	Plan	Move from symptom to systemic cause using 5 Whys or Fishbone.
6. Countermeasures	Plan	The smallest set of actions that eliminate each root cause.
7. Implementation & Follow-up	Do / Check / Act	Owners, deadlines, verification metric, and a scheduled follow-up check.

Sections 2–6 sit on the left half of the sheet (the entire Plan phase); section 7 occupies the right half (Do, Check, Act). That left-to-right reading order is deliberate: anyone can skim the left side to understand the thinking, then read the right side to see what actually happened.

1. Header

One-line title that names the gap, not the solution. Good: “Cycle time on Line 3 is 28% over takt.” Bad: “Install new fixtures on Line 3.” Include author, coach, department, date opened, and a revision number — an A3 is a living draft and each revision should be dated.

2. Background

Three to five sentences answering: why is this problem worth solving now? Who feels the pain? What higher-level business or customer goal does closing this gap serve? Avoid generic “quality is important” framing — ground the background in a specific customer impact, cost, or strategic pillar.

3. Current Condition

The most-rewritten section of any first-draft A3. It must show the current process (a simple diagram or flow sketch) and current data (chart, histogram, Pareto). Without measured baseline you cannot set a credible target or verify that the countermeasure worked. If the current condition is unclear, go to gemba (the actual workplace) before writing more of the A3.

Common tools for this section: a Pareto chart of defect types, a run chart of cycle time, a value-stream map fragment, or a spaghetti diagram of operator movement.

4. Goal / Target Condition

A measurable target with a deadline, written as “from X to Y by Z.” Example: “from 58 s average cycle time to 45 s (takt) by end of Q2.” If you cannot state the target this way, the current condition is not quantified enough.

5. Root Cause Analysis

This is where the A3 shares DNA with the rest of the RCA toolkit. Use 5 Whys on the primary branch, or a Fishbone diagram when the causal landscape is unclear. Whichever you use, the A3 box should show the verified root cause, not a list of symptoms.

A practical rule from Toyota: the root cause must explain all the data in the current condition. If your Why-chain terminates at “operator error” but the Pareto chart shows the defect spiking only on the night shift, your analysis is not finished.

6. Countermeasures

Choose the smallest set of actions that each eliminate a verified root cause. Rank candidates by impact-vs-effort; do not pack the box with everything the team wants to do. A3 discipline is to pick the few countermeasures that directly close the gap, not a shopping list.

Each countermeasure should reference the root cause it addresses: “Add andon trigger at station 4 (addresses root cause #2: no escalation path on missed takt).”

7. Implementation Plan & Follow-up

The right half of the sheet. Every countermeasure gets an owner, a start/due date, a verification metric, and a scheduled follow-up check. Leave a dated placeholder for the follow-up results; do not declare the A3 closed until you can fill that placeholder with data showing the target was met.

If the follow-up shows the gap is not closed, loop back. Revisit root cause first, then countermeasure design. Declaring victory on A3 that did not move the metric is the single fastest way to lose credibility with a Lean coach.

Worked example: Cycle-time gap on a Lean line

An illustrative A3 for a production cell producing automotive fasteners. Takt time from pull demand is 45 s; measured average cycle is 58 s (28% over takt, causing nightly overtime). This is the short form of what would live on the actual sheet.

A3 as a coaching tool

Most of the value of A3 is not the completed sheet — it is the process of making the sheet. The author drafts; the coach reads and asks questions. Common coach questions: “what is your baseline number?” “does your root cause explain all the data?” “which countermeasure directly addresses which cause?” “how will you know it worked?”

The coach never writes on the A3. The author rewrites after each session. Over two or three drafts, weak thinking becomes visible and improvable — which is why Toyota treats A3 as a talent-development format. The output is a better engineer, not just a solved problem.

Three habits that kill an A3

1. Solution jumping. Countermeasures written before the root cause is verified. The author knew the answer before the analysis — the A3 is just dressing. Tell: countermeasure box is fuller than the root cause box.
2. No baseline. Current condition section is qualitative (“the process is slow”) instead of numeric (“58 s average cycle vs 45 s takt”). Without numbers, you cannot set a goal, verify a root cause, or confirm the countermeasure worked.
3. Blaming people. Root cause terminates at “operator made a mistake” or “team did not follow process.” This is almost always a stopping point, not a root cause. Ask one more why: why was it possible for that mistake to happen? The true root is usually in the process or the standard work, not the person.

What to read next

• All A3 articles — the category hub. Template, case-study library, and A3-vs-8D comparison are in production.
• The PDCA cycle — the Plan-Do-Check-Act logic that every A3 wraps.
• 5 Whys complete library — the tool that fills the root-cause box on most A3s.
• 8D problem solving — the customer-facing, formal cousin of A3.
• Corrective Action Plan (CAPA) — the structured action-plan format that pairs with the right half of an A3.
• How to write a problem statement — the craft behind a credible background section.