View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:CATWOE AnalysisTheory of Constraints Thinking ProcessATAM (Architecture Tradeoff Analysis Method)
| Criterion | ![]() Systems Thinking CATWOE Analysis | ![]() Systems Thinking Theory of Constraints Thinking Process | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. | 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 | High | High |
Timedifferent | 45-90 min | 0.5-3 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | 4-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles | 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 thinkingFramingStakeholders | Theory of ConstraintsConstraintsSystems thinkingCausality | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






