View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Facilitation Stakeholder Mapping |  Product Strategy KPI Tree |  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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | 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 | Medium | Medium |
Timedifferent | 15-45 min | 60–90 min | 90-180 min initial, dann laufend | 60-90 min |
Participantsdifferent | 1-3 | 2-8 | 3-8 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Stakeholder Map, Engagement Plan, Risk Notes | KPI Tree, Owner List | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | StakeholdersAlignmentFacilitationChange | MetricsStrategyAlignmentMeasurement | StakeholdersFacilitationAlignmentGovernance |