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 MappingMORT AnalysisATAM (Architecture Tradeoff Analysis Method)Family Tree Analysis
| Criterion |  Systems Thinking Polarity Mapping |  Operations MORT Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Family Tree Analysis |
|---|---|---|---|---|
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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 1-2 h | Mehrere Tage bis Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h |
Participantsdifferent | 3-12 | 2-6 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Systems thinkingTradeoffsLeadership | Root causeSafetySystemicIncident | ArchitectureQualityRiskTradeoffsStakeholders | Root causePatternsIncidentSystemic |