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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
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
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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.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
MediumLowLowLow
Timedifferent
1-3 h30-60 min45-90 min45–75 min
Participantsdifferent
3-103-104-12Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogEmotion Board, Themes, Action ItemsStarfish Board, Practice Changes, Experiments4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ProcessOperationsImprovement
RetrospectiveTeamReflection
RetrospectiveImprovementExperimentsTeam
RetrospectiveLearningReflectionTeam
Add more methods