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 of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for ABC Analysis
Operations
ABC Analysis
Purposedifferent
When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.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.
Complexitydifferent
LowMediumLow
Timedifferent
30-60 min1-3 h30-60 min
Participantsdifferent
3-103-101-5
Formatdifferent
Workshop + asyncWorkshopAsync
Outputdifferent
Risk Matrix, Top Risk ListLearning Review Notes, System Factors, Improvement ActionsABC Classification, Focus Rules, Control List
Tagsno overlap
RiskDecisionPrioritizationAssessment
LearningRetrospectiveIncidentOperations
PrioritizationOperationsPortfolio
Add more methods

Often compared together

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

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
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem