View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Operations Bottleneck Analysis |  Operations Learning Review |  Operations Theory of Constraints |
|---|---|---|---|---|
Purposedifferent | 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. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 30-90 min | 1-3 h | 1-3 h | 2-4 h Analyse, laufend |
Participantsdifferent | 3-12 | 3-8 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Learning Review Notes, System Factors, Improvement Actions | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | FlowMeasurementConstraints | LearningRetrospectiveIncidentOperations | OperationsConstraintsFlowImprovement |