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 ALPEN Method | ![]() Agile Start Stop Continue | ![]() Operations Process Mapping | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 10-20 min daily | 30-60 min | 1-3 h | 45-90 min |
Participantsdifferent | 1 | 3-12 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | Daily Plan, Time Estimates, Review Notes | Start Stop Continue Board, Improvement Actions | Process Map, Handoff List, Improvement Backlog | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | PlanningTime managementProductivityOperations | RetrospectiveImprovementTeamReflection | ProcessOperationsImprovement | RetrospectiveImprovementExperimentsTeam |



