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 Concierge MVP | ![]() Product Discovery Fake Door Test | ![]() Product Discovery Learning Card |
|---|---|---|---|---|
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 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. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 1-4 h | 1-4 Wochen | 1-5 Tage | 25-40 min |
Participantsdifferent | 1-5 | 3-10 Kunden | Nutzertraffic | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Concierge Learnings, Service Blueprint, MVP Risks | Click Data, Interest Signal, Learning Decision | Learning Card with evidence and next action |
Tagsno overlap | ArchitectureCommunicationVisualization | MVPValidationServiceDiscovery | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryLearning |



