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 Kepner-Tregoe |  Decision Making Constraint Analysis |  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 a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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-8 h | 30-90 min | 15-30 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Problem Analysis, Decision Analysis, Risk Plan | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Problem solvingRoot causeDecisionOperations | ConstraintsDecisionPlanningOptions | Root causeIncidentLeanProblem solving |