A3 Problem Solving Template (Lean A3 Report)
An A3 is a one-page story of a problem, told in the PDCA order: what is wrong, why, what we will do and how we will know. This template builds that page from a handful of fields so you can focus on thinking, not formatting.
Fill in
A3 Problem Solving Template
A3 Report: Late shipments from final assembly line 2
Owner: Assembly Supervisor Coach: Lean Manager Date: 2026-10-26
1. Background
Line 2 builds 60 percent of weekly orders. Customer delivery commitment is 98 percent on-time-in-full.
2. Current Condition
On-time shipping fell from 96 percent to 88 percent in eight weeks. Most misses are caused by missing sub-assemblies at the start of the shift.
3. Goal
Return to 98 percent on-time shipping within 10 weeks
4. Root Cause Analysis
| Level | Finding |
|---|---|
| Why 1 | Sub-assemblies are missing at the start of the shift |
| Why 2 | Sub-assembly cell builds to a weekly schedule, not to line consumption |
| Why 3 | No signal tells the cell what the line used |
| Root cause | No pull signal exists between the sub-assembly cell and Line 2, so the cell builds ahead of or behind actual use. |
5. Countermeasures
Introduce a two-bin kanban between the cell and the line; set bin quantity from daily usage; add a daily check of bin status at the shift start.
6. Implementation Plan
| Action | Owner | Due | Status |
|---|---|---|---|
7. Follow-up
Review on-time shipping weekly for 10 weeks. Confirm kanban compliance in gemba walks. Standardize in the work instruction if the target is met.
Review
The classic A3 fits on one sheet of 11 by 17 inch (A3) paper. Keep text short and add charts or photos by hand after export.
Pull A3 evidence straight from ERP
Optional: ask how late orders, scrap and downtime data can be queried for your A3 reports.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in the fields from left to right. Start with background and the current condition, using data and observations from the gemba. State a measurable goal. Use the why fields for a short cause chain, and write a root cause that you can act on. Countermeasures should address the root cause, not the symptom. Export to PDF or Word, then add charts and photos. The coach reviews the document with the owner in conversation, not by email.
- Write facts and numbers, not opinions
- Keep each box to a few lines
- Verify each why by looking at the process
- Name one owner per action
The PDCA logic behind A3
The left side of an A3 is Plan: background, current condition, goal and root cause. The right side is Do, Check and Act: countermeasures, implementation plan, results and follow-up. The format forces a short, logical chain from problem to action. A weak A3 jumps from the problem to the solution without showing the cause, which is the most common error and the one coaches look for first.
Example reading
In the sample, on-time shipping dropped because sub-assemblies were missing. The five whys trace back to a missing pull signal between the cell and the line. The countermeasure, a two-bin kanban, follows the cause directly, and the follow-up measure is the same one stated in the goal. When your own A3 reads like this, with each box leading logically to the next, the logic holds.
Common mistakes
Teams often write the countermeasure first and then back-fill the analysis, list five causes without checking any of them, or use the A3 as a status report after the work is done. Another pitfall is skipping the follow-up, so the team never learns whether the change worked. Update the A3 as a living document until the goal is met.
Frequently Asked Questions
What does A3 mean?
It refers to the international A3 paper size, roughly 11 by 17 inches, that Toyota used for these one-page reports. The size is a constraint that forces concise thinking.
How is an A3 different from an 8D?
Both are structured problem solving. 8D is common in customer complaint and supplier corrective action with eight formal steps. A3 is a broader lean thinking and coaching tool used for many problem types.
Who should write the A3?
The person closest to the problem should own and write it, with a coach who asks questions. If a manager writes it alone, the learning value is lost.
How many whys do I need?
As many as it takes to reach a cause you can act on, often three to five. Stop when the answer is a process or system condition rather than a person.
If the data behind your A3 sits in ERP and quality systems, we can help you pull it quickly, read-only and with the query visible.
Related Tools
Kaizen Event Charter Template
Fill in the fields and generate a one-page charter for a kaizen blitz, with scope, targets, team, timeline and approvals.
Discrete ManufacturingGemba Walk Checklist
A 28-point gemba walk checklist covering safety, quality, flow, standard work and people, with an exportable result.
Supply Chain & InventoryKanban Card Size Calculator
Calculate how many kanban cards or bins a part needs from daily demand, replenishment lead time, container size and safety factor.
Discrete Manufacturing5S Audit Checklist
A 30-point 5S audit covering Sort, Set in Order, Shine, Standardize and Sustain, with scoring you can export.
More Quality & Inspection tools
See all- A3 Problem Solving Report Template
- Rolled Throughput Yield Calculator
- Rolled Throughput Yield Calculator
- Cpk Confidence Interval and Sample Size Calculator
- X-bar and S Control Chart Limits Calculator
- Individuals and Moving Range (I-MR) Chart Limits Calculator
- Expected PPM Out of Specification Calculator
- Taguchi Loss Function Calculator
- Western Electric and Nelson Rules Reference