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 Kepner-Tregoe |  Agile Starfish Retrospective |  Agile Start Stop Continue |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 2-8 h | 45-90 min | 30-60 min | 15-30 min |
Participantsdifferent | 2-8 | 4-12 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Problem Analysis, Decision Analysis, Risk Plan | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Root cause notes, Countermeasures |
Tagsno overlap | Problem solvingRoot causeDecisionOperations | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | Root causeIncidentLeanProblem solving |