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) |  Systems Thinking Evaporating Cloud |  Operations 5 Whys |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 60-120 min | 15-30 min | 45-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 2-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
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 | Root cause notes, Countermeasures | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Theory of ConstraintsAssumptionsSystems thinking | Root causeIncidentLeanProblem solving | AssumptionsRiskExperimentsValidation |