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

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Evaporating Cloud	Operations A3 Problem Solving	Systems Thinking Causal Loop Diagram
Purposedifferent	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.	For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.	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	2–4 h review as a planning range; preparation and evaluation additional	60-120 min	45-90 min	1-3 h
Participantsdifferent	Designers, developers as users, and facilitation	2-8	2-5	2-8
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	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	A3 Report, Action Plan, Root Cause Analysis	Causal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	Theory of ConstraintsAssumptionsSystems thinking	LeanProblem solvingCoachingOperations	FeedbackSystems thinkingCausalityDynamics

Add more methods