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 | ![]() UX Research Usability Testing | ![]() Product Discovery Wizard of Oz Test | ![]() Product Discovery Concierge MVP |
|---|---|---|---|---|
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 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 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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h Setup, laufend | 1-2 h je Session | 2-10 Tage | 1-4 Wochen |
Participantsdifferent | 1 | Based on research question | 5-20 Nutzer | 3-10 Kunden |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Usability Issues, Severity List, Recommendations | Prototype Learnings, Manual Effort Notes, Risk List | Concierge Learnings, Service Blueprint, MVP Risks |
Tagsno overlap | KnowledgeProductivityOrganization | ValidationUXPrototype | PrototypeValidationMVP | MVPValidationServiceDiscovery |



