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 Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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 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 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.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 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
LowLowMediumLow
Timedifferent
45-90 min30-60 min1-3 h45–75 min
Participantsdifferent
4-123-103-10Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Starfish Board, Practice Changes, ExperimentsEmotion Board, Themes, Action ItemsProcess Map, Handoff List, Improvement Backlog4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RetrospectiveImprovementExperimentsTeam
RetrospectiveTeamReflection
ProcessOperationsImprovement
RetrospectiveLearningReflectionTeam
Add more methods