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 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
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
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.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
LowLowLowLow
Timedifferent
45-90 min30-60 min30-60 min45–75 min
Participantsdifferent
3-123-123-10Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tags1 shared
AlignmentStakeholdersTeam
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods