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 |  Architecture Risk Storming |  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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | Low | Medium |
Timedifferent | 60-120 min | 60-90 min | 1-3 h |
Participantsdifferent | 2-8 | 4-12 | 2-8 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Annotated Diagram, Prioritized Risk List, Action Backlog | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | RiskArchitectureWorkshopValidation | FeedbackSystems thinkingCausalityDynamics |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
