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:Leverage Points ARID (Active Reviews for Intermediate Designs)Force Field Analysis Causal Loop Diagram

Criterion	Systems Thinking Leverage Points	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Force Field Analysis	Systems Thinking Causal Loop Diagram
Purposedifferent	Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.	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.	In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.	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.
Complexitydifferent	High	Medium	Low	Medium
Timedifferent	Half day	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	1-3 h
Participantsdifferent	3-12	Designers, developers as users, and facilitation	3-12	2-8
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Leverage Map, Action Strategy	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Force Field Map, Change Levers, Risk Notes	Causal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap	Systems thinkingChangeStrategy	ArchitectureEngineeringFeedbackValidationTasks	ChangeDecisionStrategy	FeedbackSystems thinkingCausalityDynamics

Add more methods