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)Cynefin Workshop Assumption Mapping Red Teaming

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Cynefin Workshop	Product Discovery Assumption Mapping	Decision Making Red Teaming
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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.	When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.	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.
Complexitydifferent	Medium	Medium	Medium	High
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	60-180 min	45-60 min	1-4 h
Participantsdifferent	Designers, developers as users, and facilitation	4-20	2-8	3-8
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Cynefin Map, Domain-specific Actions, Sensemaking Notes	Assumption map, Test backlog, Risk ranking	Challenge Findings, Risk Register, Mitigation Plan
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ComplexitySensemakingDecision	AssumptionsRiskExperimentsValidation	RiskDecisionSensemaking

Add more methods