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 Affinity Estimation.
Agile
Affinity Estimation
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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Purposedifferent
When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
MediumMediumLowLow
Timedifferent
30-90 min1-3 h45–75 min20-45 min
Participantsdifferent
3-123-10Team members involved3-12
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsProcess Map, Handoff List, Improvement Backlog4Ls Board, Learning Themes, Improvement ActionsLessons learned, Action items, Event summary
Tagsno overlap
EstimationBacklogRelative sizing
ProcessOperationsImprovement
RetrospectiveLearningReflectionTeam
LearningOperationsImprovement
Add more methods