A3 BuilderA3 Problem-Solving Report

What is an A3?

An A3 report — named for the ISO paper size (297 x 420 mm, landscape) — is a one-page problem-solving story that follows the Plan-Do-Check-Act (PDCA) cycle from start to finish. The A3 template was developed inside Toyota as a discipline for both thinking and communication: forcing every problem, analysis, and plan onto a single sheet of paper compels the author to understand the situation deeply enough to explain it simply. It is not a form to fill in after the fact. The act of building the A3 problem solving template is the thinking process itself — the document is evidence that structured reasoning happened, not a summary of a decision already made. Toyota coaches historically carried A3 reports instead of PowerPoint decks precisely because one page cannot hide shallow thinking behind extra slides.

The sheet divides naturally into two halves that mirror the PDCA cycle. The left side covers the understand phase: Background (why this problem matters now), Current Condition (what is actually happening, with data), Goal or Target (the measurable outcome you are pursuing), and Root Cause (why the gap between current and target exists). The right side covers the act phase: Countermeasures (what you will do about the root causes), Implementation Plan (who does what by when), and Follow-up (how you will confirm the countermeasures worked). This left-right structure means a reader can scan the current condition on the left and the proposed countermeasures on the right in the same glance, immediately checking whether the response matches the problem. That visual accountability is something no multi-page report provides. When used alongside kaizen events and iterative improvement cycles, A3 thinking builds the team's capacity to solve harder problems over time.

How to fill out each section

1. Background. Open by linking the problem to a specific business goal — safety, quality, delivery, or cost — so the reader understands immediately why this problem deserves attention and resources now, not later.

2. Current Condition. Describe what is actually happening with facts and numbers gathered at the gemba (where the work occurs), not opinions or assumptions. Graphs, process sketches, and data tables all belong here; interpretations do not.

3. Goal / Target. Make the target measurable and dated. “Reduce changeover from 45 to 20 minutes by March 31” is a target; “improve changeover” is a wish. A clear target defines when the A3 is done and is the reference point for the follow-up check.

4. Root Cause. Ask why repeatedly — the five whys technique works well here — and stop at a process cause you can act on, not a person to blame. If your final “why” points to an individual's failure, keep asking; the process allowed that failure to happen.

5. Countermeasures. List the actions you will take to address the root causes identified in section 4, not just the symptoms. Each countermeasure should trace to at least one root cause, and you should prefer small, reversible experiments that can be tested quickly over large irreversible changes.

6. Implementation Plan. Every action gets one owner (a specific name, not “the team”) and one due date. A plan with shared ownership is a plan with no ownership. This section transforms countermeasures into commitments.

7. Follow-up. Schedule the confirmation check before you begin implementation, not after. If the gap between current and target still exists at the review date, the A3 cycles again — this is the Check-Act portion of PDCA and is what keeps the document alive rather than filed away.

A3 vs. 8D

The A3 and the 8D (Eight Disciplines) report are both structured problem-solving frameworks, but they serve different purposes and come from different contexts. The A3 is a flexible thinking and communication discipline rooted in PDCA. It fits any improvement problem — a safety incident, a quality defect, a delivery miss, a cost overrun — and is as useful for a maintenance team as it is for an engineering group. The quality of the A3 lives or dies on the depth of the current-condition analysis and the rigor of the root-cause section: a well-drawn current condition forces the team to truly understand the gap before reaching for countermeasures.

The 8D is a formal corrective action process that is typically customer-mandated, most commonly in automotive and regulated manufacturing contexts. It follows eight prescribed disciplines: form the team, describe the problem, contain it (the D3 containment step is explicit and early — a step the A3 does not require), identify root cause, verify root cause, implement corrective action, prevent recurrence, and recognize the team. When a customer demands an 8D response, complete the 8D — it is a contractual and quality management system requirement. For internal improvement work where no customer is mandating a format, the A3 keeps the team focused on the problem rather than the paperwork, and its one-page constraint tends to produce clearer thinking than the 8D's structured narrative format.

Related

• 5 Whys Builder — work the Analysis box properly before it goes on the A3
• A3 Problem Solving in Healthcare — a worked field guide
• A3 Problem-Solving RPG — practice the thinking in a story-driven game
• Fishbone Diagram Builder — structure the root cause analysis for section 4
• 5S Audit Tool