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 PDCA Cycle | ![]() Agile Starfish Retrospective | ![]() Operations Process Mapping | ![]() Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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. | 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1 h bis mehrere Wochen | 45-90 min | 1-3 h | 30-60 min |
Participantsdifferent | 1-8 | 4-12 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Starfish Board, Practice Changes, Experiments | Process Map, Handoff List, Improvement Backlog | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | Continuous improvementLeanExperiments | RetrospectiveImprovementExperimentsTeam | ProcessOperationsImprovement | RetrospectiveImprovementTeamReflection |



