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 Architecture Decision Record |  Facilitation Storytelling |  Architecture arc42 |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 45-120 min | 1-2 Tage | 1-2 h |
Participantsdifferent | 1-3 | 1-6 | 1-4 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Narrative Outline, Key Message, Story Arc | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | CommunicationNarrativeStakeholdersFacilitation | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation |