View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Empathy Mapping |  Product Discovery Smoke Test |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 30–60 min | 1-5 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min |
Participantsdifferent | 4-8 | Nutzertraffic | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Empathy Map, Assumptions List, Research Gaps | Interest Metrics, Conversion Signal, Learning Note | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | SynthesisQualitativeWorkshop | ValidationExperimentsDemandGrowth | ArchitectureQualityRiskTradeoffsStakeholders | RiskArchitectureWorkshopValidation |