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:ARID (Active Reviews for Intermediate Designs)Impact Mapping Decision Tree Force Field Analysis

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Product Strategy Impact Mapping	Decision Making Decision Tree	Decision Making Force Field Analysis
Purposedifferent	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.	When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.	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.	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.
Complexitydifferent	Medium	Medium	Medium	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	30-90 min	45-90 min
Participantsdifferent	Designers, developers as users, and facilitation	3-8	1-6	3-12
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Impact Map, Outcome Hypotheses, Delivery Options	Decision Tree, Option Map, Assumption List	Force Field Map, Change Levers, Risk Notes
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	OutcomesStrategyBehaviorPlanning	DecisionTreeOptions	ChangeDecisionStrategy

Add more methods