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)Three AmigosArchitecture Communication Canvas
| Criterion |  Systems Thinking Polarity Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Three Amigos |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min | 60-120 min |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 3 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | 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 | Clarified Story, Test Examples, Open Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureQualityRiskTradeoffsStakeholders | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureCommunicationStakeholdersCanvas |