🧩 A3 Problem Solving – Sustainably Solving Complex Problems
A3 problem solving is a structured, step-by-step method for sustainably resolving complex problems within teams. This article explains when it makes sense to use an A3 report, how it differs from the PDCA approach (Immediate Countermeasure), and how to apply the method consistently in 7 steps – from problem description to standardization.
The focus is on proven analysis methods such as Ishikawa (fishbone) and the 5 Whys, as well as actively involving the team. In addition, you’ll find practical screenshots from the ValueStreamer system to guide you.
🔍 Content- When to use A3 – and when PDCA is enough
- The 7 steps of A3 problem solving
- Tips & Best Practices
- FAQ
📌 When to use A3 – and when PDCA is enough
A3 problem solving:
-
For complex problems where the causes are still unclear.
-
When aiming for a sustainable, long-term solution.
PDCA measure:
-
When the cause and solution are already known and it’s about implementation only.
📌 The 7 steps of A3 problem solving
Step 1 – Title & Background Description
-
Start an A3 report via “+ Action” within a deviation.
-
The deviation title is automatically carried over.
-
Define the responsible team, initiator, and participants.
-
Goal: Create curiosity and show relevance.
📸 Screenshot: Title field & background description
Step 2 – Problem Description & Immediate Countermeasures
-
Fill in all required problem fields.
-
If possible: Create immediate countermeasures as tasks directly.
-
Note: Immediate countermeasures are for direct action and do not replace the A3 analysis.
📸 Screenshot: Problem description with tasks section
Step 3 – Target State
-
Define a concrete, measurable goal that represents significant improvement over the current state.
-
Avoid premature solutions – focus on the desired end state.
📸 Screenshot: Target state input screen
Step 4 – Cause-Effect Analysis
-
Analyze causes systematically using the Ishikawa method (e.g., 6M fishbone diagram).
-
Use the pencil icon in the system to document effects and influencing factors.
-
Goal: Identify real root causes, not just treat symptoms.
📸 Screenshot: Ishikawa diagram view
Step 5 – Root Cause Investigation (5 Whys)
-
Create tasks for potential causes.
-
Challenge findings with the 5 Whys method to identify core causes.
-
In the system, clearly mark causes (“Direct Cause” / “Not Relevant”).
📸 Screenshot: 5 Whys analysis with core cause marking
Step 6 – Implementation Plan
-
Define tasks to resolve the root causes.
-
Tasks automatically appear in the team’s task board.
-
After completing actions: Check if the problem has been solved.
-
If not solved: Return to Step 4 or 5.
📸 Screenshot: Task overview with “Problem solved?” selection
Step 7 – Standardization & Closure
-
Document final remarks.
-
Standardize successful actions and share them with other teams.
-
After completion, the A3 report is stored in the global archive.
📸 Screenshot: Standardization step with final task
ℹ️ Info
-
Archived A3 reports are visible across the entire organization.
-
Steps must be completed in the given sequence.
-
Mandatory fields ensure structured and complete documentation.
✨ Tips & Best Practices
-
👥 Always conduct A3 problem solving as a team, not alone.
-
📚 Use visual aids such as diagrams and sketches for clarity.
-
📝 Regularly document progress in the description field, e.g., with timestamps and comments.
-
🔁 Be open to creative solutions – even beyond standardized methods.
❓ FAQ
When should I use PDCA instead of A3?
→ Use PDCA when the cause and solution are already known.
→ Use A3 when the causes are unclear and a sustainable solution is required.
Who can see an A3 report?
→ All teams within the organization; completed A3 reports are visible in the global archive.
Can I skip steps?
→ ❌ No, the steps must be completed in the prescribed sequence.
Can a completed A3 report be edited later?
→ No, completed A3 reports are read-only. Changes require creating a new report.