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
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.
Complexitydifferent
LowMedium
Timedifferent
45-90 min1-3 h
Participantsdifferent
4-123-10
Formatsame
WorkshopWorkshop
Outputdifferent
Sailboat Board, Risks, Improvement ActionsProcess Map, Handoff List, Improvement Backlog
Tags1 shared
RetrospectiveTeamImprovement
ProcessOperationsImprovement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review