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 ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Force Field Analysis |  Business Strategy McKinsey 7S |
|---|---|---|---|
Purposedifferent | 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. | 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. | McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min | 2-4 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Force Field Map, Change Levers, Risk Notes | 7S Assessment, Alignment Gaps, Change Actions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ChangeDecisionStrategy | OrganizationStrategyAlignmentChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
