What Features Should Go In an MVP?

Building a Minimum Viable Product (MVP) is a delicate balancing act. Include too few features, and your product won't solve the customer's problem. Include too many, and you'll waste resources and delay getting valuable feedback. This guide helps you identify exactly which features belong in your MVP.

Understanding the "Minimum" in MVP

The purpose of an MVP is to test your core business hypothesis with the least amount of effort. This means including only features that directly contribute to validating whether your product solves a real problem that customers are willing to pay for.

A true MVP isn't about launching a half-baked product—it's about strategic focus. The features you include should represent the smallest possible set that delivers real value and enables meaningful learning.

3 Types of Features to Include in Your MVP

1. Problem-Solving Features

These directly address the core problem your product aims to solve. They form the foundation of your value proposition and are non-negotiable for the MVP.

2. Must-Have Infrastructure Features

These are features that enable the core functionality to work properly. While they might not directly solve the user's problem, the product cannot function without them.

3. Differentiation Features (Limited)

Include a small number of features that differentiate your product from alternatives. Be extremely selective here—only include differentiators that are essential to your value proposition.

Features to Exclude from Your MVP

The MVP Feature Selection Framework

Use this practical framework to determine which features should make the cut for your MVP:

Step 1: Identify All Potential Features

Start by listing all possible features you could include in your product. Don't filter at this stage—capture everything from essential functionality to nice-to-have enhancements.

Step 2: Categorize by Feature Type

Classify each feature into one of these categories:

• Core: Directly solves the main user problem
• Infrastructure: Necessary for the product to function
• Differentiator: Sets your product apart from alternatives
• Enhancement: Improves the experience but isn't essential
• Future: Valuable only after achieving initial traction

Step 3: Score Features on Impact vs. Effort

For each feature, assign a score (1-10) for:

• Impact: How much this feature contributes to solving the core problem
• Effort: How much time and resources it will take to implement

Calculate an "MVP Value" by dividing Impact by Effort. Higher scores indicate better candidates for your MVP.

Step 4: Apply the MVP Criteria Filter

For each feature, ask these critical questions:

Features that pass most of these tests and have high MVP Values should be included in your MVP.

Real-World MVP Examples

Learning from successful MVPs can help you make better decisions about your own feature set:

Dropbox

Instead of building the entire product, Dropbox's MVP was a simple video demonstration showing how the product would work. This validated interest without building the complex technical infrastructure.

Airbnb

The initial version of Airbnb was simply a website offering air mattresses in the founders' apartment during a design conference when hotels were sold out.

Common MVP Feature Selection Mistakes

Conclusion: Your MVP Feature Roadmap

Selecting the right features for your MVP is about strategic focus, not compromising on quality. The best MVPs solve a specific problem well rather than multiple problems inadequately.

Remember that your MVP is just the beginning. Plan your post-MVP feature roadmap based on what you learn from real users, not on your initial assumptions. The features you thought were essential might turn out to be less important than ones you hadn't considered.

Use the frameworks in this guide to make data-driven decisions about what to include in your MVP, and you'll be well on your way to building a product that resonates with customers while minimizing wasted effort.