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 SAAM (Software Architecture Analysis Method) |  Systems Thinking Evaporating Cloud |  Product Strategy DIBB |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 60-120 min | 1-2 h | 45-90 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | DIBB document, Belief list, Bet list, Learning report | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Theory of ConstraintsAssumptionsSystems thinking | StrategyDecisionAssumptionsHypothesis | ChangeDecisionStrategy |