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 Views and Beyond |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Tage | 60-90 min | 60–90 min | 15-45 min |
Participantsdifferent | 1-4 | 3-6 | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | DocumentationStakeholdersArchitecture | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange | ArchitectureRationaleDocumentationGovernance |