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 Stakeholder Mapping | ![]() Operations ALPEN Method |
|---|---|---|---|
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 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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. |
Complexitysame | Low | Low | Low |
Timedifferent | 20-60 min | 60–90 min | 10-20 min daily |
Participantsdifferent | 1-4 | 2-8 | 1 |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | Runbook, Checklist, Escalation Path | Stakeholder Map, Engagement Plan, Risk Notes | Daily Plan, Time Estimates, Review Notes |
Tagsno overlap | OperationsReliabilityDocumentation | StakeholdersAlignmentFacilitationChange | PlanningTime managementProductivityOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






