Idea management guides

A3 Problem Solving: The A3 Report Step by Step, With a Template and Example

A3 problem solving explained: what goes on the one-page A3 report, the eight steps, a worked example, A3 vs 8D and DMAIC, and how a coach reviews an A3.

8 min read

A3 problem solving is a way of working through a problem on a single sheet of paper: what the problem is, what is happening now, what causes it, what you will do about it, and whether it worked. It takes its name from the paper size, A3 (297 × 420 mm, about 11 × 17 inches), and it comes from Toyota, where it is used as much to teach people to think as to solve problems.

The one-page limit is the point. A problem you cannot explain on one sheet is a problem you do not understand yet. An A3 forces the writer to be clear, and gives everyone else a single page to discuss instead of a 30-slide deck.

What is an A3 report?

An A3 report tells the story of one problem from left to right. The left side describes the problem and its cause; the right side describes the fix and the follow-up. It is the PDCA cycle written down: the left half is Plan, the right half is Do, Check and Act.

An A3 is not a form to fill in once. It is a document that changes as the writer learns more, and a conversation tool between the person who owns the problem and a coach or manager who asks questions. John Shook, who learned the method as a Toyota employee in Japan in the 1980s, built his book Managing to Learn around exactly that conversation.

What goes on an A3? The A3 template

Most A3s use the same sections, in this order:

Section What to write Questions to answer
Title The problem in a few words, not the solution Does the title describe a problem, or have we already decided the answer?
Background Why this problem matters to the business now Why should anyone spend time on this?
Current condition What is happening, with facts, numbers and a simple drawing What do we see at the gemba? How big is the gap?
Goal The target, with a number and a date What does good look like, and by when?
Root cause analysis Why the problem happens, often with 5 whys or a fishbone diagram Have we found the cause, or just a symptom?
Countermeasures What will be changed, linked to each cause Does each countermeasure address a cause we found?
Implementation plan Who does what, by when Is every action owned and dated?
Follow-up How the result will be checked, and what happens next How will we know it worked? What if it did not?

The left side (title to root cause) is usually the hardest and the most valuable. Many weak A3s have a thin left side and a long list of actions on the right.

What are the eight steps of A3 problem solving?

Many companies teach A3 as eight steps, a version often linked to Toyota’s practical problem-solving training:

  1. Clarify the problem. Describe the gap between how things should be and how they are, with facts.
  2. Break down the problem. Narrow it to a specific place, product, shift or failure where you can act.
  3. Set a target. A measurable goal with a date.
  4. Analyse the root cause. Go and see, ask why until you reach a cause you can act on, and check it with data.
  5. Develop countermeasures. Options that address the cause, not just the symptom.
  6. Carry out the countermeasures. On a small scale first, with an owner for each action.
  7. Check results and process. Did the numbers move? Did we do what we planned?
  8. Standardise and share. Make what worked the new standard, and share the lesson with other areas.

Steps 1 to 5 fill the left side of the sheet and the first half of the right; steps 6 to 8 complete it.

What does an A3 look like in practice?

Here is a typical example from a distribution centre, simplified.

Title: Damaged parcels reaching customers. Background: complaints about damaged goods have doubled this year and cost refunds and repeat customers. Current condition: 2.4 percent of parcels arrive damaged, against 1 percent last year; 70 percent of the damaged parcels are heavy items packed in the smallest box size. Goal: below 1 percent within three months. Root cause: the packing screen suggests a box by size only, not by weight; packers on the evening shift, who are mostly new, follow the suggestion. Countermeasures: add weight to the box rule; a visual guide at each packing station; a short training session for new packers. Implementation plan: IT changes the rule in two weeks; the team leader makes the guide; training starts on the evening shift. Follow-up: weekly damage rate by shift for eight weeks, then the new rule becomes the standard on all sites.

Notice where the cause was found: in the packing screen, not in the packers. A good A3 looks at the process before it looks at people.

How does a coach review an A3?

In the Toyota way of working, an A3 is reviewed by a coach or manager who asks questions rather than giving answers. Common questions:

  • What is the actual problem? How do you know?
  • Have you seen it yourself?
  • What is the cause, and what is your evidence?
  • How does each countermeasure address the cause?
  • Who agreed to this plan? Who still needs to?
  • How will you know if it worked?

The questions are the training. Over a few A3s, the writer learns to ask them before the coach does.

What is the difference between A3, 8D and DMAIC?

Method What it is Typical use
A3 One-page problem-solving report built on PDCA, with a coach Everyday problems, teaching people to think through a problem
8D Eight disciplines, a structured team method common in automotive and supplier quality Customer complaints and quality failures that need a formal report
DMAIC Define, Measure, Analyse, Improve, Control, the Six Sigma method Complex problems with lots of data and variation

All three follow the same logic: understand the problem, find the cause, fix it, check it and lock it in. In Six Sigma teams, an A3 is often used as the one-page summary of a DMAIC project.

What are the most common A3 mistakes?

  • Starting with the solution. A title like “Introduce a new packing screen” means the answer was decided before the problem was understood.
  • A thin current condition. Without facts and numbers, the rest of the A3 rests on opinion.
  • Stopping at the first why. “Human error” is rarely a root cause. Ask why the process allowed the error.
  • Writing it alone at a desk. A3s are written at the gemba, with the people who do the work, and discussed with the people affected.
  • Treating it as a form. An A3 that is filled in once and filed teaches nothing. It should change as you learn.
  • No follow-up. If nobody checks the result, the A3 is a plan, not a solution.

How do employee ideas fit into A3 problem solving?

Most A3s start with a problem someone noticed, and many of the best countermeasures come from the people closest to the work. The question is whether those problems and ideas reach the person writing the A3.

In Hives, people report a problem or suggest an improvement in about two minutes from a phone or a QR code on the wall. A collection’s steps and questions can follow the A3: the problem and current condition on the form, the cause and countermeasures in a review step, the result in a follow-up step. Everyone who raised the problem sees what was found and decided, which keeps them reporting the next one. Our guides on the 5S method and kaizen cover the habits that surface problems in the first place.

Frequently asked questions

What is A3 problem solving?

A3 problem solving is a structured way to work through a problem on one A3-sized sheet: background, current condition, goal, root cause, countermeasures, plan and follow-up. It comes from Toyota and follows the PDCA cycle.

Why is it called A3?

Because it fits on one sheet of A3 paper, 297 × 420 mm, roughly 11 × 17 inches. The size limit forces the writer to be clear and concise.

What are the eight steps of A3 problem solving?

Clarify the problem, break it down, set a target, analyse the root cause, develop countermeasures, carry them out, check results and process, and standardise and share what worked.

Is A3 part of Six Sigma?

A3 comes from Toyota and lean, not Six Sigma. Many Six Sigma teams use an A3 as the one-page summary of a DMAIC project, because it tells the same story on a single sheet.

Who should write an A3?

The person who owns the problem, usually with a coach or manager who reviews it through questions. The writer should spend time where the problem happens and involve the people who do the work.

How long does an A3 take?

A simple A3 can be written in a few days. Problems that need data collection and a trial often take four to eight weeks from first draft to confirmed result, with the A3 updated along the way.

Sources

  • John Shook, Managing to Learn: Using the A3 Management Process to Solve Problems, Gain Agreement, Mentor and Lead, Lean Enterprise Institute, 2008
  • Durward K. Sobek II and Art Smalley, Understanding A3 Thinking: A Critical Component of Toyota’s PDCA Management System, Productivity Press, 2008

More guides like this