MVP Canvas: People Experience Edition

Why this exists

Teams often say “MVP” but imagine different end-states. This canvas gets us to a shared picture of “done” for a first, testable slice of a people experience, clear enough to build, test, and learn from.

What this canvas enables

• Paint “done” together: align on the first shippable version.

• Challenge levels of detail: what’s essential now vs. later.

• Define success & constraints: how we’ll measure, and what boxes us in.

• Plan AI & automation: decide if/how they help, or why they won’t (yet).

Facilitation Instructions

How to Run the Session

• Who to invite: initiative owner, designer/PM (or PX lead), data/analytics, ops/HRBP, a representative end-user

• First time use: Schedule 80 minutes to complete the canvas together. This ensures we align on goals, assumptions, and scope.

• Future uses: Each additional session for a new initiative should take ~40 minutes, depending on complexity and familiarity.

• Mindset: Be collaborative, curious, and realistic. We’re looking for a starting point, not a final polished plan.

• Materials: This Miro board, sticky notes, markers (or digital equivalents), and one facilitator.

60-minute agenda (facilitator script)

8 min – Set the frame

• Say: “We’re using this to align on an MVP—what we can ship to learn fastest.”

• Explain the skateboard vs. bicycle metaphor to illustrate different MVP visions.

• MVP = smallest usable version that delivers value and tests riskiest assumptions.

• Walk participants through each section of the canvas.

8 min – Should we be doing this? (DVF)

• Quiet fill: Add stickies under Desirability, Viability, Feasibility.

• Readout: Share key points.

• Vote: Red/yellow/green dots for confidence.

12 min – Jobs to Be Done

• Write JTBD statements individually.

• Cluster similar ones.

• Select the primary job the MVP will solve.

• Confirm alignment with business goals.

7 min – Stages & scope

• Show Design Thinking stages: Discover → Define → Develop → Deliver → Iterate.

• Dot vote on which stages will be incorporated for this MVP.

5 min – Challenge Zone (first row)

• Capture top risks, assumptions, and dependencies for the first row of sections.

10 min – MVP estimate

• Frame: “If we have

• X weeks

• to ship, what fidelity does this product need?”

• Team places dots next to the picture that matches their view (skateboard → car).

• Discuss differences and justify choices.

• Agree on a realistic timebox.

10 min – MVP in / out

• Put stickies in respective boxes Included vs Not included

• Keep only what’s needed to learn in the first iteration.

• Confirm each “in” item has an owner.

8 min – AI & automation

• Decide if AI or automation adds learning or speed.

• If yes: capture how and with what guardrails.

• If no: record why not and when to revisit.

5 min – Challenge Zone (second row)

• Add critiques/risks for MVP estimate, scope, AI, and automation decisions.

7 min – Costs & constraints + success measures

• List the biggest blockers (time, cost, compliance, stakeholder bandwidth).

• Define 3–5 measurable outcomes for MVP success.

• Agree on next step and decision date for MVP review.

Closing checkpoint By the end, the team should have:

• Definition of Done for MVP

• (what’s in/out, timebox, owner)

• Clear success metrics

• Key risks and constraints documented

• Agreement on review date