View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Evaporating CloudA/B TestingARID (Active Reviews for Intermediate Designs)Causal Loop Diagram
| Criterion |  Systems Thinking Evaporating Cloud |  Growth A/B Testing |  Architecture ARID (Active Reviews for Intermediate Designs) |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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. | A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 60-120 min | 1-4 Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h |
Participantsdifferent | 2-8 | 1-6 | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Experiment results, Decision log, Learning summary | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ExperimentsGrowthAnalyticsValidation | ArchitectureEngineeringFeedbackValidationTasks | FeedbackSystems thinkingCausalityDynamics |