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 |  Operations ALPEN Method |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
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. | 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-60 min | 10-20 min daily | 45-90 min | 45-90 min |
Participantsdifferent | 1-4 | 1 | 4-12 | 4-12 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | Runbook, Checklist, Escalation Path | Daily Plan, Time Estimates, Review Notes | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | OperationsReliabilityDocumentation | PlanningTime managementProductivityOperations | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |