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 Decision Tree |  Agile Acceptance Criteria Workshop |  Decision Making Pre-Mortem |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-90 min | 20-40 min pro Story | 20–45 min | 30-60 min |
Participantsdifferent | 1-6 | 3-6 | Small cross-functional group | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Decision Tree, Option Map, Assumption List | Acceptance Criteria, Story Update | Risk list, Mitigation plan, Assumption log | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | DecisionTreeOptions | AgileRequirementsRefinementBehavior-Driven Development | RiskDecisionFailurePlanning | Behavior-Driven DevelopmentRequirementsExamplesRefinement |