View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  DevOps Blameless Postmortem |  Operations MORT Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | 30-90 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 3-10 | 3-12 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Postmortem Doc, Action Items, Timeline | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ProcessOperationsImprovement | Site Reliability EngineeringIncidentLearningReliability | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |