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 MappingProblem Framing WorkshopStakeholder Salience Model
| Criterion |  Architecture Architecture Decision Record |  Facilitation Stakeholder Mapping |  Facilitation Problem Framing Workshop |  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. | 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 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 | 60-120 min | 60-90 min |
Participantsdifferent | 1-3 | 2-8 | 4-10 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Stakeholder Map, Engagement Plan, Risk Notes | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StakeholdersAlignmentFacilitationChange | FacilitationAlignmentDiscovery | StakeholdersFacilitationAlignmentGovernance |