A3 report: solving a problem on one sheet
The A3 is the one-page report Toyota uses to think through a problem from start to finish: background, current situation, goal, root cause, countermeasures, plan and follow-up. What matters is not the paper but the conversation between the person who writes it and the person who guides them.
- Topic
- Problem Solving
- Reading time
- 8 minutes
- Sources
- 1 guide, 1 book
In one line
An A3 forces you to put on one sheet, in order and backed by data, everything you need to understand a problem and decide what to do about it.
What it is
The guide from analisisdecausaraiz.com presents the A3 report as one of the Lean management tools developed within the Toyota Production System. It picks up the description by Isao Kato, a former Toyota manager: a hybrid between the PDCA cycle and Toyota's philosophy of making things visible. The name comes from the paper size (A3, 29.7 by 42 cm), and the guide mentions a legend according to which Taiichi Ohno refused to read past the first page of any report: that is why the A3 is a single-page report. The guide itself presents it as a legend.
The central point the guide stresses: what matters in the A3 is not the paper or the format, but the process. It represents the spirit of lively debate, mutual understanding and confirmation of agreement. The person who has the problem (the "owner") fills in the boxes as they go and talks them through with colleagues and with a mentor; managers act as mentors, and that aligns interests across people and departments. Through the A3, one person is given the authority and the consent to get things done.
How to apply it: the seven boxes
According to the guide, the author of the A3 answers, in sequence:
- Business context: clarify the problem and describe it briefly; it is the starting point that gives a basis for the following steps.
- Current situation: describe how the area where the problem appears stands today. You can map the area's processes to get a broader perspective and identify the root cause.
- Desired outcome: set the goals. The guide clarifies that at this step you do not yet have the full picture, so after reaching "confirmation of effect" you can come back here and add detail.
- Root cause analysis: a very important step. Fighting the problem right away means treating only the symptoms and leaving the cause intact, so it can come back in greater proportion. Techniques such as the 5 Whys, the Ishikawa diagram or the Pareto chart are used.
- Countermeasures: the proposed solutions, which must lead to a clear understanding of how the goal will be achieved.
- Action plan: a list of actions to implement the countermeasures, with an owner and a due date.
- Follow-up process: measure the results and confirm the effect of the countermeasures. If they differ from what was expected, the plan is modified, reimplemented and followed up; if the effect is positive, it is communicated to the rest of the organization and turned into a standard.
Try it
It is saved in your browser. To print it on one sheet, use Ctrl+P.
Real example
The guide does not include a numeric case, so this is an illustrative (made-up) example to show how to fill it in, with a typical maintenance problem:
- Context: the packaging output conveyor on line 2 stops about 3 times per month and halts packaging.
- Current situation: in the last quarter, 9 stoppages, all because the belt was off-track; 35 minutes on average per stoppage.
- Goal: no more than 1 stoppage per month for this reason, starting next month.
- Root cause (5 Whys): the belt drifts because a roller seizes, it seizes because it is not greased, it is not greased because the grease point is covered by a guard.
- Countermeasures: relocate the grease point with an accessible extension and add the task to the preventive plan.
- Action plan: who, what and by when, one per line.
- Follow-up: count the conveyor stoppages every week for three months; if the goal is not reached, go back to box 4.
Template to use
The interactive template is above and also in the A3 report tool. To take it to a printed sheet, a practical format is to divide the paper into two halves: boxes 1 to 4 on the left (understanding the problem) and boxes 5 to 7 on the right (what to do and how to verify it). That layout is a common convention, not a rule of the guide.
To go deeper, there is a book dedicated to the topic:
Benefits
- It forces you to understand the problem before proposing solutions, and to rely on data.
- It puts on one page what is needed to decide: it works for talking with management and with the team.
- It turns every problem into an opportunity for learning and mentoring.
Limitations to keep in mind
- Filling in the boxes without talking with the mentor and with the people in the area reduces it to filling out a form.
- It does not replace analysis: box 4 requires root cause techniques (5 Whys, Ishikawa, Pareto) so that it is more than an opinion.
- For customer quality problems that need immediate containment, the 8D method is more specific.
In summary
The A3 is a thinking method in seven steps, written on one sheet, that goes from "what is happening and why it matters" to "how we verify that it worked". Its value is not in the paper, but in the conversation it forces you to have.
More on Problem Solving
5 Whys: reaching the root cause by asking why, 5 times
Asking "why?" in a chain, five times, to stop attacking symptoms and reach the real root cause of a problem.
8D: the 8 disciplines for solving problems
8D is the 8-step method that Ford made the standard in the automotive industry: contain the damage right away, find the root cause afterward, and document that the problem will not come back.
DMAIC: the 5 phases of a Six Sigma project
DMAIC is the 5-phase structure (Define, Measure, Analyze, Improve, Control) that Six Sigma uses to organize a data-driven improvement project from start to finish.