Compare

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 Cloud Risk Storming ARID (Active Reviews for Intermediate Designs)Causal Loop Diagram

Criterion	Systems Thinking Evaporating Cloud	Architecture Risk Storming	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.	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.	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	Low	Medium	Medium
Timedifferent	60-120 min	60-90 min	2–4 h review as a planning range; preparation and evaluation additional	1-3 h
Participantsdifferent	2-8	4-12	Designers, developers as users, and facilitation	2-8
Formatdifferent	Workshop	Workshop	Workshop + async	Workshop
Outputdifferent	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Annotated Diagram, Prioritized Risk List, Action Backlog	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	RiskArchitectureWorkshopValidation	ArchitectureEngineeringFeedbackValidationTasks	FeedbackSystems thinkingCausalityDynamics

Add more methods