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 Future Reality Tree |  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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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 | High | Low |
Timedifferent | 30-90 min | 2-4 h | 20-45 min |
Participantsdifferent | 3-12 | 3-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Lessons learned, Action items, Event summary |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | Theory of ConstraintsSystems thinkingChange | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
