A3 problem solving
Concept
A structured problem-solving method from lean that records background, current state, root cause, countermeasures and follow-up on a single sheet of paper, traditionally A3 size, to guide discussion and learning.
Opis
A3 problem solving is a structured way to work on a problem and to share the thinking behind it. The name refers to the paper size, A3, on which the whole story is kept on one sheet. The author describes the background, the current state, the goal, the analysis of root causes, the countermeasures, a plan and the follow-up.
The sheet is a discussion tool rather than a report. It is reviewed with a coach or manager, who asks questions and helps the author to think, and it is updated as results come in. Because the format forces short, clear statements, it is also a way to teach problem solving. A3 thinking follows the plan, do, check, act cycle and is a common part of lean management.
| Typ | Concept |
|---|---|
| Znane także jako | A3 report, A3 thinking |
Articles about A3 problem solving (2)
- Root Cause Analysis in Production: 5 Whys and Fishbone in Practice
· Mirko Peters
Root cause analysis in production, step by step: when to use the 5 whys or a fishbone diagram, how to verify a cause and a worked downtime example with numbers. - A3 Problem Solving: How to Write an A3 Report Step by Step
· Mirko Peters
A3 problem solving on one page: how to write an A3 report step by step, a template layout, a worked example with numbers and how to coach others to use it well.
Related to
- iFAKT GmbH · Organization
- Continuous improvement · Concept
- Lean management · Concept
- Kaizen · Concept
- Continuous improvement manager · Zawód / rola
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Eksperci i firmy w tym temacie
- Mirko Peters · Microsoft MVP
Sources
- Feed for this topic (RSS): entity/a3-problem-solving/feed.xml
- Articles on this topic: 2
Maintained by Mirko Peters (Microsoft MVP) · Last updated: