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 |  UX Research Affinity Diagramming |  Product Discovery Pretotyping |  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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30–60 min | 45–90 min | Stunden bis wenige Tage | 60-90 min |
Participantsdifferent | 4-8 | 3-10 | 1-4 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Empathy Map, Assumptions List, Research Gaps | Theme clusters, Insight statements, Opportunity areas | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | SynthesisQualitativeWorkshop | SynthesisQualitativeRoot cause | ValidationDemandMVP | RiskArchitectureWorkshopValidation |