The Complete Guide to Minimum Viable Products (MVPs)

Many innovations fail not because they are poorly executed, but because they solve problems that people do not care about. Organisations invest significant time, money and effort developing products, services and technologies, only to discover that customers are unwilling to adopt them or that the value proposition was never compelling in the first place.

Minimum Viable Products (MVPs) were developed as a response to this challenge.

Rather than spending months or years building a complete solution, innovators create the smallest possible version capable of generating meaningful learning. The objective is not to launch a perfect product. The objective is to reduce uncertainty by gathering evidence.

An MVP sits at the intersection of design thinking, entrepreneurship, innovation and experimentation. It helps teams move from assumptions to evidence and from speculation to informed decision-making.

In the Expand stage of the 5E Design Thinking Framework, MVPs provide a practical way to transform ideas into testable experiments that reveal what should happen next.

A Minimum Viable Product is the simplest version of a product, service or solution that enables meaningful learning to occur.

The emphasis should be placed on all three words:

Minimum

Only the essential elements are included.

Viable

The experience must still provide enough value or realism to generate useful feedback.

Product

The representation may be a product, service, experience, platform, learning activity or business model.

An MVP is not necessarily a product ready for market.

An MVP is an experiment designed to answer important questions.

Innovation involves uncertainty.

Teams make assumptions about:

• Customer needs
• User behaviours
• Market demand
• Technical feasibility
• Business viability
• Adoption patterns
• Pricing structures

Without testing these assumptions, decisions are often based on opinion rather than evidence.

MVPs create opportunities to learn before making large investments.

They help innovators answer questions such as:

• Do people want this?
• Will they pay for it?
• Can they use it?
• Does it create value?
• Should further investment occur?

The MVP concept gained widespread attention through Lean Startup thinking, particularly the work of Eric Ries.

The central idea is simple:

Rather than attempting to predict customer behaviour, create something small, observe what happens and learn from the results.

This philosophy aligns closely with design thinking and human-centred innovation.

Both approaches encourage experimentation, feedback and continuous learning.

Design thinking focuses on understanding people, exploring possibilities and improving solutions through iteration.

MVPs support this process by making ideas tangible and testable.

Within the 5E Framework:

Engage

Understand needs and challenges.

Evaluate

Identify opportunities and define meaningful problems.

Explore

Generate ideas and possibilities.

Expand

Test ideas through MVPs, experiments and feedback.

Execute

Implement validated solutions.

MVPs create the bridge between creativity and implementation.

Many people use these terms interchangeably, but they serve different purposes.

Prototype

A prototype helps answer:

How might this work?

Prototypes often explore usability, interaction and design.

Examples:

• Sketches
• Wireframes
• Storyboards
• Mock-ups

A prototype may never be seen by real customers.

MVP

An MVP helps answer:

Does this create value?

MVPs are often tested with real users.

Examples:

• Landing pages
• Service trials
• Pilot programs
• Concierge experiences

A prototype explores possibilities.

An MVP explores viability.

A Proof of Concept (PoC) tests whether something can be built.

Questions include:

• Is the technology feasible?
• Can the system function?
• Does the approach work technically?

A Proof of Concept focuses on technical feasibility.

An MVP focuses on user value and learning.

A pilot is typically larger and more developed than an MVP.

An MVP asks:

Should we continue?

A pilot asks:

How should we implement?

MVPs occur earlier in the process.

Myth 1: MVP Means Poor Quality

An MVP should be simple, not careless.

Participants must experience enough value to generate meaningful learning.

Myth 2: MVP Means Building Less

The goal is learning less expensively, not merely building fewer features.

Myth 3: MVPs Are Only for Startups

MVPs can be applied to:

• Education
• Healthcare
• Government
• Services
• Non-profit organisations
• Community initiatives

Any idea can be tested.

Myth 4: MVPs Are Finished Products

An MVP is an experiment.

Learning should continue after testing.

Myth 5: Success Means Positive Feedback

A successful MVP generates learning.

Even negative findings can be extremely valuable.

Different questions require different MVP approaches.

Concierge MVP

In a Concierge MVP, people manually deliver the experience behind the scenes.

Customers believe they are engaging with a solution while humans perform much of the work.

Purpose

Test demand without building expensive systems.

Example

A career coaching platform manually matching mentors and learners before developing software.

Learning Question

Will people use the service?

Wizard of Oz MVP

Users interact with what appears to be a complete system.

Behind the scenes, humans perform functions that would eventually be automated.

Purpose

Test user behaviour.

Learning Question

Will people engage with this experience?

Example

