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)Theory of Constraints Thinking Process Evaporating Cloud Assumption Mapping

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Theory of Constraints Thinking Process	Systems Thinking Evaporating Cloud	Product Discovery Assumption Mapping
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 Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship.	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.
Complexitydifferent	Medium	High	Medium	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	0.5-3 Tage	60-120 min	45-60 min
Participantsdifferent	Designers, developers as users, and facilitation	4-10	2-8	2-8
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Assumption map, Test backlog, Risk ranking
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	Theory of ConstraintsConstraintsSystems thinkingCausality	Theory of ConstraintsAssumptionsSystems thinking	AssumptionsRiskExperimentsValidation

Add more methods