View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopStarfish RetrospectiveArchitecture Decision RecordSailboat Retrospective
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Starfish Retrospective |  Architecture Architecture Decision Record |  Agile Sailboat 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 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. | 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 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min | 15-45 min | 45-90 min |
Participantsdifferent | 5-12 | 4-12 | 1-3 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Starfish Board, Practice Changes, Experiments | ADR File, Decision Log, Rationale | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ExecutionCadenceLearningGovernance | RetrospectiveImprovementExperimentsTeam | ArchitectureRationaleDocumentationGovernance | RetrospectiveTeamImprovement |