View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Systems Thinking Evaporating Cloud |  Decision Making Force Field Analysis |  Product Strategy DIBB |
|---|---|---|---|---|
Purposedifferent | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 60-120 min | 45-90 min | 1-2 h |
Participantsdifferent | 1-3 | 2-8 | 3-12 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Theory of ConstraintsAssumptionsSystems thinking | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis |