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 Force Field Analysis Constraint Analysis

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Product Strategy Impact Mapping	Decision Making Force Field Analysis	Decision Making Constraint 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.	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.	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.
Complexitydifferent	Medium	Medium	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	45-90 min	45-90 min	30-90 min
Participantsdifferent	Designers, developers as users, and facilitation	3-8	3-12	2-8
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Impact Map, Outcome Hypotheses, Delivery Options	Force Field Map, Change Levers, Risk Notes	Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	OutcomesStrategyBehaviorPlanning	ChangeDecisionStrategy	ConstraintsDecisionPlanningOptions

Add more methods