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 A/B Testing Wardley Mapping ARID (Active Reviews for Intermediate Designs)

Criterion	Systems Thinking Causal Loop Diagram	Growth A/B Testing	Systems Thinking Wardley Mapping	Architecture ARID (Active Reviews for Intermediate Designs)
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.	When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.	Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions.	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.
Complexitydifferent	Medium	High	Medium	Medium
Timedifferent	1-3 h	1-4 Wochen	1-3 h	2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent	2-8	1-6	2-10	Designers, developers as users, and facilitation
Formatdifferent	Workshop	Async	Workshop + async	Workshop + async
Outputdifferent	Causal Loop Diagram, Feedback Notes, Leverage Points	Experiment results, Decision log, Learning summary	Wardley Map, Strategic Options, Evolution Notes	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap	FeedbackSystems thinkingCausalityDynamics	ExperimentsGrowthAnalyticsValidation	StrategySystems thinkingDynamics	ArchitectureEngineeringFeedbackValidationTasks

Add more methods