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 Salience ModelConsensus WorkshopStakeholder Mapping
| Criterion |  Architecture Architecture Decision Record |  Facilitation Stakeholder Salience Model |  Facilitation Consensus Workshop |  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. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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 h | 60–90 min |
Participantsdifferent | 1-3 | 3-6 | 5-30 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | Consensus Clusters, Theme Titles, Priority Areas | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | FacilitationConsensusWorkshopAlignment | StakeholdersAlignmentFacilitationChange |