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 |  Operations Runbook |  Facilitation Consensus 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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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 | 20-60 min | 1-3 h | 60-90 min |
Participantsdifferent | 1-3 | 1-4 | 5-30 | 3-6 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path | Consensus Clusters, Theme Titles, Priority Areas | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation | FacilitationConsensusWorkshopAlignment | StakeholdersFacilitationAlignmentGovernance |