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 4Ls Retrospective |  Decision Making Force Field Analysis |
|---|---|---|---|
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 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 45-90 min | 45–75 min | 45-90 min |
Participantsdifferent | 2-5 | Team members involved | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | 4Ls Board, Learning Themes, Improvement Actions | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | LeanProblem solvingCoachingOperations | RetrospectiveLearningReflectionTeam | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
