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) |  Systems Thinking Soft Systems Methodology |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | High | High | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 0.5-3 Tage | 60–90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 5-15 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Soft systemsComplexitySensemakingSystems thinking | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
