View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Systems Thinking Evaporating Cloud |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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 | High |
Timedifferent | 1-3 h | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | 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 thinkingMappingBoundariesChange | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
