View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy VMGS | ![]() Architecture Architecture Decision Record | ![]() Facilitation Stakeholder Salience Model | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | VMGS arranges vision, mission, goals, and strategies into a clear guiding logic. Direction, purpose, and priorities are connected so teams can decide more coherently. | 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 | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 15-45 min | 60-90 min | 60–90 min |
Participantsdifferent | 3-12 | 1-3 | 3-6 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Vision Statement, Mission Statement, Goals, Strategies | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | VisionGoalsStrategy | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange |



