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 ABC Analysis
Operations
ABC Analysis
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
LowMediumMedium
Timedifferent
30-60 min1-3 h1-3 h
Participantsdifferent
1-53-103-10
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
ABC Classification, Focus Rules, Control ListProcess Map, Handoff List, Improvement BacklogLearning Review Notes, System Factors, Improvement Actions
Tags1 shared
PrioritizationOperationsPortfolio
ProcessOperationsImprovement
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

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

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem