Skip to content
LeanSuite - Lean Manufacturing Software

Book summary · Kaizen and problem solving · Intermediate

Understanding A3 Thinking: summary and review

A Critical Component of Toyota's PDCA Management System

By Durward K. Sobek II and Art Smalley. First published 2008.

The short answer

Sobek and Smalley treat the A3 as the visible part of something larger: PDCA used as the way Toyota managers think. The book covers the three A3 types (problem solving, proposal, status), seven elements of A3 thinking, formatting rules and the support the sheet needs, with example reports in the appendices. It is more systematic and less story-driven than Managing to Learn, and suits engineers, improvement leads and consultants who write and review A3s.

Read it if

  • You write or review A3s and want criteria for what a good one contains.
  • You use one A3 type for everything and need to tell the three apart.
  • You want the PDCA logic behind the layout before teaching it.

Skip it if

  • You want to hear how a mentor talks to an author. Managing to Learn does that.
  • You want proof that A3 improves results. Evidence in this area is case-level.
  • You hope to adopt A3 for every problem. Smalley has said that is a mistake.

When it pays off: Read it when a handful of A3s are in circulation and you want better ones, or before designing a review routine.

The core ideas, in plain language

  1. 1

    A3 is PDCA on paper

    The authors argue PDCA, not the form, is the heart of how Toyota manages. Sobek's earlier paper maps it: current condition and root cause are background research, target and plan are the experiment design, the follow-up prediction is the hypothesis, and results test it.

  2. 2

    Three A3 types, three jobs

    A problem-solving A3 closes a gap, a proposal A3 asks approval for a change, and a status A3 reports on a project. Using one when you need another muddles both.

  3. 3

    Seven elements as review questions

    The book names seven elements: logical thinking, objectivity, balance of results and process, synthesis and visualization, alignment, coherence and consistency, and a systems viewpoint. Use them as questions for a draft, such as whether any claim rests on opinion.

  4. 4

    Current condition is where it is won

    Sobek and Jimmerson's hospital paper calls the current condition the most important section, built from direct observation, and says efforts usually fail because the current state was not understood.

  5. 5

    Brevity forces thinking

    One sheet with pictures and counted numbers makes the author distil the problem. The same paper says diagrams also shift discussion from people to the system.

  6. 6

    Context matters as much as the form

    The book gives a chapter to supporting structures around the sheet. Sobek says he first saw A3 used pervasively while studying Toyota's product development.

How to use it on Monday morning

  1. 1

    Review one existing A3

    Take a recent A3 and mark each claim as observed or asserted. Put the seven elements on a card and ask which are missing. Give the author questions, not a verdict.

  2. 2

    Pick the type first

    Decide whether you need to fix a gap, win approval or report status, and ask whether the problem needs an A3 at all.

  3. 3

    Build the current condition on site

    Observe the process directly, draw it, and count where it goes wrong. In Sobek's hospital example, one day's check found 7 of 17 charts flagged as waiting for transcriptions already had them.

  4. 4

    Dig past the second why

    Sobek's paper says stopping at two or three whys usually means the inquiry is too shallow. Test whether the cause lies in how work is specified, how people connect or the path work takes.

  5. 5

    Write the prediction and close the loop

    State what you expect as a number and a date, then record the result on the same sheet. In that example, 98% of 371 charts arrived complete and billing took 6.6 days, against a prediction of 100% and 7.

What to be careful about

  • Not every problem is an A3

    Art Smalley has argued that treating everything as an A3 is a mistake. Readers who skip the question of whether a problem needs an A3 will misuse the book.

  • A reference book, not a coaching book

    It describes the report and its parts more than it shows a mentor talking to an author, where Managing to Learn is stronger. That is a judgement about emphasis.

  • Case-level evidence

    Support for A3 is practitioner experience and cases. Sobek and Jimmerson's hospital paper reports dozens of problems at one hospital and one worked example, not a comparison against other methods. It says finding time is the common obstacle.

Understanding A3 Thinking compared with Managing to Learn

Pick Understanding A3 Thinking if you write or review A3s and need standards for a good one. Pick Managing to Learn if your problem is mentoring: how to ask and gain agreement. For a program, read both.

Read the summary of Managing to Learn.

Tools and templates on LeanSuite that go with it

Book details

Bibliographic details of Understanding A3 Thinking
TitleUnderstanding A3 Thinking: A Critical Component of Toyota's PDCA Management System
AuthorDurward K. Sobek II and Art Smalley
First published2008
Edition shownHardcover, first edition, Productivity Press, 2008
ISBN-13978-1563273605

Details checked against public records on 7 October 2026. Other editions have other ISBNs. We carry no affiliate links.

Key terms

Lean glossary

FAQ

Questions about Understanding A3 Thinking

More lean books

Back to the lean books hub for reading paths and filters.

Rather see it on your own problem?

Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

Schedule Demo

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.