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 A3 Problem Solving | ![]() Agile Start Stop Continue | ![]() Operations Kepner-Tregoe | ![]() Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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 | Medium | Low | High | Low |
Timedifferent | 45-90 min | 30-60 min | 2-8 h | 45–75 min |
Participantsdifferent | 2-5 | 3-12 | 2-8 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Start Stop Continue Board, Improvement Actions | Problem Analysis, Decision Analysis, Risk Plan | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LeanProblem solvingCoachingOperations | RetrospectiveImprovementTeamReflection | Problem solvingRoot causeDecisionOperations | RetrospectiveLearningReflectionTeam |



