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)Scatter Diagram5 WhysRoot Cause Tree Analysis
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Scatter Diagram |  Operations 5 Whys |  Operations Root Cause Tree 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 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-90 min | 15-30 min | 1-3 h |
Participantsdifferent | Designers, developers as users, and facilitation | 1-4 | 2-6 | 2-8 |
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 | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Root cause notes, Countermeasures | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Root causeQualityVisualization | Root causeIncidentLeanProblem solving | Root causeTreeIncidentQuality |