Structured Problem Solving (A3)

← All maturity guides

SEF Reference Guide G05  |  Manufacturing OpEx Maturity Assessment

What it is

Structured problem solving is a disciplined, repeatable way to find the root cause of a problem and fix it so it stays fixed. The alternative is firefighting: treating the symptom, moving on, and meeting the same problem again next month.

SEF’s standard method is an A3 built on four phases: Measure the current state, Analyze to root cause, Improve and test, and Sustain and monitor. Root cause work uses 5 Whys for simple, single-chain problems and cause mapping when several causes combine.

The A3 itself comes from Toyota, where problem solving, proposals, and status reports were kept to one sheet of A3 paper (297 x 420 mm, close to the US 11 x 17 inch tabloid sheet). The one-page limit forces clear thinking, and the sheet becomes a coaching tool.

Why it matters

• Cost: problems solved once stop draining money through repeated scrap, rework, and expediting.
• Quality and delivery: root cause fixes remove the source of defects and delays instead of inspecting around them.
• Safety: the same method that fixes a scrap problem finds the real causes behind near misses.
• People and leadership time: a shared method gives operators, engineers, and managers one language for problems, and fewer recurring fires frees leaders to improve instead of react.

Key terms

Term	Meaning
Structured Problem Solving	A disciplined, repeatable method for solving problems at the root cause. Common forms include A3, 8D, DMAIC, and the four-step Measure, Analyze, Improve, Sustain approach.
Root Cause Analysis	Methods (5 Whys, cause mapping, fishbone, and others) used to find the underlying cause of a problem, so the fix prevents recurrence instead of treating the symptom.
A3	A one-page problem solving and planning format, named for the A3 paper size. It walks from background and current condition, through root cause, to countermeasures, a plan, and follow-up.
Cross-functional team	An improvement team with members from every function needed to find the root cause and implement a solution. Example: fixing invoice errors may need Finance, Sales, and IT.
5 Whys	Asking “why?” repeatedly, checking each answer against facts, until you reach a cause you can act on. Associated with Taiichi Ohno at Toyota.
Cause mapping	A visual root cause method: start with the impact on goals and work backward through cause-and-effect links, allowing several causes to combine (AND) at any step, with evidence attached to each cause.
Problem statement	A factual description of the gap: what, where, when, how much, compared with the standard or target. No causes or solutions.
Containment	A temporary action to protect the customer while the root cause is found (for example, 100% inspection or sorting stock).
Countermeasure	An action aimed at a verified root cause. Called a countermeasure, not a solution, because it is tested before it is trusted.
8D	Eight Disciplines. A team-based method for customer complaints and serious defects (see G21).
DMAIC	Define, Measure, Analyze, Improve, Control. The Six Sigma project method for complex, data-heavy problems.

How to do it

The SEF A3 in four phases

1. Measure the current state.
   • Write the background: why this problem matters, in one or two lines.
   • Go to the gemba, see the problem, and collect data: how often, how much, where, when.
   • Write the problem statement and a goal (from X to Y by date).
   • Contain it if the customer is at risk.
2. Analyze to root cause.
   • Break the problem down (by line, shift, product, defect type) and pick the biggest piece.
   • Use 5 Whys when the chain is simple. Check each answer at the gemba or in the data before asking the next why. Stop when you reach a cause you can control and whose removal would prevent recurrence.
   • Use a cause map when several causes combine. Start from the impact on goals (safety, customer, cost), ask why, and add causes to the right. Where two conditions were both needed, show them with AND. Mark each cause as confirmed by evidence or still to be checked.
   • Confirm the root cause: can you turn the problem on and off by changing it?
3. Improve and test.
   • List countermeasures against each confirmed root cause. Prefer ones that remove the cause or make the error impossible (see G08) over training and reminders.
   • Test on a small scale. Compare results with the baseline from phase 1.
   • Build an action plan: what, who, when, status.
4. Sustain and monitor.
   • Update the standard: SOP, job instruction, control plan, PM checklist (see G06).
   • Monitor the measure for long enough to prove the problem is gone (typically at least three months, or longer for rare events).
   • Share what you learned with other areas that could have the same problem (see G17).
   • Close the A3 with the sponsor and record the result.

Choosing A3, 8D, or DMAIC

Method	Best for	Typical length	Team
Quick fix (just do it)	Obvious cause, low risk, fix within a day	Hours	One or two people
A3 (SEF default)	Most internal problems: scrap, downtime, delays, safety near misses	2 to 8 weeks	Owner plus a small team
8D	Customer complaints and serious defects needing containment and a formal report	Containment within 24 hours (48 hours maximum); closure within 60 days (see G21)	Cross-functional team, formally named
DMAIC	Complex problems with many interacting variables, needing statistical analysis	3 to 6 months	Trained lead (for example, a Green Belt or Black Belt) and team

What makes a cross-functional team

• Every function that touches the cause or the fix is represented. If the fix needs IT, IT is on the team from the start.
• At least one person who does the work every day.
• Someone who owns the data.
• A named owner who drives the A3, and a sponsor who can remove roadblocks and provide resources.
• Small: three to seven people. Others join for specific steps.
• Use one when the cause or the fix crosses department lines, not for a problem one team can solve in a day.

What each maturity level looks like

OB-5 Structured Problem Solving

