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 Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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
LowMediumLowLow
Timedifferent
45–75 min1-3 h45-90 min30-60 min
Participantsdifferent
Team members involved1-83-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsArgument Map, Evidence Gaps, Decision RationaleExpectation Map, Alignment Notes, AgreementsStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
SensemakingDecisionRationale
AlignmentStakeholdersTeam
RetrospectiveImprovementTeamReflection
Add more methods