View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Scenario Planning |  Architecture SAAM (Software Architecture Analysis Method) |  Product Strategy Impact Mapping |
|---|---|---|---|
Purposedifferent | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. | 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. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. |
Complexitydifferent | High | High | Medium |
Timedifferent | 0.5-2 Tage | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min |
Participantsdifferent | 4-12 | Architecture experts and stakeholders for scenarios and weighting | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Scenario Set, Strategic Implications, Robust Options | 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 | Impact Map, Outcome Hypotheses, Delivery Options |
Tagsno overlap | StrategyUncertaintyPlanning | ArchitectureChangeAnalysisComparisonQuality | OutcomesStrategyBehaviorPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
