An A3 problem solving template is a one-page layout that guides a team through a problem in a logical order: background, current condition, goal, root cause analysis, countermeasures, implementation plan and follow-up. It follows the PDCA cycle and fits on one sheet of A3 paper, so the whole story of a problem can be read and reviewed at a glance.
At a glance
- What it is: a one-page layout that guides a team through a problem in a logical order.
- Sections: background, current condition, goal, root cause analysis, countermeasures, implementation plan and follow-up.
- When to use it: when a problem is too big to fix on the spot but small enough for one team to own.
- Related: what is an A3 report? and A3 thinking.
Download the free A3 problem solving template (PDF): one A3 landscape page with a prompt question printed in each of the seven sections. No sign-up needed.
Updated in November 2026 by the TeamAssurance team.
The A3 problem solving template at a glance
- Origin: Toyota, where problems and proposals were summarised on a single sheet of A3 paper (297 × 420 mm).
- Layout: seven sections read left to right. The left side is Plan; the right side is Do, Check and Act.
- Use it for: a recurring problem that one team can own and work through in roughly two to eight weeks.
- Inputs: facts gathered at the gemba, one measurable target and verified root causes.
- Output: countermeasures with owners and dates, checked results and an updated standard.
The template is the practical companion to our guide to A3 problem solving and the lean A3 method. For the thinking behind it, including coaching and how A3s compare with 8D and DMAIC, read the full guide. For a one-minute definition, see What is an A3 report?
When should you use an A3 problem solving template?
Use it when a problem is too big to fix on the spot but small enough for one team to own: a recurring defect, a machine that keeps stopping, a step that keeps causing rework. The template gives that team a structured approach, so the problem solving process is the same every time and anyone reviewing the page knows where to look. Quick fixes don't need an A3, and a customer complaint that needs formal containment and a formal response may call for 8D or a CAPA instead.
The page also stops a corrective action being chosen before anyone understands the problem. By the time the team reaches the countermeasures and the action plan, the reasoning that justifies them is already written down on the same sheet of paper.
What is on an A3 problem solving template?
The A3 problem solving template: all seven sections on one page, ready to download and print.
Across the top are spaces for a title, the owner and the date. The left side of the page covers Plan; the right side covers Do, Check and Act. Each section has a prompt question printed on it:
| Section | Question it answers |
|---|---|
| 1. Background | Why does this problem matter now? |
| 2. Current condition | What is actually happening? Use facts, data and sketches. |
| 3. Goal / target condition | What does good look like, and by when? |
| 4. Root cause analysis | Why is there a gap? Verify causes at the gemba. |
| 5. Countermeasures | What will we change to address each root cause? |
| 6. Implementation plan | Who does what, by when? |
| 7. Follow-up | Did it work? What will we standardise or adjust? |
Work through the sections in order. Each one depends on the one before: you can't set a sensible goal without knowing the current condition, and you can't choose good countermeasures without root causes verified through root cause analysis, whether that is the 5 whys or a fishbone diagram.
What does a filled-in A3 example look like?
The example below shows a completed A3 for a recurring labeller jam on a packing line. The line, numbers and causes are invented for illustration.
Notice how little text it needs. The current condition is a short summary of four weeks of jam data, the goal is one measurable line with a date, and every countermeasure traces back to a verified root cause. The full guide walks through this example section by section.
Which A3 templates are there for problem solving?
Most A3 templates for problem solving share the same seven sections, so the choice comes down to what you are solving and how you will track it:
- Standard A3 problem solving template: the free PDF on this page, for a recurring problem one team can own.
- Filled-in A3 example: the labeller jam above shows how much detail each section needs. For the definition, see what is an A3 report?
- A3 process improvement template: the same layout pointed at a process rather than a single defect (see below).
- A3 template with a calendar view: for keeping track of many A3s and their review dates; see the A3 report template with calendar view.
How do you fill in an A3 problem solving template well?
The template is only a starting point. What makes an A3 work is the thinking that goes into it.
Go to the gemba
Before filling in any section, go to where the work happens. Observe the process, talk to the people involved and collect real data. An A3 written in a meeting room is rarely effective.
Spend most of your time on the left side
Resist the urge to jump to solutions. Time spent understanding the current condition and verifying root causes is what makes the countermeasures work.
Use visuals
Charts, sketches and simple process maps say more than paragraphs. Use the limited space for a trend chart, a Pareto chart or a fishbone diagram rather than text.
Write in pencil, and share early
Expect to redraft. Share your draft with colleagues, your mentor and the people affected. The back-and-forth, known as catchball, is where much of the learning happens and where agreement is built.
Follow through
An A3 isn't finished when the actions are done. It is finished when the results have been checked against the goal and the change has been written into standard work.
How do you use an A3 template for process improvement?
An A3 process improvement template is the same seven-section A3 template pointed at a process instead of a one-off defect: the page tells the story of how a process works today, what it should achieve and which changes will close the gap. It suits slow hand-offs, long lead times, rework loops and steps that vary from person to person, and it is a natural tool for process improvement and continuous improvement work.
- Background: name the process, who depends on it and why it matters now.
- Current condition: show how the process really runs, using a simple flow sketch or value stream map and measures such as lead time, error rate or waiting time.
- Goal: one measurable target for the process, with a date.
- Root cause analysis: find why the process misses the target, not who is to blame.
- Countermeasures and plan: the specific changes to steps, roles or tools, each with an owner and a due date.
- Follow-up: re-measure, and write what worked into standard work so the gain holds. Larger ideas can become a kaizen event.
What are the most common A3 template mistakes?
- Jumping to solutions. Filling in countermeasures before the root causes are understood.
- No data. Making claims about the current condition without evidence.
- Too much text. Walls of writing defeat the purpose of one page. Be visual and concise.
- A vague goal. "Improve quality" can't be checked. State a measure, a target and a date.
- Working alone. A3 problem solving is a team activity, guided by a mentor.
- No follow-up. Abandoning the A3 after the countermeasures section, so nobody knows if it worked.
Should you use a paper or digital A3 template?
Paper A3s are quick to start, easy to sketch on and work well pinned up next to the line. Their weakness shows as the number of A3s grows: it becomes hard to see which are on track, which actions are overdue and when reviews are due. A digital template keeps the same seven sections but adds a calendar view of A3 activities and review dates, and makes it easier to share a finished A3 with other teams.
How TeamAssurance helps
In TeamAssurance, A3 problem solving is one of the structured methods in the continuous improvement capability, alongside PDCA, DMAIC and the 5 whys. An A3 is raised as an improvement project, usually from a red measure on a tier board, with the problem statement, current state, root cause analysis, target state, countermeasures and implementation plan recorded against it. Its actions appear on the owners' boards and progress is reviewed through tiered daily management, so the A3 stays visible after it is written and is closed only once the results have been checked.
Further reading: John Shook, Managing to Learn (Lean Enterprise Institute, 2008) and Durward K. Sobek II and Art Smalley, Understanding A3 Thinking (Productivity Press, 2008) are the two standard references on the A3 method.
Want to see how TeamAssurance tracks A3s through daily tier meetings? Book a demo.
