Prozanta Template
A3 problem-solving
Structured problem-solving on a single page
Title:
Owner:
Date:
How to use this template
An A3 is Toyota's method for getting an entire problem — background, analysis, solution and follow-up — to fit on a single sheet (A3 size). The pressure to be concise forces you to understand the problem before you jump to solutions. The A3 is both a working document and a dialogue tool.
When do you use it?
For larger or recurring problems that require analysis and several people involved — too complex for a single 5 Why, but scoped enough for one sheet.
Time & rhythm
Filled in over several days as you investigate. The left side (problem + analysis) before the right side (solution) — never fill in the solution first.
Step by step
- Background: why is the problem important to solve now?
- Current state: describe it with facts and figures — go to the gemba.
- Target state: what is the concrete, measurable goal?
- Root cause: find the cause with 5 Why or a fishbone.
- Countermeasures: what do you do, and why exactly that?
- Plan, verification and standardisation: who does what when — and did it work?
Watch out
- Fill in the left side (understanding) before the right (solution) — that's the whole point.
- Use facts from the gemba, not assumptions from the meeting room.
- The A3 is owned by one person, but built in dialogue with those who know the process.
Example
A good A3 can be read in five minutes and tells a coherent story: "Here's the problem, here's why, here's what we're doing, and this is how we'll know if it works."
Method: Toyota; cf. John Shook, “Managing to Learn” (2008).
Read: Quality systems that work →1. Background
Why is this problem important to solve now?
2. Current state
Describe the problem with data and facts
What is happening?
KPI impact
Chart / process flow
[ Diagram / Sketch ]
3. Target state
Goal (specific and measurable)
Deadline
4. Root cause analysis
5 Why — dig to the real cause
Root Cause:
5. Countermeasures
| Action | Owner | Date |
|---|---|---|
6. Implementation plan
Resources / budget
Risks
Communication to the team
7. Verification of effect
Before (baseline)
After (result)
Did we hit the goal?
8. Standardisation & follow-up
Updated procedures / SOP
Training of employees
What can others learn?
Next PDCA cycle (if needed)
Approved by
Date
Prozanta · prozanta.dk
A3 problem-solving
Version: Rev: