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 Discovery Context Canvas |  UX Design Design Studio |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | When several designs need to be quickly put in relation to each other, it makes ideas visible and comparable. It encourages early variants instead of long upfront debates. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 45-90 min | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 3-10 | 3-8 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Context canvas, Open questions, Shared context notes | Sketches, Concept Directions, Design Decisions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | ContextFramingRequirementsCanvas | SketchingCollaborationIdeation | ArchitectureQualityRiskTradeoffsStakeholders | Systems thinkingFramingStakeholders |