Level	Assessment wording	What it looks like on the floor	How to move up
1	Problems are handled reactively by firefighting.	The same problems return. Fixes are quick patches. Nobody writes anything down.	Pick one recurring problem and work it through a first A3 with a coach.
2	Problems are actively worked, but without a structured root cause method.	People try hard and hold meetings, but jump to solutions. Causes are opinions, not evidence.	Adopt one standard method (SEF A3) and train problem owners.
3	As Level 2, plus a structured root cause method (A3, 8D, DMAIC, or equivalent) is used.	A3s exist for significant problems, with problem statements, 5 Whys or cause maps, and action plans.	Build cross-functional teams for problems that cross department lines.
4	As Level 3, plus cross-functional teams are used where appropriate.	Teams include operators, engineering, quality, maintenance, and support functions as needed. Sponsors remove roadblocks.	Track time to close and recurrence. Verify results for three months before closing.
5	As Level 4, plus clear evidence that issues are resolved quickly and do not recur.	Closed A3s show results sustained over time. Repeat problems are rare and visible when they happen.	Share A3s across sites and use recurrence data to improve the method itself.

PE-3 Improvement Skills

Level	Assessment wording	What it looks like on the floor	How to move up
1	People are not trained in structured improvement skills.	Improvement is left to engineers or managers. No shared method.	Train a first group (team leaders, engineers) in the SEF A3 method.
2	Some people are trained in a structured improvement method (A3, 8D, DMAIC, or equivalent).	A few trained people run projects. Operators are asked for input occasionally.	Train operators in the basics (problem statement, 5 Whys, testing) and put them on every project.
3	As Level 2, plus the people who do the work are trained and are always involved in improvement.	Operators sit on A3 teams, collect data, and suggest countermeasures.	Post improvement projects on the area information boards (see G03).
4	As Level 3, plus improvement projects are tracked on information boards (VMS).	Boards show each project, owner, phase, and next step. Projects are reviewed in the daily meeting.	Measure project results and publish completed A3s with verified savings or gains.
5	As Level 4, plus clear evidence of successful improvement projects.	Completed A3s show measured before and after results. Many were led by front-line staff.	Develop internal coaches and link results to recognition (see G17).

Evidence to look for

Document

• Completed and in-progress A3s (or 8D and DMAIC reports), with problem statements, root cause analysis, and results.
• Training records showing who is trained in the method, by role.
• A problem-solving standard stating when to use A3, 8D, or DMAIC.

Observation

• Are A3s posted in the area or on the information board?
• Do root cause sections show evidence (data, photos, measurements), or only opinions?
• Are operators’ names on A3 teams?

Statement

(questions to ask and who to ask)

• Operator: “Have you been part of a problem-solving team? What was the root cause, and how did you prove it?”
• Engineer or team leader: “Show me your last A3. How do you know the problem has not come back?”
• Plant manager: “Which problems recurred this year? How do you decide which method to use?”

Management report

• Number of A3s opened and closed, and average time to close.
• Recurrence rate: closed problems that returned within 12 months (the same window G21 uses for repeat complaints).
• Percent of staff trained, by role.
• Results from closed projects (scrap, downtime, cost, safety).

Common pitfalls

• Jumping to solutions. The team skips Measure and Analyze and goes straight to “we need a new machine.” Hold the line on evidence.
• Stopping at “operator error.” Human error is a starting point. Ask why the process allowed it, and do not accept “retrain the operator” as the only countermeasure.
• 5 Whys without checking. Each answer must be verified at the gemba or in the data, or the chain drifts into guesses.
• Closing too early. An A3 is not done until the result holds and the standard is updated.
• Paperwork over thinking. A beautiful template filled in after the fact teaches nothing. Use the A3 as a coaching conversation.

Template

SEF A3 Outline

(one page, left side then right side)

Left side	Right side
Title: Problem name	3. IMPROVE: Countermeasures: Each countermeasure linked to a confirmed root cause
Owner / Sponsor / Team / Date	Test results: Small-scale trial, before and after data
Background: Why this matters (safety, customer, cost)	Action plan: What / Who / When / Status
1. MEASURE: Current condition: Data, chart, gemba observations	4. SUSTAIN: Results: Measure versus goal over time (chart)
Problem statement: What, where, when, how much, versus standard	Standards updated: SOP, job instruction, control plan, checklist
Goal: From X to Y by date	Monitoring: Measure, owner, frequency, for how long
Containment: If the customer is at risk	Shared with: Other areas or sites
2. ANALYZE: Root cause: 5 Whys or cause map, with evidence noted	Sign-off: Owner and sponsor, date closed

First 30 days

• Week 1: Pick one recurring problem with a clear measure. Name an owner, a sponsor, and a small team. Go to the gemba and collect data.
• Week 2: Write the problem statement and goal. Contain if needed. Run 5 Whys or build a cause map, verifying each cause.
• Week 3: Choose countermeasures and test them on a small scale. Post the A3 on the area board.
• Week 4: Implement, update the standard, and set up monitoring. Review the A3 with the sponsor. Pick the next problem and the next people to train.

Further reading

• John Shook, Managing to Learn: Using the A3 Management Process to Solve Problems, Gain Agreement, Mentor, and Lead, Lean Enterprise Institute, 2008.
• Durward K. Sobek II and Art Smalley, Understanding A3 Thinking: A Critical Component of Toyota’s PDCA Management System, Productivity Press, 2008.
• Taiichi Ohno, Toyota Production System: Beyond Large-Scale Production, Productivity Press, 1988.
• Lean Enterprise Institute, Lean Lexicon entries “A3 Report” and “5 Whys”: https://www.lean.org/lexicon-terms/a3-report/ and https://www.lean.org/lexicon-terms/5-whys/
• ThinkReliability, “Cause Mapping Method”: https://thinkreliability.com/cause-mapping/cause-mapping-method-explained/
• ASQ, “What is DMAIC?” and “What is 8D?”: https://asq.org/quality-resources/dmaic and https://asq.org/quality-resources/eight-disciplines-8d