8.1 Building and Launching the MVP (Minimum Viable Product)

What is an MVP?

A Minimum Viable Product (MVP) is the simplest version of a product that can be released to real users. It contains only the core features needed to solve the primary problem for early adopters, allowing the team to collect the maximum amount of validated learning with the least effort and cost.

MVP vs. Prototype

---

Why Launch an MVP?

Launching an MVP before a full-scale product helps entrepreneurs:

1. Reduce risk — Avoid building features nobody wants.
2. Save resources — Invest time and money only in validated ideas.
3. Gather real feedback — Learn from actual user behaviour, not assumptions.
4. Reach market faster — Get a working product in front of customers quickly.

---

The Build-Measure-Learn Feedback Loop

The MVP process is driven by the Build-Measure-Learn cycle, introduced by Eric Ries in The Lean Startup:

  ┌─────────┐
  │  BUILD  │  ← Develop the smallest testable feature set
  └────┬────┘
       ↓
  ┌─────────┐
  │ MEASURE │  ← Collect user metrics, feedback, and analytics
  └────┬────┘
       ↓
  ┌─────────┐
  │  LEARN  │  ← Decide: Pivot (change direction) or Persevere (continue)?
  └────┬────┘
       └──────────────────────────────────────────────────────────────────┐
                                                                          ↓
                                                                    Next iteration

Steps in Detail

• Build: Implement only the features that test your core hypothesis. Avoid feature creep.
• Measure: Use analytics tools to track how users interact with the product. Key metrics include user retention, conversion rate, and task completion rate.
• Learn: Analyse the data. If the hypothesis is validated, persevere (continue building). If not, pivot (change the product, target audience, or business model).

---

Techniques Used During MVP Iteration

A/B Testing

A/B testing (also called split testing) is a method of comparing two versions of a feature, page, or design to determine which performs better with real users.

• Version A is shown to one group of users.
• Version B is shown to another group.
• The version with better metrics (e.g., higher click-through rate) is adopted.

Example: An e-commerce startup tests two checkout button colours — green vs. orange — to see which leads to more purchases.

User Feedback Collection

• Surveys and interviews
• In-app feedback forms
• Usage analytics (heatmaps, session recordings)

---

Steps to Build and Launch an MVP

1. Identify the core problem your product solves.
2. Define your target audience (early adopters).
3. List all possible features, then ruthlessly cut to the minimum needed.
4. Build the MVP using agile/iterative development.
5. Launch to a small user group (beta users).
6. Measure and collect data on user behaviour.
7. Learn and iterate — apply the Build-Measure-Learn loop.

---

Key Terms