View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Discovery Opportunity Interview | ![]() Product Discovery Concierge MVP | ![]() Architecture Architecture Decision Record | ![]() Product Discovery Experiment Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 1-4 Wochen | 15-45 min | 30-60 min |
Participantsdifferent | 5-12 Interviews | 3-10 Kunden | 1-3 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Concierge Learnings, Service Blueprint, MVP Risks | ADR File, Decision Log, Rationale | Completed Experiment Canvas, Success Metric |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | MVPValidationServiceDiscovery | ArchitectureRationaleDocumentationGovernance | ExperimentsValidationDiscoveryHypothesis |



