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 ModelProblem Framing WorkshopAlignment Mapping
| Criterion |  Architecture Architecture Decision Record |  Facilitation Stakeholder Salience Model |  Facilitation Problem Framing Workshop |  Facilitation Alignment 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 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 60-90 min | 60-120 min | 1-2 h |
Participantsdifferent | 1-3 | 3-6 | 4-10 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | FacilitationAlignmentDiscovery | AlignmentStakeholdersStrategyFacilitation |