View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Design Service Blueprinting | ![]() Product Discovery MVP Test Matrix | ![]() Product Discovery Smoke Test | ![]() Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | 0.5-2 Tage | 45-75 min | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 6-12 | 2-8 | Nutzertraffic | 1-6 |
Formatdifferent | Workshop | Workshop | Async | Async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Test Matrix, Test Plan | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | Service designOperationsJourneyBlueprint | ExperimentsValidationDiscoveryOptions | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |



