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 Learning Review.
Operations
Learning Review
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Purposedifferent
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.For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.
Complexitydifferent
MediumHighMedium
Timedifferent
1-3 h2-4 h Analyse, laufend30-90 min
Participantsdifferent
3-103-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Learning Review Notes, System Factors, Improvement ActionsConstraint Map, Improvement Plan, Flow MetricsPostmortem Doc, Action Items, Timeline
Tagsno overlap
LearningRetrospectiveIncidentOperations
OperationsConstraintsFlowImprovement
Site Reliability EngineeringIncidentLearningReliability
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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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