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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.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 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'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.
Complexitydifferent
LowLowMediumLow
Timedifferent
45–75 min15-45 min1-3 h30-60 min
Participantsdifferent
Team members involved1-31-83-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision RationaleEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
RetrospectiveTeamReflection
Add more methods