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 MappingATAM (Architecture Tradeoff Analysis Method)Causal Loop DiagramARID (Active Reviews for Intermediate Designs)
| Criterion |  Systems Thinking Polarity Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking Causal Loop Diagram |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | 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. | A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 2-8 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Causal Loop Diagram, Feedback Notes, Leverage Points | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureQualityRiskTradeoffsStakeholders | FeedbackSystems thinkingCausalityDynamics | ArchitectureEngineeringFeedbackValidationTasks |