View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Root Cause Tree AnalysisScatter Diagram5 Whys
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Root Cause Tree Analysis |  Operations Scatter Diagram |  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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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 | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 30-90 min | 15-30 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 1-4 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Cause Tree, Evidence Notes, Countermeasures | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Root causeTreeIncidentQuality | Root causeQualityVisualization | Root causeIncidentLeanProblem solving |