View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Sailboat RetrospectiveStrategy Execution LoopArchitecture Decision RecordStarfish Retrospective
| Criterion |  Agile Sailboat Retrospective |  Business Strategy Strategy Execution Loop |  Architecture Architecture Decision Record |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Low | High | Low | Low |
Timedifferent | 45-90 min | Initial 3-6 h, then monthly or quarterly reviews | 15-45 min | 45-90 min |
Participantsdifferent | 4-12 | 5-12 | 1-3 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Execution Loop, Review Cadence, Strategic Learning Log | ADR File, Decision Log, Rationale | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveTeamImprovement | ExecutionCadenceLearningGovernance | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementExperimentsTeam |