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
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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
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'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.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
LowLowLow
Timedifferent
15-45 min30-60 min45–75 min
Participantsdifferent
1-33-10Team members involved
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, RationaleEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
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