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 |  Systems Thinking Leverage Points |  Architecture Architecture Decision Record |  Product Strategy DIBB |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 60-120 min | Half day | 15-45 min | 1-2 h |
Participantsdifferent | 2-8 | 3-12 | 1-3 | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Leverage Map, Action Strategy | ADR File, Decision Log, Rationale | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingChangeStrategy | ArchitectureRationaleDocumentationGovernance | StrategyDecisionAssumptionsHypothesis |