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) |  Decision Making Delphi Method |  Operations 5 Whys |  Operations Root Cause 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. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 Wochen | 15-30 min | 1-4 h |
Participantsdifferent | Designers, developers as users, and facilitation | 6-30 Experten | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Expert Forecast, Consensus Range, Assumption Notes | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ForecastingExpertsDecisionStrategy | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |