View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordStakeholder MappingSoftware Architecture CanvasStakeholder Salience Model
| Criterion |  Architecture Architecture Decision Record |  Facilitation Stakeholder Mapping |  Architecture Software Architecture Canvas |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 60–90 min | 1-2 h | 60-90 min |
Participantsdifferent | 1-3 | 2-8 | 3-10 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop | StakeholdersFacilitationAlignmentGovernance |