Definition
An A3 is a structured process for problem solving, proposals, and status reporting that captures the entire story — background, current condition, problem statement, analysis, countermeasures, implementation plan, and follow-up — on a single sheet of A3-sized paper (297mm x 420mm, approximately 11” x 17”). The name comes from the international paper size.
But an A3 is not fundamentally about the paper. The Lean Enterprise Institute identifies eight facets of A3: a standard paper size, a template, a storyboard, a report, a problem-solving methodology, a management discipline, a way of thinking, and an alignment tool. The paper is just the physical constraint that forces conciseness, visual communication, and structured thinking.
At its core, A3 is a vehicle for PDCA (Plan-Do-Check-Act). The left side of the A3 corresponds to Plan (understanding the problem, analyzing root causes, setting goals), and the right side corresponds to Do-Check-Act (countermeasures, implementation, verification, follow-up). The single-page format forces the author to separate signal from noise and present only what matters.
Origin — Not a Paper Format, But a Management System
The A3 as practiced today did not emerge from the shop floor. It was deliberately developed as a management development tool at Toyota headquarters in the late 1970s.
The Kan-Pro Program (1978)
In the late 1970s, Masao Nemoto — the influential executive who had led Toyota’s successful Deming Prize initiative in 1965 — observed that Toyota’s non-manufacturing managers were not developing the problem-solving and communication capabilities that had been instilled in production managers through TQC (Total Quality Control) practices. Rapid company growth meant younger managers were not receiving adequate mentoring.
In 1978, Nemoto formed a task force to create the Kanri Nouryoku Program (管理能力プログラム, “Management Capability Program”), known internally as Kan-Pro. Isao Yoshino was one of four staff members on this task force, working out of Toyota City.
Kan-Pro was a two-year program involving approximately 2,000 managers company-wide — both manufacturing and knowledge-work managers. It focused on four competencies:
- Planning and judging capability
- Broad knowledge and perspectives
- Leadership and kaizen capability
- Presentation and persuasion capability
The A3 format became the centerpiece of Kan-Pro. Managers presented their A3 documents twice yearly (in June and December) to senior officers, including Eiji Toyoda. The presentations emphasized factual identification of problems and encouraged transparency about mistakes — a sharp departure from the blame-focused cultures common in most organizations.
From Quality Circles to Management Process
The A3 did not appear from nowhere in 1978. Its roots were in the quality circle (QC circle) movement at Toyota, which used single-page reports to tell PDCA improvement stories. Toyota had won the Deming Prize in 1965 under Nemoto’s leadership, and the TQC discipline that earned the prize included concise, fact-based reporting.
What Kan-Pro did was elevate the A3 from a shop-floor quality tool to a company-wide management process. Mikio Sugiura, an architect in Toyota’s Corporate Planning Office, created a landmark A3 in 1980 reflecting on the Kan-Pro program itself. Sugiura and his team, including Yoshino, developed A3s that were “mainly fact-based or scientific” yet reflected what they called a “humanist” perspective — acknowledging personal viewpoints and biases rather than pretending to pure objectivity.
By the program’s conclusion, A3 thinking had become institutionalized at Toyota. It became the standard format for hoshin kanri (policy deployment) planning, for proposals, for problem-solving reports, and for status updates across the company.
John Shook and the Spread to the West
John Shook joined Toyota in Toyota City in late 1983 as one of the first Americans to work for the company in Japan. His first managers — Isao Yoshino and Ken Kunieda — coached him through the A3 process as part of his onboarding. At that time, every newly hired college graduate at Toyota began learning their job by being coached through A3.
Two key books brought A3 thinking to the English-speaking world, both published in 2008:
Art Smalley and Durward Sobek wrote Understanding A3 Thinking: A Critical Component of Toyota’s PDCA Management System (Productivity Press, now Taylor & Francis). Smalley drew on his direct experience working at Toyota in Japan. Sobek, a professor of mechanical and industrial engineering at Montana State University, had studied Toyota’s product development process for his PhD — spending time at Toyota Technical Center in Ann Arbor and interviewing engineers in Japan. Through that research, Sobek observed firsthand how A3s were used in technical and engineering environments and grasped their significance as a thinking discipline, not just a reporting format. The combination of Smalley’s insider production system knowledge and Sobek’s research perspective on how A3 functioned in product development produced a book that grounded A3 in Toyota’s broader PDCA management system.
John Shook wrote Managing to Learn: Using the A3 Management Process (Lean Enterprise Institute), structured as a dialogue between a manager and subordinate. Shook had joined Toyota in Toyota City in late 1983 as one of the first Americans to work for the company in Japan, where his managers — Isao Yoshino and Ken Kunieda — coached him through the A3 process. Managing to Learn focuses on how A3 develops the person writing it through the coaching relationship.
Together, these two books established A3 thinking in the English-speaking lean community — Smalley and Sobek providing the systematic PDCA framework and its application across production and engineering, Shook providing the coaching and dialogue dimension.
Types of A3
Toyota uses A3 for many purposes, not just problem solving. The format adapts to whatever situation requires structured thinking and communication. Some common examples:
Problem-Solving A3 — Perhaps the most widely known type. Follows the PDCA cycle: background, current condition, goal, root cause analysis, countermeasures, implementation plan, check/confirmation, follow-up. Used when a gap exists between a current condition and a target condition.
Proposal A3 — Used to propose a new initiative, investment, or change. The proposal A3 is how Toyota makes decisions — not through PowerPoint presentations or email chains, but through a document that forces the proposer to think through the full story.
Status Report A3 — Used to communicate progress on an ongoing initiative. Shows planned versus actual, what has been learned, and what adjustments are being made.
These are examples, not an exhaustive list. A3 can be used for hoshin planning, new product development, supplier negotiations, personnel development, process design, and virtually any situation where structured thinking and clear communication are needed. The format is flexible — what is constant is the PDCA logic underneath: understand the situation factually, reason from evidence, propose or report actions, and show how results will be verified.
How A3 Is Actually Used Inside Toyota
The Western consulting industry has turned A3 into a fill-in-the-blanks template exercise. Inside Toyota, it functions very differently.
A3 is a dialogue, not a document. The author writes a draft, discusses it with their manager or mentor, revises, discusses again, revises again. A typical A3 goes through many iterations before it is “final.” The document is the artifact of the thinking process — but the thinking process happens in the conversations around the document.
The manager coaches through questions, not answers. A Toyota manager reviewing an A3 does not say “here is what you should do.” They ask questions: “What did you actually observe?” “How do you know this is the root cause?” “What will you check to confirm your countermeasure worked?” The A3 process develops the subordinate’s capability to think clearly and solve problems independently. As the LEI axiom states: “The lean leader’s job is to develop people. If the worker hasn’t learned, the teacher hasn’t taught.”
Nemawashi happens through the A3. Before a proposal A3 is formally presented, the author shares it with affected parties, gathers feedback, and incorporates their concerns. By the time the A3 reaches a decision-maker, there should be no surprises — consensus has already been built through the circulation of the document. This is nemawashi (根回し, “going around the roots”) in practice.
The constraint of one page is real and intentional. Toyota could use larger paper or multiple pages. The single-page constraint forces the author to identify what truly matters and discard everything else. If you cannot fit your story on one page, you probably do not understand it well enough. Attachments with supporting data are acceptable, but the A3 itself must tell the complete story.
A3 is not reserved for big problems. Art Smalley has written about matching the formality of A3 to the difficulty of the problem: easy problems may be solved through direct observation and “5-Why” thinking without a formal report; medium and hard problems benefit from the structure and communication discipline of a written A3. The A3 is most valuable when a problem requires extended work, involves multiple people, or benefits from documented thinking that can be reviewed later.
The PDCA Connection
A3 is often described as “PDCA on a page,” and this is essentially correct — but with nuance.
The left side of an A3 corresponds to Plan: understanding the background, grasping the current condition, defining the problem, setting a target, and analyzing root causes. This is the hardest part. Most A3 failures happen here — superficial analysis, vague problem statements, goals that are really action items in disguise.
The right side corresponds to Do (countermeasures and implementation plan), Check (verification of results — before and after comparison), and Act (standardization of what worked, follow-up on what remains).
The key insight is that the Plan phase should take the majority of the effort. At Toyota, an A3 author is often sent back multiple times to deepen their understanding of the current condition and root causes before being allowed to propose countermeasures. Western practitioners tend to rush through the left side and jump to solutions — which is precisely what the A3 structure is designed to prevent.
Common Mistakes
Art Smalley has documented common A3 mistakes from his experience coaching practitioners:
The scope is too big. New A3 writers often take on problems that are too large for a single A3 cycle. The result is vague analysis and generic countermeasures. Start small, with a problem you can observe directly and solve within a reasonable timeframe.
The A3 is an answer in search of a problem. The author has already decided on the solution and reverse-engineers the A3 to justify it. This defeats the entire purpose — A3 is a thinking process, not a justification process.
No clear depiction of the process or situation. The current condition should be shown, not just described. Process maps, sketches, data charts, and photos communicate more effectively than paragraphs of text. Taiichi Ohno insisted on going to see the actual process; the A3 should reflect what was actually observed.
The entire document is in text. An effective A3 uses graphics, diagrams, and data visualizations — not walls of text. The visual format is essential to communication and comprehension.
No PDCA cycle. Some A3s list observations and recommendations without any structured analysis connecting causes to effects, or any plan to verify that countermeasures actually worked.
The analysis is superficial. A3 writers often stop at the first plausible cause rather than pursuing root causes. “The machine broke” is a symptom, not a root cause. Why did it break? Why was the failure not prevented? Why was the prevention not in the maintenance plan?
The goal statement is fuzzy or is an action item in disguise. “Implement a new scheduling system” is an action, not a goal. “Reduce changeover time from 45 minutes to 10 minutes by June 30” is a goal. The difference matters because a goal can be checked; an action cannot.
No clear assignments. Who will do what, by when? The 5W1H method (Who, What, When, Where, Why, How) should be applied to every countermeasure and follow-up item.
The check lacks before-and-after comparison. The whole point of Check in PDCA is to verify whether countermeasures produced the expected results. Without a clear before-and-after comparison using the same metrics, you cannot know whether the A3 achieved its purpose.
Worked Example
See A3 Report Example: Apollo 13 — an experiment in AI-assisted problem-solving report writing, using the Apollo 13 oxygen tank failure as a well-documented historical case study.