View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling PARA Method |  Product Discovery Wizard of Oz Test |  Product Discovery Solution Interview |  UX Research Usability Testing |
|---|---|---|---|---|
Purposedifferent | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | When a new experience would still be too expensive to automate for real, it simulates the outcome behind the scenes. It checks user reaction and value before the technology disappears. | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h Setup, laufend | 2-10 Tage | 30-60 min je Interview | 1-2 h je Session |
Participantsdifferent | 1 | 5-20 Nutzer | 5-10 Interviews | Based on research question |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Prototype Learnings, Manual Effort Notes, Risk List | Solution Feedback, Objection List, Validation Notes | Usability Issues, Severity List, Recommendations |
Tagsno overlap | KnowledgeProductivityOrganization | PrototypeValidationMVP | ValidationInterviewsPrototype | ValidationUXPrototype |