An A3 problem-solving review walks a team through a single sheet of paper that tells the whole story of a problem and its solution. Named for the paper size, the A3 is a cornerstone of Lean thinking: it forces clear, structured reasoning through the plan-do-check-act cycle and turns problem-solving into a teachable discipline rather than a scramble.
Use an A3 review for any problem important enough to warrant rigorous root cause thinking, from a quality defect to a missed Hoshin target. The review happens as the A3 develops and again when results come in. It doubles as a coaching tool, since the questions a reviewer asks teach the owner how to think.
Keep it small: the A3 owner, a coach or mentor, and the few stakeholders who understand the problem or own part of the solution. Three to eight people is plenty. The owner drives the A3; everyone else sharpens it through questions.
The owner walks the A3 in order: background and problem statement, current condition with data, the goal, and the root cause analysis. Spend real time on root cause, since countermeasures aimed at symptoms always fail. Review the countermeasures, the implementation plan, and how results will be checked and followed up. Throughout, the coach asks questions rather than giving answers, because the value of A3 is the thinking it develops, not just the document it produces.
Build problem-solving as a discipline. Run it in OrgTP and keep each A3 problem, root cause, and countermeasure tracked to closure.
60 minutes total · 6 sections
In Lean manufacturing and continuous improvement frameworks (pioneered by Toyota), the A3 process is the gold standard for structured problem-solving. The name comes from the international A3 paper size - because the core philosophy of the framework is that the complete story of a problem, its analysis, and its solution must fit on a single sheet of paper.
If your team struggles with disorganized problem-solving, jumps to conclusions without analyzing data, or fails to document lessons learned, implementing the A3 process will transform your operational discipline.
This comprehensive guide provides a battle-tested A3 Problem-Solving Template and a step-by-step review agenda to help your team analyze root causes, implement countermeasures, and foster a culture of continuous learning.
An A3 Problem-Solving Review is a structured, 60-minute collaborative session where a problem owner presents their A3 report to a coach, leadership team, or key stakeholders.
Rather than a formal presentation, the A3 review is a coaching and alignment session. It follows the classic Plan-Do-Check-Act (PDCA) cycle to ensure the team is solving the right problem, using data-driven analysis, and implementing sustainable countermeasures.
To ensure a rigorous, data-driven discussion that focuses on coaching and root-cause thinking, we recommend a structured 60-minute agenda:
| Time | Agenda Item | Objective |
|---|---|---|
| 00:00 - 00:10 | Background & Problem Statement | The owner presents the business context and defines the specific problem being addressed. |
| 00:10 - 00:20 | Current Condition & Goal | Review the data representing the current state and align on the measurable target. |
| 00:20 - 00:35 | Root Cause Analysis | Deep-dive into the analysis (e.g., Five Whys). Verify that the analysis is based on facts, not assumptions. |
| 00:35 - 00:45 | Countermeasures Evaluation | Review the proposed solutions and verify that they directly address the identified root causes. |
| 00:45 - 00:55 | Implementation & Check Plan | Review the action plan, timeline, and the mechanism for measuring results (the "Check" phase of PDCA). |
| 00:55 - 01:00 | Coaching Feedback & Close | The coach or stakeholders provide feedback, document lessons learned, and approve the next steps. |
An A3 report cannot be written from an office or a conference room. The owner must go to the "Gemba" - the actual place where the work is done - to observe the process, gather data, and talk to the people executing the work. Facts on an A3 must be verified firsthand.
In the PDCA cycle, the "Plan" phase consists of the first four sections of the A3 (Background, Current Condition, Goal, and Root Cause Analysis). High-performing teams spend 80% of their time and effort on these sections. If you define the problem correctly and find the true root cause, the countermeasures are usually obvious.
An effective A3 report uses charts, graphs, process maps, and diagrams instead of dense blocks of text. Anyone in the organization should be able to look at the A3 and understand the complete story of the problem and solution in under 5 minutes.
An A3 is a structured problem-solving tool and report format pioneered by Toyota. It fits the complete story of a problem, its analysis, countermeasures, and follow-up plan on a single sheet of A3-sized paper, following the Plan-Do-Check-Act (PDCA) cycle.
Gemba is a Japanese term meaning "the real place." In business and Lean manufacturing, it refers to the place where value is created (e.g., the factory floor, the customer support desk, or the software development environment) where problems should be observed firsthand.
The PDCA (Plan-Do-Check-Act) cycle maps perfectly to the A3: Sections 1-4 represent "Plan" (defining the problem and root cause), Section 5 represents "Do" (implementing countermeasures) and "Check" (measuring results), and Section 6 represents "Act" (standardizing the solution and sharing lessons).
The A3 is written by the individual closest to the problem (the owner) and reviewed in a collaborative session with a coach (manager or Lean specialist) and key stakeholders who are impacted by the process.
Stop copying agendas into a doc every week. OrgTP runs your meetings live — scorecard, rocks, issues, and to-dos all in one place, with your AI agents in the room.