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 Family Tree 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 a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h | 2-4 h |
Participantsdifferent | 3-20 Reviewer | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Family Tree Diagram, Pattern Notes, Systemic Measures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Root causePatternsIncidentSystemic | Root causeSafetyIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
