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 Usability Testing | ![]() Product Discovery Problem Interview | ![]() Product Discovery MVP Test Matrix | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h je Session | 30-60 min je Interview | 45-75 min | 1-5 Tage |
Participantsdifferent | Based on research question | 5-12 Interviews | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Problem Evidence, Risk Notes, Customer Segments | Test Matrix, Test Plan | Click Data, Interest Signal, Learning Decision |
Tags1 shared | ValidationUXPrototype | DiscoveryInterviewsValidation | ExperimentsValidationDiscoveryOptions | ValidationExperimentsDemandDiscovery |



