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 MORT Analysis |  Architecture arc42 |  Operations 5 Whys |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Mehrere Tage bis Wochen | 1-2 Tage | 15-30 min | 2-4 h |
Participantsdifferent | 2-6 | 1-4 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Root causeSafetySystemicIncident | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving | Root causeSafetyIncident |