View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Domain StorytellingATAM (Architecture Tradeoff Analysis Method)Alignment MappingStakeholder Mapping
| Criterion |  Knowledge Modeling Domain Storytelling |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Alignment Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 | Low | High | Medium | Low |
Timedifferent | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h | 60–90 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange |