View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Double Diamond |  DevOps Blameless Postmortem |  Operations MORT Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | 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 | Wochen bis Monate | 30-90 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 3-12 | 3-12 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Postmortem Doc, Action Items, Timeline | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ProcessDivergenceInnovation | Site Reliability EngineeringIncidentLearningReliability | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |