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

Criterion	Systems Thinking Polarity Mapping	Systems Thinking Evaporating Cloud	Product Discovery Assumption Mapping	Architecture ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent	Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.	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.	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.
Complexitydifferent	Medium	Medium	Medium	High
Timedifferent	1-2 h	60-120 min	45-60 min	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	3-12	2-8	2-8	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Workshop	Workshop	Workshop + async	Workshop + async
Outputdifferent	Polarity Map, Warning Signs, Balance Actions	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	Assumption map, Test backlog, Risk ranking	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap	Systems thinkingTradeoffsLeadership	Theory of ConstraintsAssumptionsSystems thinking	AssumptionsRiskExperimentsValidation	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods