View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Pre-Mortem |  Domain Modeling EventStorming |  Decision Making Decision Tree |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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 decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20–45 min | 2-8 h | 30-90 min | 45-90 min |
Participantsdifferent | Small cross-functional group | 5-12 | 1-6 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Decision Tree, Option Map, Assumption List | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskDecisionFailurePlanning | Domain-Driven DesignEventsDiscoveryWorkshop | DecisionTreeOptions | AssumptionsRiskDecisionDiscovery |