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 |  Delivery RAID Log |  Product Discovery Assumption Mapping |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Medium | Low | Medium | Low |
Timedifferent | 60-120 min | 30 min Setup, dann laufend | 45-60 min | 45-90 min |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 2-8 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | RAID Log, Status Report Source | Assumption map, Test backlog, Risk ranking | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | RiskTrackingStakeholdersGovernance | AssumptionsRiskExperimentsValidation | AssumptionsRiskDecisionDiscovery |