methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Starfish 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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
LowLowLowLow
Timedifferent
20-60 min10-20 min daily30-60 min45-90 min
Participantsdifferent
1-413-124-12
Formatdifferent
AsyncAsyncWorkshopWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathDaily Plan, Time Estimates, Review NotesStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
OperationsReliabilityDocumentation
PlanningTime managementProductivityOperations
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods