methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
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.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 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
LowLowMediumLow
Timedifferent
15-45 min45–75 min1-3 h30-60 min
Participantsdifferent
1-3Team members involved3-103-12
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, Rationale4Ls Board, Learning Themes, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RetrospectiveLearningReflectionTeam
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementTeamReflection
Add more methods