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 Architecture Decision Record Causal Loop Diagram ARID (Active Reviews for Intermediate Designs)

Criterion	Systems Thinking Leverage Points	Architecture Architecture Decision Record	Systems Thinking Causal Loop Diagram	Architecture ARID (Active Reviews for Intermediate Designs)
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.	An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.	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.
Complexitydifferent	High	Low	Medium	Medium
Timedifferent	Half day	15-45 min	1-3 h	2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent	3-12	1-3	2-8	Designers, developers as users, and facilitation
Formatdifferent	Workshop	Async	Workshop	Workshop + async
Outputdifferent	Leverage Map, Action Strategy	ADR File, Decision Log, Rationale	Causal Loop Diagram, Feedback Notes, Leverage Points	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap	Systems thinkingChangeStrategy	ArchitectureRationaleDocumentationGovernance	FeedbackSystems thinkingCausalityDynamics	ArchitectureEngineeringFeedbackValidationTasks

Add more methods