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 Stakeholder Salience Model |  Architecture Views and Beyond |  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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Medium | Low |
Timedifferent | 15-45 min | 60-90 min | 1-3 Tage | 60–90 min |
Participantsdifferent | 1-3 | 3-6 | 1-4 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | Architecture Views, Cross-view Notes, Rationale | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | DocumentationStakeholdersArchitecture | StakeholdersAlignmentFacilitationChange |