View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Storytelling | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | When an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | 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. | 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 | Medium | High | Low |
Timedifferent | 45-120 min | Several meetings plus preparation and analysis; total effort depends on scope | 60–90 min |
Participantsdifferent | 1-6 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Narrative Outline, Key Message, Story Arc | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Stakeholder Map, Engagement Plan, Risk Notes |
Tags1 shared | CommunicationNarrativeStakeholdersFacilitation | ArchitectureQualityRiskTradeoffsStakeholders | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






