View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy DIBB |  Agile Start Stop Continue |  Decision Making Force Field Analysis |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 h | 30-60 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-8 | 3-12 | 3-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | DIBB document, Belief list, Bet list, Learning report | Start Stop Continue Board, Improvement Actions | Force Field Map, Change Levers, Risk Notes | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | StrategyDecisionAssumptionsHypothesis | RetrospectiveImprovementTeamReflection | ChangeDecisionStrategy | RetrospectiveLearningReflectionTeam |