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:Constraint Analysis ARID (Active Reviews for Intermediate Designs)Root Cause Tree Analysis Decision Tree

Criterion	Decision Making Constraint Analysis	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Root Cause Tree Analysis	Decision Making Decision Tree
Purposedifferent	When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.	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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.	For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.
Complexitydifferent	Low	Medium	Medium	Medium
Timedifferent	30-90 min	2–4 h review as a planning range; preparation and evaluation additional	1-3 h	30-90 min
Participantsdifferent	2-8	Designers, developers as users, and facilitation	2-8	1-6
Formatdifferent	Workshop + async	Workshop + async	Workshop	Workshop + async
Outputdifferent	Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Cause Tree, Evidence Notes, Countermeasures	Decision Tree, Option Map, Assumption List
Tagsno overlap	ConstraintsDecisionPlanningOptions	ArchitectureEngineeringFeedbackValidationTasks	Root causeTreeIncidentQuality	DecisionTreeOptions

Add more methods