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 RetrospectiveArchitecture Decision RecordStrategy Execution LoopSprint Retrospective
| Criterion |  Agile Sailboat Retrospective |  Architecture Architecture Decision Record |  Business Strategy Strategy Execution Loop |  Agile Sprint 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. | 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. | 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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 45-90 min | 15-45 min | Initial 3-6 h, then monthly or quarterly reviews | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 4-12 | 1-3 | 5-12 | Scrum Team |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | ADR File, Decision Log, Rationale | Execution Loop, Review Cadence, Strategic Learning Log | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveTeamImprovement | ArchitectureRationaleDocumentationGovernance | ExecutionCadenceLearningGovernance | RetrospectiveImprovementLearning |