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

Criterion	Systems Thinking Causal Loop Diagram	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Getting Things Done	Systems Thinking Stock and Flow Diagram
Purposedifferent	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.	With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.	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	1-3 h	2–4 h review as a planning range; preparation and evaluation additional	1-2 h Setup, laufend	2-6 h
Participantsdifferent	2-8	Designers, developers as users, and facilitation	1	1-6
Formatdifferent	Workshop	Workshop + async	Async	Workshop + async
Outputdifferent	Causal Loop Diagram, Feedback Notes, Leverage Points	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Action Lists, Project List, Review Routine	Stock and Flow Model, Dynamics Notes, Simulation Hypotheses
Tagsno overlap	FeedbackSystems thinkingCausalityDynamics	ArchitectureEngineeringFeedbackValidationTasks	ProductivityPlanningTasksExecution	DynamicsSimulationFeedbackSystems thinking

Add more methods