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 Barrier Analysis |  Architecture Request for Comments |  Operations MORT Analysis |
|---|---|---|---|
Purposedifferent | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 2-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | Mehrere Tage bis Wochen |
Participantsdifferent | 2-6 | 3-20 Reviewer | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Root causeSafetyIncident | ArchitectureDecisionAsyncGovernance | Root causeSafetySystemicIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
