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)Change Analysis Evaporating Cloud Causal Loop Diagram

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Change Analysis	Systems Thinking Evaporating Cloud	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.	For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.	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	2–4 h review as a planning range; preparation and evaluation additional	45-120 min	60-120 min	1-3 h
Participantsdifferent	Designers, developers as users, and facilitation	2-6	2-8	2-8
Formatdifferent	Workshop + async	Workshop + async	Workshop	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Change Matrix, Cause Hypotheses, Validation Questions, Action List	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Causal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ChangeRoot causeTroubleshootingComparison	Theory of ConstraintsAssumptionsSystems thinking	FeedbackSystems thinkingCausalityDynamics

Add more methods