A minimum viable product, or MVP, is the smallest version of your product that lets you learn whether you are solving a real problem for real people. Too often, MVPs become either a rushed prototype that proves nothing or a bloated first version that takes a year to ship. Here is the framework we use to find the right balance.
Step 1: Write down your riskiest assumptions
Every product idea rests on assumptions. List them, then rank them by how much damage it would do if they were wrong. Typical examples:
- Customers experience this problem often enough to care.
- They will trust a new provider with this task.
- They will pay, or businesses will pay on their behalf.
- We can reach them at a reasonable cost.
Your MVP exists to test the top two or three assumptions on this list. Anything that does not help test them can wait.
Step 2: Define what success looks like
Before building anything, agree on measurable signals. For example: “Within six weeks of launch, 40 percent of users who sign up complete their first transaction.” Clear targets turn opinions into decisions when the results arrive.
Step 3: Map the core journey
Identify the single most important journey a user takes, from discovering your product to getting value from it. Design that journey end to end and make it excellent. Secondary journeys such as detailed settings, advanced reporting and integrations belong in later releases.
Step 4: Cut scope ruthlessly, not quality
“Minimum” refers to scope, not to quality. A small product that is reliable, fast and pleasant to use teaches you far more than a large product full of bugs, because users judge the idea through the experience. We typically:
- Keep features to the core journey;
- Use proven services for authentication, payments and notifications instead of building them from scratch;
- Invest properly in onboarding, error handling and performance.
Step 5: Build in weeks, not months
With a focused scope, most MVPs can launch in eight to twelve weeks. We work in one- or two-week iterations with a working demo at the end of each, so stakeholders see progress and can adjust priorities quickly.
Step 6: Instrument everything that matters
Set up privacy-respecting analytics for your success metrics before launch, along with crash reporting and a simple way for users to give feedback. Without data you are guessing, even after launch.
Step 7: Launch, learn and decide
After launch, review results against the success criteria you set in step 2. Then choose deliberately:
- Persevere if the signals are strong, and invest in the next most valuable features;
- Pivot if you learned something that changes the problem or the audience;
- Pause if the evidence says the idea is not viable, saving you from a much larger investment.
Common MVP mistakes to avoid
- Building for every possible user instead of one clear audience;
- Skipping user research because “we already know what they want”;
- Treating the MVP as throwaway code, then being stuck with it;
- Launching without a plan to reach the first users.
If you have an idea and want help turning it into a focused, testable MVP, our team would love to hear about it.