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 ARID (Active Reviews for Intermediate Designs) |  Operations 5 Whys |  Operations Causal Factor Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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 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 | Low | High | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 15-30 min | 2-6 h | 2-4 h |
Participantsdifferent | Designers, developers as users, and facilitation | 2-6 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Root cause notes, Countermeasures | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Root causeIncidentLeanProblem solving | CausalityIncidentRoot causeTimeline | Root causeSafetyIncident |