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

Criterion	Engineering Failure Scenario Analysis	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Pre-Mortem	Product Discovery Assumption Mapping
Purposedifferent	In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.	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.	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.	When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent	Medium	Medium	Low	Medium
Timedifferent	1-3 h	2–4 h review as a planning range; preparation and evaluation additional	20–45 min	45-60 min
Participantsdifferent	3-8	Designers, developers as users, and facilitation	Small cross-functional group	2-8
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop + async
Outputdifferent	Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Risk list, Mitigation plan, Assumption log	Assumption map, Test backlog, Risk ranking
Tagsno overlap	FailureResilienceRisk	ArchitectureEngineeringFeedbackValidationTasks	RiskDecisionFailurePlanning	AssumptionsRiskExperimentsValidation

Add more methods