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 Pretotyping |  Innovation Design Sprint |  Innovation Lean Startup |
|---|---|---|---|---|
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. | 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. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-2 h je Session | Stunden bis wenige Tage | 4-5 Tage | Wochen bis Monate je Lernzyklus |
Participantsdifferent | Based on research question | 1-4 | 5-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Prototype, Test Findings, Decision Rationale | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tags1 shared | ValidationUXPrototype | ValidationDemandMVP | Design sprintPrototypeValidationInnovation | LeanStartupValidationMVP |