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 Problem Interview |  Architecture Architecture Decision Record |  Architecture C4 Model |  Product Discovery Concierge MVP |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 15-45 min | 1-4 h | 1-4 Wochen |
Participantsdifferent | 5-12 Interviews | 1-3 | 1-5 | 3-10 Kunden |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Concierge Learnings, Service Blueprint, MVP Risks |
Tagsno overlap | DiscoveryInterviewsValidation | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | MVPValidationServiceDiscovery |