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 Personas |  Product Discovery Opportunity Solution Tree |  Architecture arc42 |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Tage | 1-2 h Setup, laufend | 1-2 Tage | 30-60 min je Interview |
Participantsdifferent | Internes Team | 2-6 | 1-4 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Opportunity Solution Tree, Experiment Backlog, Learning Log | Architecture Document, Context View, Runtime View, Deployment View | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | ResearchCustomerSynthesis | DiscoveryOutcomesExperimentsOpportunity | ArchitectureDocumentationCommunication | DiscoveryInterviewsOpportunityCustomer |