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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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
With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.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 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
Ongoing45-90 min1-3 h45–75 min
Participantsdifferent
1-204-123-10Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Visual Board, Status Indicators, Exception CuesSailboat Board, Risks, Improvement ActionsProcess Map, Handoff List, Improvement Backlog4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
SignalsOperationsVisual management
RetrospectiveTeamImprovement
ProcessOperationsImprovement
RetrospectiveLearningReflectionTeam
Add more methods