Lean Startup

🧠 What is MVP?

MVP (Minimum Viable Product) is a product prototype built with the lowest cost and only the core functionality, launched quickly to test whether the market and users truly need it.

MVP is not a “crude product,” but a minimal version that solves a problem and collects real feedback.

The concept was first introduced by the Lean Startup methodology, and it has become a key approach for entrepreneurs and product teams to reduce risk and test quickly.

🧪 Origin & Key Figures

• Origin: Introduced in the Lean Startup framework
• Key Figure: Eric Ries (author of The Lean Startup)
• Typical Cases: Dropbox, Buffer, and Airbnb all validated market demand through MVPs, avoiding huge investments in the wrong direction.

💡 Core Principles of MVP

1. Quickly Validate Hypotheses — don’t spend months or years building a full product; test key assumptions first.
2. Small, Fast Steps — launch with minimal features to see if users are willing to use or pay.
3. Reduce Risk — avoid massive waste caused by pursuing the wrong direction.
4. Data-Driven Decisions — use feedback and data to decide whether to continue, pivot, or stop.

📌 Common Types of MVP

• Single-Feature MVP: Implement only the core function (e.g., Dropbox initially only focused on “file synchronization”).
• Landing Page MVP: Create a simple page to test if users sign up (e.g., Buffer used a landing page for validation).
• Wizard of Oz MVP: Appears automated in the front end but is manually operated in the back end (e.g., Zappos founder personally buying shoes for customers).
• Prototype/Mockup MVP: Low-fidelity or interactive prototypes to gather early user feedback.

📚 Case Studies

• Case 1 (Business: Dropbox)

  Instead of building a full cloud storage system, Dropbox released a short demo video showing cross-device file sync.

  The result: thousands joined the waiting list, validating strong market demand.

  Insight: Even a simple demo can prove a big idea.

• Case 2 (Startup: Buffer)

  Buffer created a basic landing page explaining “scheduled social media posts” and measured sign-ups before building the product.

  Positive responses validated the concept.

  Insight: A simple web page can serve as a powerful MVP.

⚖️ Advantages & Limitations (Optional)

Advantages

• Validates market demand early
• Saves time and resources
• Enables rapid learning and iteration

Limitations

• Over-simplification may harm user experience
• Poor execution may fail to collect useful data
• Investors or users may misinterpret it as “unfinished”

❓ Frequently Asked Questions (Optional)

1. Isn’t an MVP too “basic”?
   • No. The goal is to validate assumptions, not to build perfection from the start.
2. Is MVP suitable for all projects?
   • Best for startups and innovation projects. Highly regulated industries (e.g., healthcare) may require compliance adjustments.

🎯 Application Scenarios (Optional)

• Work: new product development, market testing, user research
• Entrepreneurship: risk reduction, rapid experimentation
• Learning/Personal Projects: testing the feasibility of ideas

📖 Recommended Resources

Books

• Eric Ries: The Lean Startup — systematic explanation of the MVP concept
• Steve Blank: The Startup Owner’s Manual — emphasizes customer validation

Other Resources

• Dropbox startup story
• Buffer’s official startup blog

🔗 Related Methods (Optional)

• Lean Startup
• Agile Development
• Rapid Prototyping

💡 Key Takeaway

“MVP: Validate maximum value with minimum cost.”