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 | ![]() Operations Learning Review | ![]() 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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 | Medium | Low | Low |
Timedifferent | 2-8 h | 1-3 h | 30-60 min | 15-30 min |
Participantsdifferent | 2-8 | 3-10 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Problem Analysis, Decision Analysis, Risk Plan | Learning Review Notes, System Factors, Improvement Actions | Start Stop Continue Board, Improvement Actions | Root cause notes, Countermeasures |
Tagsno overlap | Problem solvingRoot causeDecisionOperations | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementTeamReflection | Root causeIncidentLeanProblem solving |



