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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
45-90 min1-3 h30-60 min45–75 min
Participantsdifferent
3-123-103-10Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsProcess Map, Handoff List, Improvement BacklogEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
AlignmentStakeholdersTeam
ProcessOperationsImprovement
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods