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 A3 Problem Solving |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1 h bis mehrere Wochen | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 1-8 | 4-12 | 2-5 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Starfish Board, Practice Changes, Experiments | A3 Report, Action Plan, Root Cause Analysis | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Continuous improvementLeanExperiments | RetrospectiveImprovementExperimentsTeam | LeanProblem solvingCoachingOperations | RetrospectiveLearningReflectionTeam |