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
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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
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.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–75 min1-3 h
Participantsdifferent
Team members involved3-10
Formatsame
WorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
RetrospectiveLearningReflectionTeam
ProcessOperationsImprovement
Add more methods

Often compared together

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

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Learning Review.
Operations
Learning Review