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 Causal Factor Analysis |  Operations Change Analysis |  Operations Barrier 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 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 | Medium | High | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-6 h | 45-120 min | 2-4 h |
Participantsdifferent | 3-20 Reviewer | 3-10 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CausalityIncidentRoot causeTimeline | ChangeRoot causeTroubleshootingComparison | Root causeSafetyIncident |