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 Balanced Scorecard |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | 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. | 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 | High | Low |
Timedifferent | Halber Tag bis mehrere Wochen | 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-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Balanced Scorecard, Strategic Measures, Initiative Map | 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 | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | StrategyMetricsExecution | ArchitectureChangeAnalysisComparisonQuality | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
