View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Stakeholder Salience ModelArchitecture Decision RecordProblem Framing WorkshopStakeholder Mapping
| Criterion |  Facilitation Stakeholder Salience Model |  Architecture Architecture Decision Record |  Facilitation Problem Framing Workshop |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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 | Medium | Low | Low | Low |
Timedifferent | 60-90 min | 15-45 min | 60-120 min | 60–90 min |
Participantsdifferent | 3-6 | 1-3 | 4-10 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Salience Diagram, Strategy per Class | ADR File, Decision Log, Rationale | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | StakeholdersFacilitationAlignmentGovernance | ArchitectureRationaleDocumentationGovernance | FacilitationAlignmentDiscovery | StakeholdersAlignmentFacilitationChange |