Skip to content
Discovery WaypointDecision-ready discovery
Start WorkspaceSign in
Start Workspace
Sign in
Toyota

Toyota A3 / Lean A3

Borrow the artifact · Primary + examples

Toyota A3 Problem Solving

Use the A3 as a thinking discipline and coaching artifact, not as a tidy one-page form that pretends the team has already understood the problem.

Best opened when

Problems that need one visible reasoning chain before the room jumps to solutions.

What to steal first

The one-page reasoning chain and the coaching-style review that tests the logic.

What not to copy

It is not just a status update template.

Closest move

Current vs Future State Mapping

Core artefact

Artifact anatomy

The Toyota A3 is a one-page artifact that forces a complete problem-solving argument onto a single sheet: current condition, analysis of causes, target condition, proposed countermeasures, and follow-up. At Toyota, the discipline was not the page — it was the coaching conversation that the page made possible. A visible reasoning chain that a senior engineer could challenge, improve, and push back on in one standing review.

What transfers is the commitment to a single coherent argument. If you cannot explain the move from observation to root cause to countermeasure without a gap, the A3 is revealing a thinking weakness rather than hiding it. That is the point. The artifact is not a presentation; it is a working document that should get better through challenge.

What does not transfer cleanly: the A3 discipline depends on someone in the organization having the coaching skill and authority to challenge the reasoning. A strong A3 reviewer is not someone who approves well-formatted documents — they are someone who can ask 'how do you know that?' and refuse to accept the first answer. Without that role, the artifact becomes a compliance template.

Use it in a session

A clean first pass you can run

Participants
Problem owner plus 2–3 people with direct knowledge of the problem context. One facilitator if the problem owner and the room need to be separated. 3–5 people total.
Timing
90–120 minutes for the initial A3 draft. A separate 60-minute review session at least 24 hours later, when the problem owner has had time to test the current condition claims.
Prep
Before the session, the problem owner writes a two-sentence problem statement: what is happening and why it matters. If they cannot write it, that becomes the first 20 minutes of the session.
  1. 1Background: Why does this problem matter? State the business or operational context in two to three sentences. Not the solution — the stakes.
  2. 2Current condition: What is actually happening now? Use data and direct observation, not interpretation. If the current condition is based on assumption rather than evidence, say so.
  3. 3Target condition: What should be happening? Be specific enough that two people can independently judge whether it has been achieved. 'Reduce defects from 12% to 4% by end of Q3' is a target condition. 'Improve quality' is not.
  4. 4Root cause analysis: What is actually causing the gap between current and target? Go deeper than the obvious first answer. Use five-whys or fishbone to surface the cause behind the symptom.
  5. 5Countermeasures: What specific actions address the root cause? Each countermeasure needs an owner and a date. If a countermeasure does not have both, it is a suggestion, not a commitment.
  6. 6Review plan: When will the team check whether countermeasures changed the target condition? A review plan that is never scheduled is a countermeasure list with no accountability.

You leave with

A single-page A3 with a grounded current condition, a specific target condition, a root cause that is supported by evidence, and countermeasures with owners and dates.

First failure point: The team jumps to countermeasures before the current condition is grounded in direct observation rather than interpretation. A3s built on assumed current conditions produce countermeasures for the wrong problem.

What good looks like

If this is working, these are the signals you should be able to point to

  • The A3 fits on one page and someone who did not write it can explain the problem and countermeasure from the page alone.
  • The root cause section contains causes the team did not already know before starting.
  • The countermeasure was chosen from more than one option and the choice is visible on the page.
  • There is a follow-up plan with a specific confirmation date, not just an expected outcome.

How it worked there

The conditions that made it hold

Toyota used A3 thinking as a management development tool inside a manufacturing culture where making the reasoning visible was part of how problems got solved and how engineers learned. The format served two purposes simultaneously: it improved the specific problem being solved, and it built the solver's analytical discipline.

The coaching relationship was the load-bearing mechanism. A3s traveled up and down the organization not as reports but as objects for discussion. A manager who received an A3 was expected to engage with the reasoning, not sign it off. That culture — where vague problem framing was unacceptable and where analysis was supposed to reveal rather than defend — is the condition the artifact was designed for. Most adopting organizations have the template without the coaching culture, and the A3 behaves accordingly.

What not to copy · Failure modes

What goes wrong when this is copied

The A3 is filled after the decision is already made. The most common failure is using the artifact to document a conclusion that has already been reached — reverse-engineering the reasoning chain from a known answer. The result looks like rigorous analysis but the current condition is framed to support the solution, the root cause analysis stops at the level the team was already comfortable with, and the countermeasures are the ones the team had already decided to implement. A post-rationalized A3 is a reporting document, not a thinking tool.

The sheet is treated as the method rather than the artifact. Teams import the A3 template and use it as a structured report format. The method is not the template. The method is the coaching discipline — the back-and-forth challenge of 'why is the problem framed this way,' 'how do we know that is the root cause,' and 'what assumption is being smuggled through as a conclusion.' Without that challenge, a well-formatted A3 can have razor-thin reasoning.

Polished presentation substitutes for strong argument. A visually clean A3 with neat boxes and clear handwriting looks like strong thinking. A messy A3 with crossed-out sections and margin notes that evolved through challenge might be much stronger. The quality signal is the evidence chain — whether causes actually follow from observations, whether countermeasures follow from causes — not whether the artifact looks finished.

Weak signals to watch for

  • It is not just a status update template.
  • It is not a shortcut around clarifying the problem and evidence first.
  • Do not treat the sheet as the method.
  • Do not fill the page with post-rationalized certainty after the real analysis already stopped.

Closest Waypoint move

What to open next

Primary route

Current vs Future State Mapping

Use this when the room needs a sharper picture of the current condition before compressing the work into an A3.

Use this when you need a single-page problem-solving narrative and can accept that building the A3 well takes longer than most teams initially expect.

Sources and confidence

Primary + examples

Reviewed by Discovery Waypoint Editorial Team · 2026-04-04