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 Kepner-Tregoe |  Facilitation Decision Jam |
|---|---|---|---|---|
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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 45-90 min | 2-8 h | 2-8 h | 60-90 min |
Participantsdifferent | 2-5 | 5-12 | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Analysis, Decision Analysis, Risk Plan | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | LeanProblem solvingCoachingOperations | Domain-Driven DesignEventsDiscoveryWorkshop | Problem solvingRoot causeDecisionOperations | FacilitationDecisionProblem solvingWorkshop |