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 |  Systems Thinking Evaporating Cloud |  Operations After-Action Review |
|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Medium | Medium | Low |
Timedifferent | 30-90 min | 60-120 min | 20-45 min |
Participantsdifferent | 3-12 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Lessons learned, Action items, Event summary |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | Theory of ConstraintsAssumptionsSystems thinking | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
