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 StorytellingStorytellingATAM (Architecture Tradeoff Analysis Method)Architecture Communication Canvas
| Criterion |  Knowledge Modeling Domain Storytelling |  Facilitation Storytelling |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 1-2 h | 45-120 min | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min |
Participantsdifferent | 2-8 | 1-6 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | 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 | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | CommunicationNarrativeStakeholdersFacilitation | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureCommunicationStakeholdersCanvas |