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 Alignment Mapping |  Architecture arc42 |  Facilitation Stakeholder 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 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. | 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 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 | Medium | Low | Low |
Timedifferent | 15-45 min | 1-2 h | 1-2 Tage | 60–90 min |
Participantsdifferent | 1-3 | 4-12 | 1-4 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Alignment Map, Open Issues, Decision Questions | Architecture Document, Context View, Runtime View, Deployment View | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AlignmentStakeholdersStrategyFacilitation | ArchitectureDocumentationCommunication | StakeholdersAlignmentFacilitationChange |