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 ATAM (Architecture Tradeoff Analysis Method) | ![]() Delivery RAID Log |
|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | High | High | Low |
Timedifferent | Halber Tag bis mehrere Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend |
Participantsdifferent | 4-12 | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Balanced Scorecard, Strategic Measures, Initiative Map | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source |
Tagsno overlap | StrategyMetricsExecution | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






