View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Facilitation Alignment Mapping |  Architecture Architecture Decision Record |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-60 min | 1-2 h | 15-45 min | 60–90 min |
Participantsdifferent | 1-4 | 4-12 | 1-3 | 2-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Alignment Map, Open Issues, Decision Questions | ADR File, Decision Log, Rationale | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | OperationsReliabilityDocumentation | AlignmentStakeholdersStrategyFacilitation | ArchitectureRationaleDocumentationGovernance | StakeholdersAlignmentFacilitationChange |