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 |  Agile Example Mapping |  Decision Making Decision Tree |  Agile Specification by Example |
|---|---|---|---|---|
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 story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 20–45 min | 30-60 min | 30-90 min | 60-90 min pro Feature |
Participantsdifferent | Small cross-functional group | 3-7 | 1-6 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Example Map, Acceptance Criteria, Open Questions | Decision Tree, Option Map, Assumption List | Example Table, Acceptance Tests |
Tagsno overlap | RiskDecisionFailurePlanning | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DecisionTreeOptions | AgileRequirementsExamplesBehavior-Driven Development |