View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Evaporating Cloud | ![]() Decision Making Pre-Mortem | ![]() Systems Thinking Current Reality Tree | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 60-120 min | 20–45 min | 2-6 h | 45-60 min |
Participantsdifferent | 2-8 | Small cross-functional group | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Risk list, Mitigation plan, Assumption log | Current Reality Tree, Core Problems, Intervention Ideas | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | RiskDecisionFailurePlanning | Systems thinkingRoot causeConstraintsCausality | AssumptionsRiskExperimentsValidation |



