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:Pre-Mortem ARID (Active Reviews for Intermediate Designs)Constraint Analysis Assumption Mapping

Criterion	Decision Making Pre-Mortem	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Constraint Analysis	Product Discovery Assumption Mapping
Purposedifferent	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.	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 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.	When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent	Low	Medium	Low	Medium
Timedifferent	20–45 min	2–4 h review as a planning range; preparation and evaluation additional	30-90 min	45-60 min
Participantsdifferent	Small cross-functional group	Designers, developers as users, and facilitation	2-8	2-8
Formatdifferent	Workshop	Workshop + async	Workshop + async	Workshop + async
Outputdifferent	Risk list, Mitigation plan, Assumption log	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries	Assumption map, Test backlog, Risk ranking
Tagsno overlap	RiskDecisionFailurePlanning	ArchitectureEngineeringFeedbackValidationTasks	ConstraintsDecisionPlanningOptions	AssumptionsRiskExperimentsValidation

Add more methods