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 ARID (Active Reviews for Intermediate Designs)Intervention Mapping Causal Loop Diagram

Criterion	Systems Thinking Evaporating Cloud	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Intervention Mapping	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.	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.	Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.	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	Medium	High	Medium
Timedifferent	60-120 min	2–4 h review as a planning range; preparation and evaluation additional	1-5 Tage	1-3 h
Participantsdifferent	2-8	Designers, developers as users, and facilitation	4-12	2-8
Formatdifferent	Workshop	Workshop + async	Workshop + async	Workshop
Outputdifferent	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Logic Model, Change Objectives, Intervention Components, Evaluation Plan	Causal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap	Theory of ConstraintsAssumptionsSystems thinking	ArchitectureEngineeringFeedbackValidationTasks	ChangeSystems thinkingCapability	FeedbackSystems thinkingCausalityDynamics

Add more methods