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 MappingARID (Active Reviews for Intermediate Designs)Evaporating CloudATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Systems Thinking Polarity Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Systems Thinking Evaporating Cloud |  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. | 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. | 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 | 2–4 h review as a planning range; preparation and evaluation additional | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | Designers, developers as users, and facilitation | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | 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 | 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 | ArchitectureEngineeringFeedbackValidationTasks | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureQualityRiskTradeoffsStakeholders |