View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Innovation Design Sprint |  Product Discovery Problem Interview |  Product Discovery Concierge MVP |
|---|---|---|---|---|
Purposedifferent | 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 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. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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 | Low | High | Medium | Medium |
Timedifferent | 15-45 min | 4-5 Tage | 30-60 min je Interview | 1-4 Wochen |
Participantsdifferent | 1-3 | 5-8 | 5-12 Interviews | 3-10 Kunden |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Prototype, Test Findings, Decision Rationale | Problem Evidence, Risk Notes, Customer Segments | Concierge Learnings, Service Blueprint, MVP Risks |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Design sprintPrototypeValidationInnovation | DiscoveryInterviewsValidation | MVPValidationServiceDiscovery |