View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Delphi Method |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations 5 Whys |  Operations Kepner-Tregoe |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | 1-4 Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 15-30 min | 2-8 h |
Participantsdifferent | 6-30 Experten | Designers, developers as users, and facilitation | 2-6 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Expert Forecast, Consensus Range, Assumption Notes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | ForecastingExpertsDecisionStrategy | ArchitectureEngineeringFeedbackValidationTasks | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations |