View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Operations Barrier Analysis |  Operations Causal Factor Analysis |
|---|---|---|---|
Purposedifferent | 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 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 an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h | 2-6 h |
Participantsdifferent | 3-20 Reviewer | 2-6 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Root causeSafetyIncident | CausalityIncidentRoot causeTimeline |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
