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)Evaporating Cloud Assumption Mapping Risk Storming

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Evaporating Cloud	Product Discovery Assumption Mapping	Architecture Risk Storming
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.	The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.	When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.	Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent	Medium	Medium	Medium	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	60-120 min	45-60 min	60-90 min
Participantsdifferent	Designers, developers as users, and facilitation	2-8	2-8	4-12
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	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Assumption map, Test backlog, Risk ranking	Annotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	Theory of ConstraintsAssumptionsSystems thinking	AssumptionsRiskExperimentsValidation	RiskArchitectureWorkshopValidation

Add more methods