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 Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Learning Review.
Operations
Learning Review
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 a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
15-45 min45–75 min30-60 min1-3 h
Participantsdifferent
1-3Team members involved3-103-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, Rationale4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action ItemsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
LearningRetrospectiveIncidentOperations
Add more methods