View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Problem Framing WorkshopArchitecture Decision RecordStakeholder Salience ModelStakeholder Mapping
| Criterion |  Facilitation Problem Framing Workshop |  Architecture Architecture Decision Record |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 | Low | Medium | Low |
Timedifferent | 60-120 min | 15-45 min | 60-90 min | 60–90 min |
Participantsdifferent | 4-10 | 1-3 | 3-6 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | FacilitationAlignmentDiscovery | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange |