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 Sailboat Retrospective
Agile
Sailboat Retrospective
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
Purposedifferent
When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
45-90 min1-3 h30-60 min45-90 min
Participantsdifferent
4-123-103-104-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Sailboat Board, Risks, Improvement ActionsProcess Map, Handoff List, Improvement BacklogEmotion Board, Themes, Action ItemsStarfish Board, Practice Changes, Experiments
Tagsno overlap
RetrospectiveTeamImprovement
ProcessOperationsImprovement
RetrospectiveTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods