New to this topic?
Read these first to get the most out of this guide:
The 7 Sections of an A3
The A3 is read left-to-right, top-to-bottom, following the PDCA cycle:
1. Title / Theme
A specific, actionable problem statement. Not “Improve quality” but “Reduce sealant rework at Station 7 from 18% to under 5% by end of Q2.” The title should tell the reader exactly what problem is being solved and what success looks like.
2. Background / Context
Why does this problem matter? Connect it to business impact: cost, delivery, quality, safety. Use 2 to 3 sentences maximum. Example: “Station 7 sealant rework costs $340K/year in labor and delays 2 aircraft per month by 3 days each.”
3. Current Condition
What is actually happening now? Data, not opinions. Include a visual: Pareto chart, process map, trend chart, or data table. This is where the author proves they went to the floor and measured. “18% rework rate over the last 8 weeks, with 62% of rework caused by insufficient fillet radius.”
4. Target Condition
What does “solved” look like? A specific, measurable target with a deadline. “Reduce rework from 18% to ≤5% by June 30.” The gap between current and target drives the analysis.
5. Root Cause Analysis
Why does the gap exist? Use 5-Why, fishbone, or fault tree analysis to identify true root causes (not symptoms). Each root cause should connect logically from the current condition data. “Insufficient fillet radius caused by: (1) sealant gun nozzle wear (not replaced on schedule), (2) operator technique variation (no standard work for bead application).”
6. Countermeasures
Specific actions that address each root cause. Each countermeasure has: What, Who, When, and how you will verify it worked. Not “improve training” but “Create standard work for sealant bead application (IE, by May 15) and train all Station 7 operators using TWI JI method (team lead, by May 30).”
7. Follow-Up / Results
After implementation: did the countermeasures work? Show the same metric from Section 3, updated with post-implementation data. If the target was not reached, why not? What is the next experiment? This section closes the PDCA loop.
A3 as a Coaching Tool
The deepest value of A3 is not the document. It is the coaching conversation between the author and their mentor. The mentor does not fill out the A3. They ask questions:
| Section | Mentor Questions |
|---|---|
| Background | “Why is this important to the business? What happens if we do nothing?” |
| Current Condition | “How do you know this? Where did the data come from? Did you go see?” |
| Root Cause | “How do you know this is the root cause and not a symptom? What evidence supports this?” |
| Countermeasures | “How will you know this worked? What could go wrong? Is there a faster way to test?” |
| Follow-Up | “Did you confirm the result? What did you learn? What would you do differently?” |
This coaching dialogue develops the author’s problem-solving capability, which is the real output. The A3 paper is a byproduct. This is why A3 thinking is inseparable from coaching for improvement.
Common A3 Failures
The desk A3: Written entirely from ERP data without visiting the floor. Always wrong. The solution-first A3: Author already knows the answer and works backward to justify it. Defeats the purpose. The novel A3: 500 words per section, 8-point font, no one will read it. Brevity is a feature, not a limitation. The orphan A3: Completed, filed, never followed up. Section 7 is the most important section.
The Bottom Line
A3 is PDCA on one page: define the problem with data (Plan), implement countermeasures (Do), verify results (Check), standardize what works (Act). The constraint of one page forces clarity. The coaching dialogue develops capability. And Section 7 (follow-up) closes the loop that makes improvement stick. Next: Root Cause Analysis Toolkit, the methods that power Section 5 of your A3.
Frequently asked questions
What is an A3?
An A3 is a structured problem-solving document that captures the entire problem-solving process on a single A3-sized sheet of paper (11×17 inches). It forces concise thinking: if you cannot explain the problem, analysis, and solution on one page, you do not understand it well enough. The format follows PDCA: the left side is Plan (problem, current state, target, root cause), the right side is Do/Check/Act (countermeasures, implementation plan, results, follow-up).
Why one page?
Brevity forces clarity. A 30-slide PowerPoint can hide fuzzy thinking behind pretty graphics. A one-page A3 cannot. Every word must earn its place. The constraint of one page forces the author to distill the problem to its essence, identify the true root cause (not a symptom), and propose countermeasures that are specific, actionable, and measurable.
Is the A3 a document or a thinking process?
It is a thinking process that happens to produce a document. The value is not the paper. It is the structured thinking the author goes through to fill it out. An A3 written at a desk without going to the floor is worthless. A3 thinking requires: go see the problem, gather data, analyze root causes, test countermeasures, and verify results. The paper records this journey.