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:Evaporating Cloud Knowledge Mapping ATAM (Architecture Tradeoff Analysis Method)Assumption Mapping

Criterion	Systems Thinking Evaporating Cloud	Knowledge Modeling Knowledge Mapping	Architecture ATAM (Architecture Tradeoff Analysis Method)	Product Discovery Assumption Mapping
Purposedifferent	The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.	Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.	ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.	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	High	Medium
Timedifferent	60-120 min	1-3 h	Several meetings plus preparation and analysis; total effort depends on scope	45-60 min
Participantsdifferent	2-8	3-12	Evaluation team, architects, and relevant stakeholders	2-8
Formatdifferent	Workshop	Workshop	Workshop + async	Workshop + async
Outputdifferent	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Knowledge Map, Critical Knowledge Areas, Transfer Plan	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Assumption map, Test backlog, Risk ranking
Tagsno overlap	Theory of ConstraintsAssumptionsSystems thinking	KnowledgeMappingRisk	ArchitectureQualityRiskTradeoffsStakeholders	AssumptionsRiskExperimentsValidation

Add more methods