View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy Product Canvas |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Fishbone Diagram |
|---|---|---|---|
Purposedifferent | When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point. | 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 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 | Medium | High | Low |
Timedifferent | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Canvas, Product Assumptions, Scope Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | CanvasDiscoveryScope | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
