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 Software Architecture Canvas |  Operations Barrier Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. | 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 | High | Low | Medium | Low |
Timedifferent | Mehrere Tage bis Wochen | 1-2 h | 2-4 h | 15-30 min |
Participantsdifferent | 2-6 | 3-10 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Architecture Canvas, Goals, Constraints, Quality Attributes | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Root cause notes, Countermeasures |
Tagsno overlap | Root causeSafetySystemicIncident | CanvasArchitectureAlignmentWorkshop | Root causeSafetyIncident | Root causeIncidentLeanProblem solving |