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 Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck 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.
Complexitysame
LowLowLow
Timedifferent
45–75 min20-45 min45-90 min
Participantsdifferent
Team members involved1-83-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsOwnership Reflection, Action Commitment, Coaching NotesExpectation Map, Alignment Notes, Agreements
Tags1 shared
RetrospectiveLearningReflectionTeam
ResponsibilityLeadershipTeam
AlignmentStakeholdersTeam
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 Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping