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 Causal Factor Analysis |  Architecture Risk Storming |  Operations 5 Whys |
|---|---|---|---|---|
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 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 architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | 2–4 h review as a planning range; preparation and evaluation additional | 2-6 h | 60-90 min | 15-30 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-10 | 4-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Annotated Diagram, Prioritized Risk List, Action Backlog | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | CausalityIncidentRoot causeTimeline | RiskArchitectureWorkshopValidation | Root causeIncidentLeanProblem solving |