methodatlas

Product Discovery Research method

MVP Test Matrix

Matches critical assumptions to a test whose evidence strength, cost, duration, and realism fit the next decision.

The matrix prevents MVP from automatically meaning a small product. A fake door can test demand, concierge can observe value in a workflow, Wizard of Oz can test use of a manually delivered service, and a functional prototype can test feasibility. A test only answers the assumption it was designed for.

Core question
Which smallest test provides enough evidence for each critical assumption to support the next investment decision?
Participants
2-8
Time
45-75 min

Test type follows the assumption. Fake door, concierge, Wizard of Oz, prototype, and spike create different evidence and cannot support the same claim.

Paper illustration of MVP Test Matrix with a method-specific labelled workspace.
  1. Assumptions

    Bound decision and assumptions

    Expose critical desirability, viability, feasibility, and adaptability assumptions.

  2. Match

    Match test type to evidence need

    Choose a test type with suitable evidence strength and realism for each top assumption.

  3. Protocol

    Make the test decision-capable

    Document population, procedure, metric, threshold, and guardrails before launch.

  4. Sequence

    Plan evidence ladder and next test

    Set the next test and the condition for moving to stronger evidence.

Start with cheaper, weaker evidence and move deliberately toward behaviourally stronger tests when results justify it.

A good fit when

Useful when critical assumptions and an investment decision are known. Use interviews or field observation first for open problem discovery.

Ideal for

  • Discovery coaching
  • Innovation teams
  • Test backlog building

Not good for

  • Pure execution sprints

Outputs

  • Assumption-test mapping

    Critical assumptions with suitable test type, evidence strength, effort, and explicit limit.

  • Sequenced MVP test plan

    Pre-set rules, guardrails, owners, and transition to the next stronger test.

MVP Test Matrix

Fictional worked example

Connect assumptions to test type, evidence strength, effort, and a pre-set decision.

MVP Test Matrix
AssumptionCritical assumptionSuitable test typeObservation and evidenceEffort and guardrailThreshold and next test
Review useDesirability before automationProject leads use audit-ready exports in monthly reviews.Concierge: manually prepared export for 12 suitable teams.Observed review use; stronger than stated intent, no self-service evidence yet.5 working days; no sensitive production data; stop on compliance objection.Pass ≥8 in review and ≥6 using a chart; then clickable prototype, else revisit segment/job.
  1. 1. Critical assumption

    Review use
    Project leads use audit-ready exports in monthly reviews.
  2. 2. Suitable test type

    Review use
    Concierge: manually prepared export for 12 suitable teams.
  3. 3. Observation and evidence

    Review use
    Observed review use; stronger than stated intent, no self-service evidence yet.
  4. 4. Effort and guardrail

    Review use
    5 working days; no sensitive production data; stop on compliance objection.
  5. 5. Threshold and next test

    Review use
    Pass ≥8 in review and ≥6 using a chart; then clickable prototype, else revisit segment/job.

An MVP test validates only the assumption its measure actually addresses.

Strategyzer: Select the Next Best Test

First step

Start with the core question: Which smallest test provides enough evidence for each critical assumption to support the next investment decision?

Open the method guide

Deep dive

Purpose

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.

How it works

It places possible MVP forms alongside the hypotheses they are meant to test and the matching measurement logic. The comparison shows which test form delivers enough evidence and which variant would be too large or too weak.

In detail

The MVP Test Matrix is based on work by Strategyzer and David Bland. It maps assumptions across three dimensions, often desirability, feasibility, and viability, and shows which test design fits each assumption best. That prevents teams from reflexively using the same format for every risk.

Facilitation

Bring concrete examples of common test formats. Ask the team to explain why a format fits, not only which one they choose.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics
Artifact templates
MVP Test Matrix: WorksheetPlan MVP Test Matrix with real scope, suitable roles, and a clear decision objective.
markdown

mvp-test-matrix-working-template.md

Plan MVP Test Matrix with real scope, suitable roles, and a clear decision objective.

MVP Test Matrix: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Plan the full workshop Time: 45–60 minutes for selection and protocol

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Assumption portfolio, test-type catalogue, audience access, cost and time constraints, analytics plan, and ethics review.
  • Roles: Product · Research · Engineering · Analytics · experiment owner
  • Advance information: Prepare top assumptions, current evidence, and the next irreversible investment.
  • Overall time needed: 45–60 minutes for selection and protocol
  • Setup: Compare test types by evidence strength, setup time, run time, cost, and realism.

Prepare for the work steps

Assumptions: Bound decision and assumptions

  • Upcoming investment decision
  • Product or business model
  • Current evidence

Match: Match test type to evidence need

  • Prioritised assumptions
  • Available test types
  • Audience access and constraints

Protocol: Make the test decision-capable

  • Selected test type
  • Audience and channel
  • Baseline or comparison

Sequence: Plan evidence ladder and next test

  • Test protocols
  • Investment stages
  • Time and cost budget

MVP Test Matrix

Assumptionassumption · dimensionfake door/concierge/wizard/prototype/spikebehaviour · strength · limitduration · cost · guardrailpass · fail · next
Review use
  • Review use: Desirability before automation

Choose test type after assumption and decision; record the evidence limit.

Strategyzer: Select the Next Best Test

Assumptions: Bound decision and assumptions

Expected artifact: Assumption portfolio

Dimension · assumption · evidence gap · decision

Entry:

...

  • Is it clear which decision each test supports?

Match: Match test type to evidence need

Expected artifact: Test matrix

Assumption · test type · evidence strength · effort · limit

Entry:

...

  • Does the test measure the claimed dimension?

Protocol: Make the test decision-capable

Expected artifact: Test protocol

Population · procedure · metric · threshold · guardrail · decision

Entry:

...

  • Can the team evaluate results without inventing new rules?

Sequence: Plan evidence ladder and next test

Expected artifact: Sequenced test plan

Now · threshold · next · owner · review

Entry:

...

  • Does evidence strength increase only after a viable result?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/mvp-test-matrix/run-sheet

Alternatives and neighbors

Fitting alternatives with decision guidance, followed by other related methods.

All methods
Constraints and origin
MediumWorkshop45-75 min

Profile

Method form
Research method
Participants
2-8
Time
45-75 min
Maturity
Established
Origin
Lean Startup Community
Paper illustration for Smoke Test.
Next up: Smoke Test