View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Agile Sailboat Retrospective |  Operations Learning Review |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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 | Low | Medium | Low |
Timedifferent | 15-45 min | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 1-3 | 4-12 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementExperimentsTeam |