A3 Problem Solving | SymplProcess

1 Page

Forces Clarity

Sections

PDCA

Built-In Structure

Story

Tells Itself

What Is A3 Thinking?

A3 is a structured problem-solving and communication method from Toyota that fits the entire problem, analysis, solution, and follow-up plan on a single A3-size sheet of paper (11″ × 17″). The constraint of one page is the point — it forces you to think clearly, separate signal from noise, and communicate concisely.

A3 is not just a template. It is a way of thinking that follows the PDCA cycle: the left side of the page is Plan (understand the problem), and the right side is Do-Check-Act (implement and verify).

The Real Power of A3

The A3 is not the paper — it is the thinking process behind it. The act of filling out each section forces you to slow down, gather facts, analyze causes, and propose countermeasures based on evidence rather than gut feel. A good A3 takes 2-4 hours of thinking to produce, not 20 minutes of typing.

The 7 Sections

1. Background / ContextWhy does this problem matter? What is the business context? Connect the problem to a KPI, customer impact, or strategic objective. Two to three sentences. If you cannot explain why it matters, pick a different problem.

2. Current ConditionWhat is happening now? Use data, not opinions. Charts, Pareto analysis, process maps. Go to the gemba and observe. This section should make the gap between actual and expected performance undeniable.

3. Goal / TargetWhat specific, measurable outcome are you aiming for? "Reduce Line 2 changeover time from 45 minutes to 15 minutes by March 30." Not "improve changeover" — that is not a target.

4. Root Cause AnalysisWhy does the gap exist? Use 5 Whys, fishbone diagrams, or data analysis. This is the most important section — if the root cause is wrong, the countermeasure will not work. Test your root cause: does it explain all instances of the problem?

5. CountermeasuresWhat specific actions will address the root cause? Each countermeasure should directly connect to a root cause. Include who, what, and when. Prefer error-proofing and process changes over training and reminders.

6. Confirmation / CheckHow will you verify the countermeasures worked? What data will you track? What does success look like? Set a check date. If results are not achieved, the A3 cycles back to root cause analysis.

7. Follow-Up ActionsWhat remains to be done? Standardize successful countermeasures into standard work. Share learnings with other areas (yokoten). Update training materials. Close the A3 when results are sustained.

Left Side (PLAN)

1. Background
2. Current Condition
3. Goal / Target
4. Root Cause Analysis

Right Side (DO-CHECK-ACT)

5. Countermeasures
6. Confirmation
7. Follow-Up

The A3 layout mirrors PDCA: left side = Plan (understand), right side = Do-Check-Act (solve and verify)

Types of A3s

Type	Purpose	When to Use
Problem-Solving A3	Investigate and fix a specific problem	Recurring quality issue, missed targets, equipment failures
Proposal A3	Propose a change or investment	New equipment request, process redesign, staffing change
Status A3	Report progress on a project or initiative	Monthly update on a transformation initiative

A3 Coaching

In Toyota culture, a mentor does not fill out the A3 for the learner. They coach through questions:

Section	Coaching Questions
Background	"Why should the organization care about this?" "What is the business impact?"
Current Condition	"Have you been to the gemba?" "What does the data show?" "How do you know this is true?"
Goal	"Is this measurable?" "Is the timeline realistic?" "How will you know you succeeded?"
Root Cause	"Did you verify this at the gemba?" "Does this explain all instances?" "What if there is a deeper cause?"
Countermeasures	"Does each countermeasure connect to a root cause?" "What could go wrong?" "Who is the owner?"
Confirmation	"How will you measure the result?" "When will you check?" "What is your plan if it does not work?"

✅ Good A3 Practice

Problem verified at the gemba before writing
Current condition based on data, not assumptions
Root cause tested and verified
Countermeasures directly address root causes
Confirmation plan with specific check dates
A3 is a living document, not filed and forgotten

❌ A3 Anti-Patterns

Jump to countermeasures before understanding the problem
Current condition based on conference room opinions
Root cause = "operator error" (go deeper)
No check step — assume the fix worked
A3 completed in 20 minutes as a checkbox exercise
Beautiful formatting, shallow thinking

🎯 Key Takeaway

A3 thinking is not about the paper — it is about the discipline of understanding before solving. The one-page constraint forces you to find the signal in the noise. Master this method and you will solve problems faster, communicate more clearly, and build problem-solving capability in everyone you coach. Start with one A3 on your team's biggest recurring problem this week.

Interactive Demo

Walk through an A3 report section by section. See how each piece builds on the last to tell a complete problem-solving story on one page.

⚡

Try It Yourself

A3 Problem-Solving Walkthrough

▼

Step through each section of Toyota's A3 report. The left side defines the problem; the right side solves it. Follow the running example to see how each section builds on the last.

Progress0/8 sections

Problem Side (Left)

Solution Side (Right)