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 Causal Loop Diagram ARID (Active Reviews for Intermediate Designs)Stock and Flow Diagram

Criterion	Systems Thinking Evaporating Cloud	Systems Thinking Causal Loop Diagram	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Stock and Flow Diagram
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.	A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics.
Complexitydifferent	Medium	Medium	Medium	High
Timedifferent	60-120 min	1-3 h	2–4 h review as a planning range; preparation and evaluation additional	2-6 h
Participantsdifferent	2-8	2-8	Designers, developers as users, and facilitation	1-6
Formatdifferent	Workshop	Workshop	Workshop + async	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	Stock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap	Theory of ConstraintsAssumptionsSystems thinking	FeedbackSystems thinkingCausalityDynamics	ArchitectureEngineeringFeedbackValidationTasks	DynamicsSimulationFeedbackSystems thinking

Add more methods