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 C4 Model |  Product Discovery Problem Interview |  Product Discovery Learning Card |  Product Discovery MVP Test Matrix |
|---|---|---|---|---|
Purposedifferent | 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 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-4 h | 30-60 min je Interview | 25-40 min | 45-75 min |
Participantsdifferent | 1-5 | 5-12 Interviews | 1-5 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Problem Evidence, Risk Notes, Customer Segments | Learning Card with evidence and next action | Test Matrix, Test Plan |
Tagsno overlap | ArchitectureCommunicationVisualization | DiscoveryInterviewsValidation | ExperimentsValidationDiscoveryLearning | ExperimentsValidationDiscoveryOptions |