Minimum Viable Product (MVP): Building the Right Thing First

1. What an MVP Really Is (and Is Not)

In this module, you connect your value proposition and lean business model to a concrete first version of your product: the Minimum Viable Product (MVP).

Practical definition

A Minimum Viable Product is:

> The smallest thing you can build to *reliably test one key assumption* about your idea with real users.

Key parts of this definition:

• Minimum: as little as possible in terms of features, time, and cost.
• Viable: good enough that users can realistically interact with it and you can trust the feedback.
• Product: not always a full product; it can be a prototype, landing page, demo, or service that simulates the product.

Common misconceptions

An MVP is not:

• ❌ A low-quality, buggy version of your final product.
• ❌ “Version 1.0” with all core features squeezed in.
• ❌ An excuse to ship something you are ashamed of and never improve.

An MVP is:

• ✅ A learning tool to test your riskiest assumptions.
• ✅ A way to reduce waste by avoiding building features nobody wants.
• ✅ A temporary experiment, not your long-term architecture or design.

Keep this in mind: MVPs are about learning, not launching.

2. Identify Your Riskiest Assumption

Before choosing an MVP type, you must know what you are testing.

Quick exercise

Take your value proposition from the previous module. In your notes, write answers to these prompts:

1. Who is your primary customer segment?
2. What problem are you solving for them?
3. What is your boldest assumption right now? For example:

• They have this problem and care enough to solve it.
• They will pay for my solution.
• They will switch from their current alternative.
• I can deliver this solution at a reasonable cost.

Now, pick one riskiest assumption:

• If this assumption is wrong, your whole idea collapses.

Write a one-line hypothesis:

> "I believe that [customer segment] will [behavior] when they see [offer], because [reason]."

You will design your MVP around testing this hypothesis.

3. Types of MVPs (Digital and Non-Digital)

There are many MVP formats. You choose based on what assumption you are testing and how much effort you can invest.

Common MVP types

1. Landing Page MVP

• A simple webpage describing your product with a clear call to action (e.g., “Join waitlist”, “Pre-order”, “Book a demo”).
• Tests: Interest, value proposition clarity, pricing sensitivity.

1. Clickable Prototype / Mockup

• Designed in tools like Figma, Adobe XD, or even PowerPoint; looks real but is not fully functional.
• Tests: Usability, feature priorities, user flow.

1. Concierge MVP

• You manually do what the product is supposed to automate (e.g., you personally match users to products instead of using an algorithm).
• Tests: Problem–solution fit, willingness to pay, workflow.

1. Wizard of Oz MVP

• The front-end looks like a finished product, but you handle the back-end manually.
• Tests: Demand and behavior at scale, without building complex tech.

1. No-Code MVP

• Built with tools like Webflow, Bubble, Airtable, Zapier/Make, or Shopify.
• Tests: End-to-end journey, basic operations, and sometimes payment.

1. Explainer Video MVP

• Short video explaining your product (common in early Dropbox days).
• Tests: Understanding and interest (tracked via views, sign-ups, or shares).

1. Paper Prototype / Physical Mockup (for non-digital products)

• Sketches, cardboard models, 3D-printed rough shapes.
• Tests: Form factor, basic interactions, user reactions.

1. Pilot / Small-Scale Trial

• Limited rollout with a few users or one organization.
• Tests: Real-world usage, operations, and early unit economics.

You rarely need to build code-heavy products first. Pick the lightest MVP that still gives you reliable learning.

4. Matching MVP Types to Assumptions (Examples)

Here are three short scenarios to show how to choose an MVP type.

Example 1: Language-learning mobile app

• Riskiest assumption: Students will practice daily if the lessons are short and gamified.
• MVP choice: Clickable prototype + small concierge test.
• Create a Figma prototype of 3 lesson screens.
• Run 1-week test with 10 students where you manually send daily lesson links and track responses.
• Why this MVP? You are testing engagement behavior, not your full tech stack.

Example 2: Healthy lunch subscription for office workers

• Riskiest assumption: Enough employees in one building will subscribe weekly to make delivery viable.
• MVP choice: Landing page + concierge delivery.
• Landing page describing plans and collecting pre-orders.
• For a small group of early adopters, you personally cook or source meals and deliver them.
• Why this MVP? You test demand and pricing before investing in a kitchen or app.

Example 3: B2B analytics dashboard

• Riskiest assumption: Managers will actually use data dashboards weekly to make decisions.
• MVP choice: Wizard of Oz.
• Build a simple front-end dashboard with sample charts.
• Behind the scenes, you manually pull data into spreadsheets and update charts.
• Why this MVP? You test usage and decision impact before building a full data pipeline.

Notice the pattern: each MVP is designed specifically around the riskiest assumption, not around building a full product.

5. The Build–Measure–Learn Loop

The MVP sits inside a Build–Measure–Learn feedback loop, a core idea from Eric Ries’ Lean Startup (still widely used in 2026).

Imagine a simple cycle:

1. Build: Create the smallest experiment (MVP) to test your hypothesis.
2. Measure: Collect data on how people actually behave.
3. Learn: Decide whether to pivot, persevere, or pause.

Example cycle (landing page MVP)

• Build: A one-page site with your value proposition and a "Join Waitlist" button.
• Measure: Track:
• Number of visitors.
• Percentage who click the button (conversion rate).
• Emails collected.
• Learn:
• If conversion ≥ 25% from a relevant audience → Persevere and refine.
• If conversion 5–10% → Iterate: change headline, benefits, or target segment.
• If near 0% after multiple tests → consider a pivot (change problem, solution, or segment).

The loop should be fast. For early-stage ideas, your cycle time is often days or weeks, not months.

6. Design Your MVP Experiment (Template)

Use this lightweight template to design an MVP experiment for your idea.

In your notes, fill in:

1. Hypothesis

I believe that [customer segment] will [behavior] when they see [offer/MVP] because [reason].

1. MVP Type

Choose one: landing page, prototype, concierge, Wizard of Oz, no-code app, explainer video, paper prototype, pilot, etc.

1. What exactly will you build?

Be specific and small:

• Example: One-page website with headline, 3 benefits, price range, and an email sign-up form.

1. Success metric (primary)

Pick one main metric:

• Sign-up rate
• Click-through rate
• Pre-orders
• Meeting bookings
• Weekly active users, etc.

1. Success threshold (decision rule)

Define before you run the test:

• If ≥ X, we continue or invest more.
• If between Y and X, we iterate and retest.
• If < Y, we reconsider the idea or pivot.

1. Time box

Decide how long you will run the experiment (e.g., 7 days, 20 sign-ups, 5 customer interviews).

This structure forces you to treat your MVP as a controlled experiment, not a vague “launch.”

7. Simple MVP Metrics Tracking (Example Code)

For digital MVPs, you often need basic tracking. Here is a minimal JavaScript example to track button clicks on a landing page and log them (in reality you would connect this to an analytics tool or backend).

```html

<!DOCTYPE html>

<html>

<head>

<title>MVP Landing Page</title>

</head>

<body>

<h1>Learn Spanish in 10 Minutes a Day</h1>

<p>Short, gamified lessons for busy students.</p>

<button id="cta">Join the Beta</button>

<script>

let clickCount = 0;

document.getElementById('cta').addEventListener('click', () => {

clickCount++;

console.log('CTA clicked', clickCount, 'times');

// In a real MVP, you might send this to your backend:

// fetch('/track', {

// method: 'POST',

// headers: { 'Content-Type': 'application/json' },

// body: JSON.stringify({ event: 'cta_click', timestamp: Date.now() })

// });

});

</script>

</body>

</html>

```

You do not need complex analytics at first. Simple counts of visitors and conversions are often enough to drive early decisions.

8. Check Understanding: What Counts as an MVP?

Answer this question to check your understanding of MVP basics.

9. Check Understanding: Choosing MVP Types

Choose the most appropriate MVP type for the scenario.

10. Review Key Terms

Flip the cards (mentally or with a partner) to review the key concepts from this module.

11. Plan Your Next Move (Apply to Your Idea)

To close the module, connect this to your own project.

In your notes, answer briefly:

1. What is your riskiest assumption right now?

(About problem, solution, customer, or revenue.)

1. Which MVP type will you use first, and why?

1. What will you measure to decide if the MVP is a success?

1. What is your decision rule?

Complete this sentence:

• If [metric] is ≥ [number] after [time/volume], I will [next action]. If not, I will [alternative action].

Share your answers with a classmate or in a discussion group and challenge each other: Is this really the minimum thing you can build to learn?