A3 Problem Solving
A3 problem solving is a structured, consensus-driven continuous improvement methodology developed by Toyota Motor Corporation. Built upon the Plan-Do-Check-Adjust (PDCA) management cycle, it guides teams to record the complete path of an operational issue on a single sheet of A3-sized paper. The document's left column establishes the operational reality through background analysis, current conditions, target states, and root-cause investigations. The right column outlines tested countermeasures, implementation schedules, effect confirmation, and standardized follow-up procedures, fostering cross-functional alignment and frontline coaching throughout the organization.
- One page overview
- The entire incident fits on one page. Readers grasp the sequence, causes, and safeguards in minutes.
- Left column diagnosis
- The left side defines the background, current state, and root cause before proposing any solutions.
- Root cause analysis
- The why-chain traces failures back to the procurement process rather than assigning individual blame.
- System countermeasures
- Retraining was rejected as ineffective. Physical segregation and software hard stops were adopted.
- Sustained follow-up
- The run chart tracks cabinet override rates returning to baseline. Improvement is verified with data.
Key facts
- Originator
- Toyota Motor Corporation
- Standard paper size
- 297 x 420 mm (ISO 216)
- North American equivalent
- 11 x 17-inch ledger paper
- Core framework
- PDCA (Plan-Do-Check-Adjust) cycle
- Left column focus
- Problem understanding and root-cause analysis
- Right column focus
- Countermeasures, implementation, and standardization
By Matthew Savas — Founder of Kaizumi. Reviewed 1 September 2026.
A3 problem solving is a structured, consensus-driven continuous improvement methodology developed by Toyota Motor Corporation. The method records the complete path of a problem, from initial identification through sustained resolution, on a single sheet of international standard A3 paper measuring 297 by 420 millimeters. Beyond its role as a standardized documentation template, the A3 process operates as a core management discipline built upon the PDCA (Plan-Do-Check-Adjust) cycle. The format documents the background, current condition, target goal, root-cause analysis, proposed countermeasures, implementation plan, and follow-up audit procedures. Limiting the summary to one page forces concise analysis, eliminates non-essential information, and establishes a standardized communication medium across all levels of an organization.
Origins and physical format
The practice of A3 problem solving emerged out of Toyota's desire to standardize communication and promote factual, data-driven operational decisions. The name derives directly from the international ISO 216 paper size standard, where an A3 sheet measures 297 millimeters in height by 420 millimeters in width. In North American contexts, an 11 by 17-inch ledger sheet is often substituted due to regional paper availability.
Toyota leadership recognized that lengthy, narrative reports often obscured key operational facts, delayed critical operational decisions, and discouraged cross-functional dialogue. By constraining the entire analysis to a single physical page, the author must isolate the essential facts, quantitative data, and logical connections that explain why a problem exists and how it will be corrected.
The physical format is structured into a logical sequence, traditionally arranged across two primary columns:
- Left column: Focuses on understanding the operational reality. It includes the background, current condition, target performance metrics, and root-cause analysis.
- Right column: Focuses on taking corrective action and sustaining gains. It contains tested countermeasures, the execution plan, and the follow-up audit schedule.
This spatial arrangement mirrors human reading patterns from left to right and top to bottom, guiding reviewers through the analytical progression from problem identification to resolution.
Structural alignment with the PDCA cycle
The A3 methodology translates the theoretical PDCA cycle into an explicit, visible series of operational steps. Every section on the sheet corresponds directly to a phase within the improvement cycle. For an instructional walkthrough of this sequence, review the guide to A3 problem solving, step by step.
The Plan phase occupies the entire left side of the document and frequently consumes the majority of the author's investigation time. Problem solvers must define the historical context, document the direct observations of the process, set measurable targets, and isolate systemic causes before formulating solutions.
The Do, Check, and Adjust phases occupy the right side. Countermeasures represent specific actions tested against identified root causes. The implementation plan details specific tasks, assigned owners, and fixed deadlines. The Check phase defines the quantitative confirmation steps used to measure performance against the target, and the Adjust phase outlines the standardized operational procedures and subsequent audits required to sustain the improvement.
Standard sections of an A3 report
An A3 document organizes problem solving into a standardized, logical flow. While specific organizational guidelines may adapt section titles, standard A3 reports contain eight key elements across the two columns.
Left column: Understanding the problem
The left side of the page builds the factual foundation for the investigation:
- Theme or title: A concise, descriptive statement identifying the specific problem, process, and location under review.
- Background: Explains why this specific issue is critical to business operations, safety, quality, delivery, or cost. It connects the local process failure to broader organizational objectives.
- Current condition: Documents the observable state of the process using direct observation data, process maps, defect tallies, and run charts. It details the gap between what is currently happening and what should happen.
- Target state: Defines the quantitative goal of the project. A valid target state specifies the performance metric, the desired numerical outcome, and the exact completion date.
- Root-cause analysis: Investigates the underlying failure modes of the system rather than its superficial symptoms. Analysts employ tools such as the 5 Whys and cause-and-effect diagrams to trace observable defects back to systematic procedural, equipment, or organizational breakdowns.
Right column: Designing and sustaining solutions
The right side of the page details the technical and operational actions required to close the performance gap:
- Proposed countermeasures: Specific interventions engineered to neutralize each root cause identified in the left column. When evaluating multiple technical options, teams often construct trade-off curves to select interventions that optimize performance criteria without introducing secondary operational failures.
- Implementation plan: A chronological schedule listing the specific work packages, assigned single-point owners, necessary resources, and target milestones.
- Effect confirmation: A side-by-side comparison of baseline performance metrics against post-implementation performance metrics. This section verifies whether the countermeasures produced the targeted result.
- Standardization and follow-up: Details the specific updates made to standard operating procedures, operator training matrices, and daily management tracking boards. It also defines the schedule for subsequent management audits to verify adherence.
The role of coaching and dialogue
A central premise of A3 problem solving is that the physical document is secondary to the thinking process it facilitates. Organizations that use the A3 method treat the document as a coaching tool that pairs an author with a designated mentor or supervisor.
The mentor does not provide answers or dictate solutions. Instead, the mentor asks open-ended, probing questions at each stage of the document's development:
- How did you confirm the current condition through direct observation at the work location?
- What data demonstrates that this cause is the primary driver of the defect?
- How directly does this countermeasure address the specific root cause identified?
- What indicators will confirm that the countermeasures are operating as designed?
This dialogue forces the author to return to the physical process, gather empirical evidence, and refine their analysis. The mentor-author interaction develops problem-solving competence throughout the workforce, transitioning employees from reactive troubleshooting to systematic, evidence-based improvement.
Additionally, the A3 serves as the primary instrument for nemawashi, the practice of gathering consensus before formally implementing changes. The author carries the draft document to affected stakeholders across different departments, integrating operational feedback and securing agreement before capital is committed or work processes are modified.
Worked operational example
The following example illustrates an A3 problem-solving sequence in a clinical pharmacy and nursing department. The incident and the figures are constructed to show the method, not drawn from a reported case.
Background and current condition
A hospital inpatient unit experienced a severe medication administration error during night-shift operations. A physician entered a digital order for 2 milligrams of hydromorphone for postoperative pain management. The automated medication dispensing cabinet dispensed a 10-milligram per milliliter vial instead of the standard 2-milligram per milliliter unit-dose vial. The administering nurse gave 20 milligrams of the drug, ten times the ordered dose.
The patient experienced acute respiratory depression. Emergency clinical rescue occurred via the administration of 0.4 milligrams of intravenous naloxone, which reversed the physiological harm within two minutes of administration. A process audit revealed that nursing staff overrode automated dispensing cabinet safety warnings on 21 percent of all opioid medication pulls.
Root-cause analysis
The team conducted a root-cause investigation using sequential 5 Whys analysis:
- Why was 20 milligrams administered? The nurse pulled two 10-milligram vials from the automated cabinet instead of the ordered dose.
- Why were 10-milligram vials selected? The 10-milligram high-concentration vials were placed in the open drawer bin adjacent to the 2-milligram unit doses.
- Why were high-concentration vials stocked in an open unit bin? Pharmacy central supply ran out of dedicated locking individual matrix bins during the prior week's restocking.
- Why did the automated cabinet release the medication without verified order matching? The nurse used the emergency cabinet override function.
- Why are cabinet overrides utilized for 21 percent of distributions? The digital interface response time between the provider order entry system and the cabinet database averaged 14 minutes, creating operational delays that nurses bypassed to prevent pain management delays.
Countermeasures and results
The team tested and executed three focused countermeasures:
- Physical isolation: Removed all multi-dose and high-concentration vials of hydromorphone from general unit dispensing cabinets, restricting high concentrations exclusively to the central pharmacy sterile compounding cleanroom.
- Interface latency remediation: Reconfigured the server network communication protocols, reducing the order verification latency from 14 minutes to 12 seconds.
- Override constraint: Restricted cabinet override permissions to certified charge nurses and rapid response team leaders, requiring dual-authentication biometric authorization.
During the subsequent six-month audit period, medication cabinet overrides fell from 21 percent of transactions to 4 percent of transactions. Zero repeated medication dosage errors or concentration mix-ups occurred across the operational monitoring period.
Common misconceptions and pitfalls
Organizations implementing the A3 methodology frequently encounter execution errors that diminish the effectiveness of the system:
- Treating the A3 as an administrative form: When organizations view the document merely as a reporting template, authors fill out the sections retrospectively to justify preselected solutions. This bypasses empirical observation and root-cause analysis.
- Restricting authoring to management: Reserving A3 authorship for managers, quality engineers, or technical specialists limits operational impact. Developing problem-solving competence throughout an organization requires operators and front-line staff to author A3s with supervisory coaching.
- Jumping to solutions: Authors often complete the background and immediately propose countermeasures on the right side of the sheet without validating the current condition or testing root-cause hypotheses on the left side.
- Formatting clutter: Attempting to bypass the physical constraint of the page by reducing font sizes or eliminating white space obscures critical data points and impedes rapid peer review.
Interactive tools
Draft a real A3 right here.
Try it yourself
Put A3 thinking to work: A3 Investigator drops you into a factory crisis and walks you from problem statement through root cause to countermeasure.
Play it yourself
Frequently asked questions
- What does the "A3" designation refer to in A3 problem solving?
- The name originates from the international ISO 216 paper standard, where an A3 sheet measures 297 by 420 millimeters. In North American facilities, an 11 by 17-inch ledger sheet is commonly substituted due to local paper availability. Toyota established this standard size to constrain reporting to one physical page, preventing operational facts from being buried in lengthy narrative documents.
- How does the two-column layout of an A3 report map to the PDCA cycle?
- The left column corresponds entirely to the Plan phase, requiring the author to document background context, observe current conditions, set target metrics, and isolate root causes. The right column covers the remaining three phases of the cycle: Do for testing countermeasures and scheduling implementation, Check for evaluating performance results against the target, and Adjust for standardizing operational procedures and scheduling follow-up audits.
- How is nemawashi practiced during the A3 problem-solving process?
- Nemawashi is the practice of gathering consensus and alignment across an organization prior to formally executing operational changes. The A3 author takes the draft document directly to stakeholders and frontline personnel across affected departments to collect feedback and resolve concerns. This dialogue ensures operational agreement before capital is committed or standard work procedures are modified.
- What is the mentor's role during the A3 problem-solving process?
- A mentor acts as a coach who guides the author through open-ended, probing questions rather than providing answers or dictating solutions. The mentor prompts the author to verify operational conditions through direct observation, validate root causes with empirical data, and confirm countermeasure effectiveness. This collaborative dialogue builds problem-solving competence across frontline personnel instead of reserving it for managers or technical specialists.
- What common mistakes undermine the effectiveness of an A3 report?
- A primary failure occurs when organizations treat the A3 as a retrospective administrative form used merely to justify predetermined solutions. Authors also frequently skip direct observation and root-cause analysis on the left side of the sheet to jump immediately to countermeasures. Finally, teams often undermine readability by shrinking fonts to crowd excessive data onto the page or by restricting authorship exclusively to managers.
Sources and notes
- ISO 216 — The 297 by 420 millimetre sheet the method is named for.