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 Family Tree Analysis |  Architecture arc42 |  Operations MORT Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 2-4 h | 1-2 Tage | Mehrere Tage bis Wochen | 15-30 min |
Participantsdifferent | 2-6 | 1-4 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Architecture Document, Context View, Runtime View, Deployment View | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Root cause notes, Countermeasures |
Tagsno overlap | Root causePatternsIncidentSystemic | ArchitectureDocumentationCommunication | Root causeSafetySystemicIncident | Root causeIncidentLeanProblem solving |