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
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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.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.
Complexitysame
LowLowLow
Timedifferent
45–75 min30-60 min15-45 min
Participantsdifferent
Team members involved3-101-3
Formatdifferent
WorkshopWorkshopAsync
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action ItemsADR File, Decision Log, Rationale
Tagsno overlap
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
ArchitectureRationaleDocumentationGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments