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 |  Delivery RAID Log |  Operations 5 Whys |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Medium | High | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-6 h | 30 min Setup, dann laufend | 15-30 min |
Participantsdifferent | 3-20 Reviewer | 3-10 | 1-3 maintaining, briefing for everyone | 2-6 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | RAID Log, Status Report Source | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CausalityIncidentRoot causeTimeline | RiskTrackingStakeholdersGovernance | Root causeIncidentLeanProblem solving |