An AI assistant manually responding to requests.

Landing Page MVP

A simple website presents a value proposition and measures interest.

Actions may include:

• Sign-ups
• Enquiries
• Pre-orders
• Downloads

Purpose

Test demand.

Learning Question

Do people care enough to act?

Video MVP

A video demonstrates how a future product or service may work.

Purpose

Evaluate interest before development.

Example

Dropbox famously demonstrated the concept through video before building the full product.

Learning Question

Does the concept resonate?

Crowdfunding MVP

A campaign presents the idea and asks people to support it financially.

Purpose

Evaluate both interest and willingness to pay.

Learning Question

Will people invest?

Pre-Order MVP

Potential customers commit to a purchase before production begins.

Purpose

Validate actual demand.

Learning Question

Are people willing to buy?

Single Feature MVP

Rather than developing an entire solution, teams focus on one critical feature.

Purpose

Test core value.

Learning Question

Is this feature genuinely useful?

Service MVP

A simplified version of a service experience is delivered manually.

Purpose

Explore user needs and operational requirements.

Learning Question

Does the service solve the intended problem?

Effective MVPs begin with questions.

Step 1: Identify a Critical Assumption

Examples:

• Students want personalised learning support.
• Small businesses need automated reporting.
• Consumers are willing to pay for convenience.

Not all assumptions are equally important.

Focus on the assumptions most likely to influence success.

Step 2: Define Learning Objectives

Ask:

What specifically must be learned?

Examples:

• Will people use it?
• Will people pay for it?
• Does it solve a problem?
• Which features matter most?

Step 3: Select an MVP Type

Choose the simplest approach capable of generating useful evidence.

Avoid unnecessary complexity.

Step 4: Define Success Metrics

Determine how learning will be measured.

Metrics may include:

• Sign-ups
• Conversion rates
• Purchases
• Retention
• Engagement
• Satisfaction

Step 5: Test with Real People

Learning requires interaction with potential users.

The objective is evidence, not validation.

Many teams focus exclusively on growth metrics.

Effective MVPs focus on learning metrics.

Examples include:

Behaviour Metrics

• Clicks
• Registrations
• Purchases
• Referrals

Engagement Metrics

• Time spent
• Repeat use
• Completion rates

Experience Metrics

• Satisfaction
• Usability
• Perceived value

Qualitative Insights

• Interviews
• Observations
• User comments

Multiple forms of evidence create stronger learning.

Not all metrics are useful.

Focus on metrics linked to behaviour.

Strong Metrics

• Purchases
• Registrations
• Retention
• Recommendations

Weaker Metrics

• Likes
• Views
• Impressions

Behaviour often reveals more than opinions.

Building Too Much

Complexity slows learning.

Testing Too Many Things

Focus on one important question.

Ignoring Negative Evidence

Learning is valuable regardless of outcome.

Measuring Vanity Metrics

Views do not necessarily indicate value.

Waiting for Perfection

An MVP exists to reduce uncertainty.

Testing should occur as soon as meaningful learning becomes possible.

Airbnb

Airbnb's founders initially rented air mattresses in their apartment to test whether travellers would pay for short-term accommodation.

Lesson

Simple experiments can validate demand.

Dropbox

Dropbox used a demonstration video to gauge interest before building the complete platform.

Lesson

Sometimes a video is enough to test a concept.

Zappos

The founder photographed shoes from local stores and only purchased inventory after customers ordered.

Lesson

Demand can be validated before investing in infrastructure.

Buffer

A simple landing page tested interest before software development began.

Lesson

Market demand can be explored through lightweight experiments.

Spotify

Numerous experiments, prototypes and staged releases helped refine user experiences over time.

Lesson

Continuous experimentation supports long-term innovation.

An MVP Canvas helps structure experimentation.

Problem

What challenge is being addressed?

Audience

Who is affected?

Assumption

What must be true?

Learning Objective

What needs to be learned?

MVP Approach

How will learning occur?

Success Metrics

How will outcomes be measured?

Next Steps

What decisions will be informed?

• What assumptions underpin your current idea?
• Which assumption is most risky?
• What is the smallest experiment capable of generating learning?
• How will success be measured?
• What evidence would increase confidence?

MVPs are not shortcuts.

They are learning tools.

The purpose of an MVP is not to launch a product.

The purpose of an MVP is to reduce uncertainty through evidence.

The most effective MVPs:

• Focus on critical assumptions
• Generate meaningful learning
• Minimise unnecessary investment
• Involve real users
• Inform future decisions

The best innovators do not try to predict the future.

They design experiments that help them learn from it.