Minimum Viable Product (MVP)

Overview

A product development philosophy focused on testing core value propositions with the minimum functional set required for hypothesis validation. It is a model that prioritizes the “Speed of Learning” over initial “Completeness”. An MVP is not a “lite” version of a product, but the smallest thing you can build that lets you move through the Build-Measure-Learn feedback loop.

Rating (1–5)

• Versatility: 4
• Immediacy: 4
• Difficulty: 2
• Misuse Risk: 4

Evaluation Comment

An extremely powerful tool for reducing waste. However, it is frequently misunderstood as simply “Releasing unfinished work”. If the product is not “Viable” (i.e., it doesn’t actually solve the core problem), you won’t learn anything useful, and you may cause lasting brand damage.

The First Question

“What is the bare minimum we can build to sufficiently validate our riskiest hypothesis at the lowest cost and effort?”

Objectives

• To maximize the frequency of the “Learning Loop”.
• To prevent unnecessary “Over-engineering” before market fit is confirmed.
• To fail fast and cheap if the core idea is fundamentally flawed.

Poor Questions

• “Should we wait until it’s perfect before we release it?” (Perfection is the enemy of learning)
• “Won’t users be disappointed if we don’t include every feature?” (If the core value is high, users will tolerate missing secondary features)
• “How can we ensure it won’t fail?” (MVPs are designed to surface failure early)

How to Use (Step-by-Step)

1. Clarify the Hypothesis

   • State exactly what you believe to be true (e.g., “Users will pay $10/month for automated bookkeeping”).

2. Identify the “Viable” Core

   • Determine the absolute minimum functionality required for the user to experience the value. Avoid “feature creep.”

3. Build and Launch

   • Create the minimum configuration. This could be a landing page, a manual “Concierge” service, or a single-feature app.

4. Measure and Learn

   • Capture specific data (KPIs) and qualitative feedback. Decide whether to “Pivot” (change direction) or “Persevere” (improve the current path).

Output Examples

1. The Validation Plan

• Hypothesis: Professional consultants want a bilingual mental model dictionary.
• MVP: A simple Markdown-based static site with 10 core models.
• Metric: Number of return visitors and newsletter sign-ups.

2. Visualization

• The Iteration Loop: A circular diagram showing the flow from Hypothesis → MVP → Data/Learning → Improved Product.

Use Cases

• Business: Launching new digital services, testing new marketing channels, or internal tool development.
• Daily Life: Testing new habits (e.g., a “3-minute workout” before committing to a gym) or career experiments (e.g., a weekend freelance project).
• Decision Making: Small-scale validation before committing large amounts of capital or time to a project.

Typical Misuses

• The “M” without the “V”: Releasing a product so broken or low-quality that it cannot be used, leading to false negative results.
• No Learning Design: Releasing an MVP without a plan for how to collect or analyze data.
• Feature Bloat: Adding “just one more thing” until the MVP takes six months to build, defeating the purpose of speed.

Relationship with Other Models

• Higher-level Concept: Hypothesis-based Thinking.
• Complementary: OODA Loop (Observe-Orient-Decide-Act), Agile Methodology.