View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Innovation Design Thinking |  Operations Fishbone Diagram |
|---|---|---|---|
Purposedifferent | 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 complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | High | High | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1 Tag bis mehrere Wochen | 30-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Problem Statement, Prototype, Test Learnings | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | InnovationPrototypeResearch | Root causeQualityOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
