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 A3 Problem Solving |  Domain Modeling EventStorming |  Operations Fishbone Diagram |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 45-90 min | 2-8 h | 30-60 min | 2-6 h |
Participantsdifferent | 2-5 | 5-12 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Fishbone Diagram, Cause Categories, Investigation Backlog | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | LeanProblem solvingCoachingOperations | Domain-Driven DesignEventsDiscoveryWorkshop | Root causeQualityOperations | RiskQualityOperationsRoot cause |