View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordSailboat RetrospectiveAfter-Action ReviewStarfish Retrospective
| Criterion |  Architecture Architecture Decision Record |  Agile Sailboat Retrospective |  Operations After-Action 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 missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 45-90 min | 20-45 min | 45-90 min |
Participantsdifferent | 1-3 | 4-12 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Sailboat Board, Risks, Improvement Actions | Lessons learned, Action items, Event summary | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveTeamImprovement | LearningOperationsImprovement | RetrospectiveImprovementExperimentsTeam |