View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations 5 Whys |  Domain Modeling Domain Context Map |  Operations A3 Problem Solving |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-30 min | 1-3 h | 45-90 min | 2-4 h |
Participantsdifferent | 2-6 | 3-10 | 2-5 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Domain Context Map, Boundary Notes, Ownership Map | A3 Report, Action Plan, Root Cause Analysis | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Root causeIncidentLeanProblem solving | Domain-Driven DesignContextBoundaries | LeanProblem solvingCoachingOperations | Root causeSafetyIncident |