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 Start Stop Continue |  Operations After-Action Review |  Agile 4Ls 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 30-60 min | 20-45 min | 45–75 min |
Participantsdifferent | 1-3 | 3-12 | 3-12 | Team members involved |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Start Stop Continue Board, Improvement Actions | Lessons learned, Action items, Event summary | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementTeamReflection | LearningOperationsImprovement | RetrospectiveLearningReflectionTeam |