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

Criterion	Systems Thinking Polarity Mapping	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Evaporating Cloud	Systems Thinking Causal Loop Diagram
Purposedifferent	Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.	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.	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.
Complexitysame	Medium	Medium	Medium	Medium
Timedifferent	1-2 h	2–4 h review as a planning range; preparation and evaluation additional	60-120 min	1-3 h
Participantsdifferent	3-12	Designers, developers as users, and facilitation	2-8	2-8
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Polarity Map, Warning Signs, Balance Actions	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Causal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap	Systems thinkingTradeoffsLeadership	ArchitectureEngineeringFeedbackValidationTasks	Theory of ConstraintsAssumptionsSystems thinking	FeedbackSystems thinkingCausalityDynamics

Add more methods