Plan my session
Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.
Session: MVP Test Matrix
The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.
Method session with 2-8. The plan uses the existing method logic and the runsheet.
RunsheetUse the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
The session works directly toward Test-Matrix. After the session, the artifact should be shareable, reviewable, or reusable.
- 1
Phase 1: Categorize assumptions and dimensions
15 minClarify the dimension for each assumption (Desirability = will someone want it, Feasibility = can we build it, Viability = is it economically viable). Mark assumptions on cards. Hint: Assumption dimension drives format choice. Desirability rarely fits smoke test, Feasibility rarely fits survey. Clear assignment avoids format reflexes.
FacilitatorTest-Matrix - 2
Phase 2: Explain format options
15 minFor each test format explain output, effort, and suitable dimensions. Add examples from Testing-Business-Ideas or previous tests. Hint: Participants often only know two to three formats. Expanding repertoire is part of the workshop value. Present at least seven to ten formats clearly.
FacilitatorTest-Plan - 3
Phase 3: Fill the matrix
20-30 minDiscuss suitable format for each assumption. In each matrix cell, note the rationale briefly. A format can cover several assumptions, but one assumption should get a primary format. Hint: Participants who select the same format for every assumption (for example always interview) are not using the repertoire. Ask for alternatives.
FacilitatorTest-Matrix - 4
Phase 4: Derive test plan
10-15 minConvert top-five assumptions with assigned formats into a test plan. Define owner, start date, and budget per test. Limit parallel tests to max three. Hint: A test plan without owner and date is only a wish list. The workshop ends with a concrete calendar plan, not the matrix alone.
OwnerTest-Plan - 5
Publish artifact
10 minCheck the artifact for completeness, define location, set version or status, and name review recipients.
OwnerTest-Matrix
Session Brief
For invitations, boards, tickets, PR descriptions, or workshop notes.
session-brief.md
Session Brief: MVP Test Matrix
Goal
Artifact: Test-Matrix
Working Question
Which test format best fits each assumption, and which mix of formats tests the open assumption pipeline most efficiently?
Context
Assumption list with dimensions (Desirability/Feasibility/Viability); list of available test formats with short descriptions; budget and time range for each test.
Setup
- Format: Method session
- Duration: 45-75 min
- Mode: Workshop
- Participants: A discovery lead who walks the matrix, designer and engineer for feasibility judgment, a data analyst for metric questions, and optionally a coach for format choice.
- Owner: A discovery lead who walks the matrix, designer and engineer for feasibility judgment, a data analyst for metric questions, and optionally a coach for format choice
- Participation mode: Team round, shared work and alignment
- Outcome logic: Finish artifact
Participation Logic
Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
Outcome Logic
The session works directly toward Test-Matrix. After the session, the artifact should be shareable, reviewable, or reusable.
Input
Matrix template (assumptions as columns, test formats as rows) as board or printout; assumption list; format description with typical effort and output; examples from Strategyzer/Testing-Business-Ideas.
Preparation
Set up matrix: assumptions vertically, test formats horizontally (Interview, Survey, Fake-Door, Landing Page, Concierge, Wizard-of-Oz, Prototype, Smoke Test, A/B). Keep format descriptions visible as banners.
Agenda
-
Phase 1: Categorize assumptions and dimensions (15 min) Owner: Facilitator Action: Clarify the dimension for each assumption (Desirability = will someone want it, Feasibility = can we build it, Viability = is it economically viable). Mark assumptions on cards. Hint: Assumption dimension drives format choice. Desirability rarely fits smoke test, Feasibility rarely fits survey. Clear assignment avoids format reflexes. Output: Test-Matrix
-
Phase 2: Explain format options (15 min) Owner: Facilitator Action: For each test format explain output, effort, and suitable dimensions. Add examples from Testing-Business-Ideas or previous tests. Hint: Participants often only know two to three formats. Expanding repertoire is part of the workshop value. Present at least seven to ten formats clearly. Output: Test-Plan
-
Phase 3: Fill the matrix (20-30 min) Owner: Facilitator Action: Discuss suitable format for each assumption. In each matrix cell, note the rationale briefly. A format can cover several assumptions, but one assumption should get a primary format. Hint: Participants who select the same format for every assumption (for example always interview) are not using the repertoire. Ask for alternatives. Output: Test-Matrix
-
Phase 4: Derive test plan (10-15 min) Owner: Owner Action: Convert top-five assumptions with assigned formats into a test plan. Define owner, start date, and budget per test. Limit parallel tests to max three. Hint: A test plan without owner and date is only a wish list. The workshop ends with a concrete calendar plan, not the matrix alone. Output: Test-Plan
-
Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Test-Matrix
Closeout
- Update result artifact: Test-Matrix
- Define location, version, and review recipients.
- Define owner, next step, and review date.
Work artifact
Pre-filled starting point based on the matching template.
work-artifact.md
Test-Matrix: MVP Test Matrix
Working Question
Which test format best fits each assumption, and which mix of formats tests the open assumption pipeline most efficiently?
Context
Assumption list with dimensions (Desirability/Feasibility/Viability); list of available test formats with short descriptions; budget and time range for each test.
Participants
- Owner: A discovery lead who walks the matrix, designer and engineer for feasibility judgment, a data analyst for metric questions, and optionally a coach for format choice
- Participants: A discovery lead who walks the matrix, designer and engineer for feasibility judgment, a data analyst for metric questions, and optionally a coach for format choice.
Input
Matrix template (assumptions as columns, test formats as rows) as board or printout; assumption list; format description with typical effort and output; examples from Strategyzer/Testing-Business-Ideas.
Template
MVP Test Matrix Working Matrix
| Element | Description | Rating | Evidence | Owner | Next step |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 |
Output artifacts
- Test Matrix:
- Test Plan:
Decision or recommendation
What consequence follows from the matrix?
Completion Check
- Test-Matrix is complete enough for review:
- Location:
- Version / status:
- Review by:
- Next step:
Next Step
- Review result
- Mark open questions
- Schedule review or decision
MVP Test Matrix Working Template
View templateCompact working template for MVP Test Matrix with context, input, output artifacts, and next step.spreadsheet
mvp-test-matrix-working-template.md
Compact working template for MVP Test Matrix with context, input, output artifacts, and next step.
MVP Test Matrix Working Matrix
| Element | Description | Rating | Evidence | Owner | Next step |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 |
Output artifacts
- Test Matrix:
- Test Plan:
Decision or recommendation
What consequence follows from the matrix?
- Working question, owner, and target artifact are visible.
- The result fits Test-Matrix.
- Snapshot per discovery sprint. Document completed tests with outcome and date. Capture format learnings (what worked) in the team wiki as lessons learned.
- Open questions are noted as follow-ups.
- The next review or decision point is scheduled.