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) |  Product Strategy GIST Planning |  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. | GIST Planning helps clarify target groups, value, goals, and priorities. It links customer value, product logic, and decision priorities, and captures the result as goals, an idea bank, and a step-project list. | 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 | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Wochen bis Monate je Goal | 60–90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-10 | 2-8 |
Formatsame | Workshop + async | Workshop + async | 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 | Goals, Idea bank, Step-project list, Tasks, Learning reports | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RoadmapOutcomesPlanningExperiments | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
