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)Evaporating CloudRoot Cause Tree Analysis5 Whys
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Systems Thinking Evaporating Cloud |  Operations Root Cause Tree 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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 | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 60-120 min | 1-3 h | 15-30 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Cause Tree, Evidence Notes, Countermeasures | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Theory of ConstraintsAssumptionsSystems thinking | Root causeTreeIncidentQuality | Root causeIncidentLeanProblem solving |