Minimum Viable Product (MVP)

A Minimum Viable Product (MVP) is a version of a product with just enough features to satisfy early customers and provide feedback for future development. It's about learning, not perfection.

Core Concept

Not: Build everything, launch perfectly Instead: Build minimum, learn quickly, iterate

The goal: Validate assumptions with real users using the least resources possible.

What Makes a Good MVP

Viable: Actually solves a real problem Minimum: Only essential features included Product: Delivers real value, not just a prototype

Example - Dropbox MVP:

• Not: Full product with all features
• Instead: Simple video showing how it would work
• Result: Validated demand before building

Why MVPs Matter

Reduce Risk:

• Test ideas cheaply
• Fail fast if wrong
• Don't waste months building unwanted features

Learn Faster:

• Real user feedback
• Actual behavior data
• Iterate based on evidence

Save Resources:

• Less time and money
• Focus on what matters
• Build only what's needed

Get to Market Quickly:

• Beat competitors
• Start earning revenue
• Build reputation early

MVP is NOT

❌ A prototype: MVPs are real products people use ❌ Buggy software: Basic ≠ broken ❌ No design: Must still be usable ❌ Feature-complete: That's version 2.0 ❌ The final product: It's the starting point

Types of MVPs

Smoke Test MVP:

• Landing page describing product
• Measures interest (sign-ups, pre-orders)
• Validates demand before building

Concierge MVP:

• Manually do what software will eventually do
• Learn exact workflow needed
• Example: Doing tasks for users before automating

Wizard of Oz MVP:

• Appears automated but is manual
• Users think it's working software
• Tests concept before building tech

Single-Feature MVP:

• One killer feature done well
• Solves one problem completely
• Add features based on feedback

Building an MVP

Step 1 - Define the Problem

• What problem are you solving?
• For whom?
• How much does it hurt?

Step 2 - Identify Core Value

• What's the ONE thing that must work?
• What's the minimum to deliver value?
• Everything else can wait

Step 3 - Build Only That

• Cut features ruthlessly
• Launch date is fixed, scope is not
• Quality over quantity

Step 4 - Launch to Small Group

• Early adopters
• Forgiving users
• Will give feedback

Step 5 - Learn and Iterate

• What works?
• What doesn't?
• What do users actually need?

MVP + Card Sorting

Use card sorting for MVP IA:

Problem: Don't know how to organize features

Solution:

1. List all possible features (even for version 2+)
2. Card sort with potential users
3. Identify most intuitive structure
4. Build MVP with simplest navigation that works

Result: Even basic product has good UX

Example:

• Card sort reveals users expect "Dashboard" not "Home"
• Build MVP with correct terminology from day 1
• Avoid rebranding later

Famous MVP Examples

Airbnb:

• Simple website
• Founders' apartment as listing
• Manual payment handling
• Learned what travelers needed

Zappos:

• Founder bought shoes from stores when customers ordered
• No inventory initially
• Validated demand before scaling

Instagram:

• Originally "Burbn" (location check-ins)
• Users only cared about photos
• Stripped to just photo sharing
• Became billion-dollar company

Buffer:

• Landing page describing product
• Two pricing plans
• Before writing any code
• Validated people would pay

Common MVP Mistakes

❌ Too many features: Defeats the purpose ❌ Taking too long: Should launch in weeks, not years ❌ Ignoring feedback: Learn from users! ❌ Poor quality: Minimum ≠ terrible ❌ No metrics: How will you know it works? ❌ Building in isolation: Talk to users throughout

What to Include in MVP

✅ Must-Haves:

• Core value proposition (the one thing)
• Basic usability
• Way to collect feedback
• Simple but functional design
• Essential user flows only

❌ Not in MVP:

• Nice-to-have features
• Advanced functionality
• Perfect polish
• Complex integrations
• Scale for millions

Testing Your MVP

Metrics to track:

• Sign-ups or activations
• Engagement (daily active users)
• Feature usage
• Retention rate
• User feedback scores
• Time to value

Qualitative:

• User interviews
• Support tickets
• Feature requests
• Drop-off points

After the MVP

If it works:

1. Double down on what users love
2. Fix biggest pain points
3. Add features users request most
4. Scale infrastructure
5. Improve design

If it doesn't:

• Pivot: Change direction based on learnings
• Persevere: Keep refining
• Kill it: Fail fast, move to next idea

MVP Mindset

Think "What's the quickest way to test this assumption?"

Not: "Let's build the perfect product" Instead: "What's the smallest thing we can build to learn?"

Embrace imperfection in service of learning.

From MVP to Product

MVP (Week 1-12):

• Core feature only
• Manual processes OK
• Basic design
• Small user group

V1.0 (Month 3-6):

• Polish based on feedback
• Automate manual processes
• Add requested features
• Improve design
• Expand user base

V2.0+ (Month 6+):

• Advanced features
• Integrations
• Scale infrastructure
• Professional design
• Mass market

Start with great IA for your MVP using card sorting at freecardsort.com