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:Assumption Surfacing Red Teaming ARID (Active Reviews for Intermediate Designs)Assumption Mapping

Criterion	Decision Making Assumption Surfacing	Decision Making Red Teaming	Architecture ARID (Active Reviews for Intermediate Designs)	Product Discovery Assumption Mapping
Purposedifferent	Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.	For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.	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.
Complexitydifferent	Low	High	Medium	Medium
Timedifferent	45-90 min	1-4 h	2–4 h review as a planning range; preparation and evaluation additional	45-60 min
Participantsdifferent	2-8	3-8	Designers, developers as users, and facilitation	2-8
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop + async
Outputdifferent	Assumption List, Critical Assumptions, Learning Plan	Challenge Findings, Risk Register, Mitigation Plan	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Assumption map, Test backlog, Risk ranking
Tagsno overlap	AssumptionsRiskDecisionDiscovery	RiskDecisionSensemaking	ArchitectureEngineeringFeedbackValidationTasks	AssumptionsRiskExperimentsValidation

Add more methods