View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Sailboat Retrospective |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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. | 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min | 30-60 min | 45-90 min |
Participantsdifferent | 5-12 | 4-12 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ExecutionCadenceLearningGovernance | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |