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)Assumption Mapping Pre-Mortem

Criterion	Decision Making Constraint Analysis	Architecture ARID (Active Reviews for Intermediate Designs)	Product Discovery Assumption Mapping	Decision Making Pre-Mortem
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.	When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.	In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.
Complexitydifferent	Low	Medium	Medium	Low
Timedifferent	30-90 min	2–4 h review as a planning range; preparation and evaluation additional	45-60 min	20–45 min
Participantsdifferent	2-8	Designers, developers as users, and facilitation	2-8	Small cross-functional group
Formatdifferent	Workshop + async	Workshop + async	Workshop + async	Workshop
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	Assumption map, Test backlog, Risk ranking	Risk list, Mitigation plan, Assumption log
Tagsno overlap	ConstraintsDecisionPlanningOptions	ArchitectureEngineeringFeedbackValidationTasks	AssumptionsRiskExperimentsValidation	RiskDecisionFailurePlanning

Add more methods