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 4Ls Retrospective |  Decision Making Argument Mapping |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 45–75 min | 1-3 h | 30-60 min |
Participantsdifferent | 1-3 | Team members involved | 1-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | 4Ls Board, Learning Themes, Improvement Actions | Argument Map, Evidence Gaps, Decision Rationale | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RetrospectiveLearningReflectionTeam | SensemakingDecisionRationale | RetrospectiveImprovementTeamReflection |