Knowledge Base · Solutions
What is an A3, and how do I write one?
An A3 is a problem-solving report written on a single sheet of A3 paper, 297 by 420 millimetres, roughly 11 by 17 inches. Developed at Toyota and built on the PDCA cycle, it tells the whole story of a problem in seven sections: background, current condition, goal, root cause analysis, countermeasures, implementation plan, and follow-up.
The discipline of the A3 is the single page. A problem that cannot be explained clearly on one sheet has usually not been understood yet, so the format forces hard choices about what matters. Diagrams, simple charts, and a sketch of the process carry more weight than paragraphs of text. When the A3 is finished, anyone affected by the problem can read the entire chain of reasoning in a few minutes and challenge the exact step where the logic is weak.
The sections run in a fixed order that follows the PDCA cycle:
- Background: why the problem matters and why it is being taken up now, stated in the terms of the work: what it costs, whom it affects, and what happens if it is left alone.
- Current condition: how the process actually runs today, drawn from direct observation where the work happens, with the gap between the current condition and the expected condition shown in numbers or a diagram.
- Goal: the improvement being aimed at, stated as a measurable target with a date.
- Root cause analysis: the causes underneath the symptoms, investigated with tools such as the 5 Whys or a fishbone diagram and tested against evidence, until the team reaches a cause it can act on.
- Countermeasures: the changes proposed against those root causes. The lean term is deliberate: a countermeasure is the best response known today, not a permanent solution, and it stays open to revision when the check shows it is not working.
- Implementation plan: the countermeasures converted into scheduled steps, each with a named owner and a date.
- Follow-up: the point at which results are checked against the goal, the learning is written down, and whatever worked is standardised or the plan is adjusted and run again.
The sheet is only part of the method. An A3 is developed through conversation: the author drafts it, then a coach or manager works through it section by section, asking how the author knows each claim and what evidence sits behind it. The draft is normally revised several times as the understanding sharpens. The coach's role is to test the thinking rather than supply the answers, so the skill being built belongs to the author. Because the people affected by the change are brought into that conversation while the A3 is forming, agreement about the countermeasures tends to exist before implementation begins.
The Introduction to Continuous Improvement in the Workplace shows A3 thinking at work in its opening case study: a cross-functional team at a large insurance company used it to define a compliance problem, analyse its root causes, and develop countermeasures, before designing the replacement process. A3s that hold up tend to share two features: a current condition drawn from real observation rather than opinion, and a goal stated as a number that can later be checked.
Related questions
Source: Continuous Improvement in the Workplace, Introduction (FACTA compliance case study); A3 method after Shook, Managing to Learn (Lean Enterprise Institute, 2008).