View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Start Stop Continue |  Product Strategy DIBB |  Decision Making Force Field Analysis |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 1-2 h | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 2-8 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | DIBB document, Belief list, Bet list, Learning report | Force Field Map, Change Levers, Risk Notes | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | StrategyDecisionAssumptionsHypothesis | ChangeDecisionStrategy | RetrospectiveTeamImprovement |