What is an MVP, and how does it prevent misplaced spending?
An MVP, or minimum viable product, is the smallest version that delivers the product's core value in a usable form and lets you test an important assumption through real user behavior. The goal isn't a cheap, unfinished product; it's learning before developing a wide range of features.
1. The core MVP question
An MVP needs a clear hypothesis: will users sign up, submit a request, pay, or return to solve their problem? “Let's see if they like it” isn't a sufficient metric.
- —Defined user group
- —A real problem
- —Observable behavior
- —Metrics defined before launch
- —Evaluation period
- —Decision based on results
2. Understanding the terms
Prototype
Used to explore flows and interfaces; it may not contain operational code.
Proof of concept
Tests technical or integration feasibility, not necessarily product value.
MVP
A usable version that tests core value and real behavior.
Beta
Usually a more extensive product released to gather bug reports and feedback.
3. Defining scope
Write down the main journey:
- How does the user arrive?
- What information do they need?
- What is the main action?
- What result do they receive?
- What does the internal team do?
- What gets recorded?
Feature categories
- Essential to the core value
- Essential for security or operations
- Useful, but can wait
- Dependent on test results
- Outside the first version
Scope can be narrow, but the main journey must be complete and usable.
4. What can wait
Depending on the project:
- —Extensive personalization
- —Secondary reports
- —Automating every exception
- —Multiple languages
- —Rarely used roles
- —Nonessential integrations
- —Social features
- —A second platform
Every feature needs a reason to be in the first version.
5. Success criteria
Define these before building:
- —How many target users?
- —Which behavior will be recorded?
- —How important is the completion rate?
- —Where do users abandon the journey?
- —What feedback will be collected?
- —Which errors or costs are unacceptable?
- —What decision follows a positive or negative result?
6. After launch
Launch is the start of measurement. Behavioral data, user conversations, errors, and operating costs are reviewed together.
- —Continue and expand
- —Refine and test again
- —Stop or change direction
Stopping an unsuccessful hypothesis is a useful outcome too: it prevents a larger expense.
7. Common mistakes
- —Confusing an MVP with a poor-quality product
- —Adding a feature for every comment
- —Measuring vanity metrics
- —Building massive infrastructure for a hypothetical future
- —Ignoring internal operations
- —Having no clear decision after testing
Build the first version around one core value and measurable behavior. A narrow scope is acceptable; a broken core experience, inadequate security, or an unusable product is not.
Website and web platform design and development
From presenting your services to selling online, we build websites your customers can use easily and your team can manage.