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 Future Reality Tree |  Delivery RAID Log |  Systems Thinking Evaporating Cloud |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 2-4 h | 30 min Setup, dann laufend | 60-120 min | 45-60 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 2-8 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | RAID Log, Status Report Source | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsSystems thinkingChange | RiskTrackingStakeholdersGovernance | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskExperimentsValidation |