View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Systems Thinking Causal Loop Diagram |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 60-120 min | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 2-8 | 2-8 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Causal Loop Diagram, Feedback Notes, Leverage Points | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | FeedbackSystems thinkingCausalityDynamics | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
