The MVP Lie: Prioritizing Desirability Over Feasibility in Early-Stage Product Design
Here's a conversation I've heard in every startup:
Engineer: "We can ship the MVP in 6 weeks. It'll have user accounts, a dashboard, basic CRUD operations, and—"
Designer: "Wait. What problem does this actually solve?"
PM: "All the core functionality. Users can create, read, update, and delete items."
Designer: "But will users want to? What makes this better than their current solution?"
Engineer: "It's not about 'better.' It's about getting something out fast, learning from users, and iterating."
Designer: "But if users don't want it, there's nothing to iterate from. They'll just leave."
PM: "That's why it's called a minimum viable product. We'll make it better later."
Six months later:
- 500 sign-ups
- 8% activation rate (only 40 users actually used the product)
- 95% churn within first week
- 0 paying customers
- Burned $200K in engineering and marketing
What went wrong?
The team shipped a Minimum Viable Product. It was technically functional. It worked. Users could create accounts, log in, and use features.
But nobody wanted to. Because the product was viable (it worked), but not desirable (nobody cared).
This is the MVP lie: the belief that if you ship something fast and cheap, users will forgive the lack of polish and stick around for the "vision."
They won't.
The Feasibility Trap
The problem with the traditional MVP approach is that it prioritizes feasibility (Can we build it?) and viability (Can we profit from it?) while treating desirability (Will people want it?) as an afterthought.
Here's the traditional MVP thinking:
- Feasibility First: What's the fastest, cheapest thing we can build?
- Viability Second: Can we monetize this?
- Desirability Last: We'll add polish later, once we validate demand.
This is backwards.
Because here's what actually happens:
The Undesirable MVP Cycle
Week 1-6: Build the MVP
- Focus on getting features working
- Skip design polish ("we'll improve it later")
- Ignore edge cases ("we'll fix bugs after launch")
- Cut UX research ("we don't have time")
Week 7: Launch
- Announce to mailing list, social media, Product Hunt
- Get initial traffic spike
- Users sign up
Week 8-12: Reality Hits
- 90%+ of users never activate (don't complete onboarding)
- Of those who do, 80% churn within a week
- Reviews are mixed: "Seems promising, but..." / "Not ready yet" / "Too buggy"
- Team scrambles to fix top bugs
Month 4-6: The Death Spiral
- Early momentum is gone
- Word-of-mouth is negative ("I tried it, it's not ready")
- Team is stuck fixing technical debt instead of building new features
- Harder to raise next round ("Your activation rate is 8%")
The Problem:
You shipped a product that was viable (it worked), but not desirable (nobody wanted it enough to stick around).
And now you're in a worse position than if you'd waited to ship something people actually loved.
The Cost of an Undesirable MVP
Let's be clear: shipping an undesirable product is worse than shipping nothing.
Here's why:
1. First Impressions are Permanent
When users try your product and have a bad experience, they:
- Won't come back (even if you improve it)
- Won't recommend it to others
- Remember the bad experience and warn others
Example:
A project management tool launched an MVP with a clunky UI, slow load times, and confusing navigation. They got 1,000 beta users.
Six months later, they redesigned everything. The product was now beautiful, fast, and intuitive.
They emailed the original 1,000 users: "We've completely rebuilt the product! Come check it out."
Reactivation rate: 3%.
Why? Because those users remembered the first experience. Their mental model was: "This product is janky and confusing."
Even though the product was now objectively better, the perception was set.
2. Negative Word-of-Mouth Spreads Faster
When users try your MVP and it disappoints, they tell people.
Example:
Early Twitter users loved the simplicity. They told friends: "You have to try this."
Early Google Wave users were confused. They told friends: "I don't get the point."
Twitter grew through word-of-mouth. Google Wave died despite massive hype.
The difference? Twitter was desirable. Google Wave was viable (it worked) but not desirable (users didn't understand why they needed it).
3. You Lose Your Launch Window
You only get one launch. If you blow it on an undesirable MVP, you don't get another chance.
Example:
You launch on Product Hunt with an unfinished MVP. You get 500 upvotes, 2,000 sign-ups... and 90% churn.
Six months later, you've rebuilt the product. You want to launch again on Product Hunt.
But you can't. You already launched. And now the product has a reputation: "That thing that launched too early."
You wasted your launch.
The MDP Framework: Minimum Desirable Product
Here's the shift:
Stop asking: "What's the minimum we can ship?"
Start asking: "What's the minimum we need to ship to make users fall in love?"
That's the Minimum Desirable Product (MDP).
The MDP framework has three components:
Step 1: Define the Core Value
The Rule:
Identify the one thing the user cannot live without. Everything else is optional.
How to find it:
Ask: "If we could only ship one feature, what would it be?"
Not "What's the most important feature?" (that leads to feature lists).
But: "What is the single capability that solves the user's problem?"
Example: Dropbox
Core Value: "My files are accessible from any device, automatically."
Not:
- File sharing
- Version history
- Team folders
- File recovery
Those came later. The core value was: seamless file sync.
Why it worked:
Users didn't need to think about Dropbox. It just worked. That was desirable.
Example: Superhuman (Email Client)
Core Value: "I can get to inbox zero in half the time."
Not:
- Calendar integration
- Contact management
- Advanced search
- Team collaboration
Those came later. The core value was: speed.
Why it worked:
Users felt productive. That emotional payoff (getting through email faster) made them stick around.
Step 2: Define the Core Emotion
The Rule:
Identify the emotion the user must feel when using the product.
Why it matters:
Users don't remember features. They remember how a product made them feel.
Common Core Emotions:
| Emotion | Product Example | How It's Delivered |
|---|
| Trust | Stripe | Clear error messages, reliable uptime, transparent pricing |
| Delight | Slack | Fun emojis, smooth animations, personality in microcopy |
| Control | Notion | Infinite customization, powerful but not overwhelming |
| Calm | Headspace | Minimalist design, soothing colors, gentle guidance |
| Speed | Superhuman | Keyboard shortcuts, instant load times, no friction |
| Confidence | Figma | Real-time collaboration, no data loss, auto-save |
How to choose the Core Emotion:
Ask: "When a user finishes using this product, what should they feel?"
Example: Notion
Core Emotion: Control
Notion's entire design is built around giving users control:
- Drag and drop anything anywhere
- Customize every view (table, board, calendar, gallery)
- Build your own workflow
Users feel like they're in charge. That's the emotion. That's what makes it desirable.
Example: Calm (Meditation App)
Core Emotion: Calm (obviously)
Every design decision reinforces this:
- Soft, muted colors (no bright reds or yellows)
- Slow, gentle animations
- Minimal UI (no clutter)
- Soothing audio cues
Users feel calm before they even start meditating. That's the desirability.
Step 3: Feature Scaffolding
The Rule:
Build only the features needed to deliver the Core Value and Core Emotion. Everything else is debt.
How to prioritize:
For every feature, ask:
- Does this directly support the Core Value?
- Does this reinforce the Core Emotion?
If the answer to both is "no," cut it.
Example: Superhuman (Email Client)
Core Value: Inbox zero in half the time
Core Emotion: Speed
Features that made it into the MDP:
✅ Keyboard shortcuts (supports Core Value: speed)
✅ Split inbox (supports Core Value: triage faster)
✅ Instant load times (reinforces Core Emotion: speed)
✅ Snooze emails (supports Core Value: defer decisions)
Features that were cut from MDP:
❌ Calendar integration (nice to have, not core)
❌ Team shared inboxes (different user segment)
❌ Advanced filters (power user feature, not essential)
❌ Email templates (writing aid, not core to speed)
Result:
Superhuman shipped with fewer features than Gmail. But the features they shipped were perfectly aligned with the Core Value and Core Emotion.
Users loved it. Waitlist grew to 180,000+. NPS score: 60+ (world-class).
Why? Because it was desirable, not just viable.
Collaboration Case Study: 3 Polished Features Beat 8 Simple Features
Let me show you a real example where prioritizing desirability over feasibility paid off.
The Scenario
Product: SaaS tool for managing customer support tickets
Timeline: 8 weeks to MVP
Team:
- 2 engineers
- 1 designer
- 1 PM
The Debate
Engineering's Proposal: 8 Simple Features
"We can ship 8 features in 8 weeks if we keep them simple:
- Create ticket
- Assign ticket
- Reply to ticket
- Close ticket
- Search tickets
- Filter by status
- User dashboard
- Admin settings
Each feature is basic, but functional. We'll polish them later."
Design's Counter-Proposal: 3 Polished Features
"We should ship 3 features, but make them excellent:
- Smart ticket triage (AI-powered auto-categorization and priority scoring)
- Unified inbox (email, chat, and social media tickets in one view)
- Instant reply templates (context-aware suggested responses)
These three solve the core pain: support teams spend too much time triaging and routing tickets. If we nail these, we don't need the other 5 features yet."
The Tension
PM: "But with only 3 features, we won't have feature parity with competitors."
Designer: "We're not trying to match competitors. We're trying to be 10x better at the thing that matters most: reducing triage time."
Engineer: "But building AI-powered triage is way harder than basic CRUD. It'll take the entire 8 weeks."
Designer: "Exactly. And it'll be desirable. Users will see the value immediately."
The Decision
The team chose the 3 polished features.
The Result (After 3 Months)
| Metric | Predicted (8 Features) | Actual (3 Features) |
|---|
| Sign-ups | 800 | 1,200 |
| Activation rate | 25% | 47% |
| Week 1 retention | 18% | 61% |
| NPS | +15 | +52 |
| Word-of-mouth growth | 10% of new users | 38% of new users |
Why the 3-feature MDP won:
- Immediate Value: Users saw results in the first session (AI triage saved them 40% of their time)
- Emotional Payoff: Users felt relief ("Finally, I'm not drowning in tickets")
- Word-of-Mouth: Users told colleagues: "You have to try this—it's like magic"
Key Insight:
Users didn't care that the product was "missing" features like admin settings or advanced filters. They cared that it solved their biggest pain point better than anything else.
That's desirability.
Metrics: How to Measure Desirability
Traditional MVP metrics focus on vanity numbers:
- Sign-ups
- Feature usage
- Page views
MDP metrics focus on engagement and love:
1. Activation Rate
Definition: % of users who complete the core action in their first session
Why it matters: If users don't "get it" immediately, they won't stick around.
Target: 40%+ (anything below 25% means your product isn't desirable enough)
2. Week 1 Retention
Definition: % of users who return within 7 days of signing up
Why it matters: This is the strongest signal of desirability. If users come back, they found value.
Target: 30%+ for B2C, 50%+ for B2B
3. Time to Value (TTV)
Definition: How long it takes a user to experience the Core Value
Why it matters: The faster users feel the benefit, the more likely they are to stick around.
Target: <5 minutes for consumer, <30 minutes for enterprise
Definition: "How likely are you to recommend this product to a friend or colleague?"
Why it matters: Word-of-mouth is the ultimate signal of desirability.
Target: +40 is good, +50 is excellent, +60+ is world-class
5. Organic Growth Rate
Definition: % of new users who came from referrals or word-of-mouth (not paid marketing)
Why it matters: If users love your product, they'll tell others.
Target: 20%+ of new users should be organic
Common Objections (and Rebuttals)
Objection 1: "We Don't Have Time to Make It Desirable"
The Myth:
"Desirability is a luxury. We need to ship fast and learn."
The Reality:
You don't have time not to make it desirable.
If you ship an undesirable product:
- Users churn immediately (you learn nothing)
- You get negative reviews (harder to acquire new users)
- You spend months fixing perception instead of building features
Better approach:
Ship 3 features users love instead of 8 features users tolerate.
Objection 2: "We'll Add Polish Later"
The Myth:
"Ship the basic version now. We'll improve it based on feedback."
The Reality:
"Later" never comes. You'll be stuck fixing bugs, onboarding new users, and fighting churn.
Example:
A startup shipped a basic MVP with plans to "polish it later."
6 months later:
- 40% of engineering time spent fixing bugs
- 30% spent on feature requests from early users
- 20% spent on infrastructure scaling
- 10% left for "polish"
The polish never happened.
Better approach:
Ship fewer features, polished from day one.
Objection 3: "Users Said They Want Features X, Y, Z"
The Myth:
"We asked users what they want, and they said they need these 12 features."
The Reality:
Users are terrible at articulating what they want. They describe solutions, not problems.
Example:
If you'd asked people in 1999 what they wanted, they'd say: "Faster email, better search, more storage."
Nobody would have said: "An infinite scrolling feed of my friends' updates."
But that's what Facebook built. And it was massively desirable.
Better approach:
Focus on the problem, not the feature list.
Ask: "What's frustrating about your current solution?" Not: "What features do you want?"
How to Convince Your Team to Build an MDP
If you're a designer trying to shift your team from MVP to MDP, here's how to make the case:
1. Reframe "Minimum" as "Focused," Not "Cheap"
Don't say: "Let's cut features to save time."
Do say: "Let's focus on the one thing that will make users fall in love."
2. Show the ROI of Desirability
Don't say: "This will take longer but feel better."
Do say: "Here's how Superhuman's focus on desirability led to a 180,000-person waitlist and $33M Series B."
3. Use Data to Justify Cuts
Don't say: "I think we should cut Feature X."
Do say: "Based on user interviews, Feature X solves a low-priority problem. Feature Y solves the #1 pain point. If we cut X, we can make Y excellent."
4. Propose a Test
Don't say: "We should ship 3 polished features instead of 8 basic ones."
Do say: "Let's test both approaches with a prototype. We'll show 20 users Version A (8 features) and 20 users Version B (3 polished features) and measure which gets higher activation and retention."
Conclusion: Viability Comes from Desire
Here's the fundamental truth:
The viability of a product doesn't come from its technical completeness. It comes from the human desire to use it.
A product can be:
- Technically perfect
- Feature-complete
- Bug-free
- Well-documented
...and still fail. Because nobody wants it.
The shift from MVP to MDP is simple:
MVP: What's the minimum we can ship to test viability?
MDP: What's the minimum we can ship to make users fall in love?
The MDP framework:
- Core Value: The one thing users can't live without
- Core Emotion: The feeling users must experience
- Feature Scaffolding: Only build features that support #1 and #2
The result:
- Higher activation rates (users "get it" immediately)
- Higher retention (users come back)
- Organic growth (users tell others)
- Faster path to product-market fit
Ship a desirable experience, even if it's smaller.
Because 3 features users love will always beat 8 features users tolerate.
Want to learn more about product strategy and user-centered design?
What's your experience with MVPs? Have you shipped something too early and regretted it? Or waited and shipped something users loved?
