Building the wrong product remains one of the most expensive mistakes businesses make worldwide.
A minimum viable product helps founders and organisations test demand early, reduce uncertainty, and make smarter decisions before scaling.
This guide explains how to define, design, and build an MVP that solves real problems and supports sustainable growth across global markets.
Key Takeaways
- A minimum viable product is a practical way to test real demand early and reduce the risk of building the wrong solution.
- The success of an MVP depends on clear focus, minimal scope, real user behaviour, and measurable outcomes.
- Choosing the right MVP type and testing the right assumption leads to faster learning and better decisions.
- An MVP delivers value when it produces clear evidence to refine, scale, or stop a product idea.
What Is a Minimum Viable Product (MVP)?
A minimum viable product is the simplest version of a product you can release to real users to test whether there is genuine demand.
It is a practical approach to product development that prioritises learning quickly and reducing risk before you commit serious time and capital.
An MVP is built around one clear value proposition. It should solve a specific problem well enough for users to try it, use it, and give behaviour based feedback.
In other words, it is not about building less for the sake of it. It is about building only what is necessary to validate your assumptions.
The simplest way to define an MVP
If you want a one line definition that stays true in any industry, it is this: an MVP is the smallest product that can deliver value and test a key assumption with real users.
A key assumption could be one of the following:
- People will switch from their current solution to yours
- People will complete a key action inside the product
- People will pay for the outcome you promise
- A specific segment will adopt the product fast enough to justify building further
What a minimum viable product includes
A minimum viable product typically includes:
- A clearly defined target user
- One problem to solve and one primary outcome
- The minimum set of features needed to deliver that outcome
- A way to observe user behaviour and capture feedback
- A simple onboarding path that gets users to value quickly
To keep it concrete, here is how MVP scope usually looks in practice.
| MVP element | What it means in practice | Example |
|---|---|---|
| Target user | One specific audience, not everyone | First time landlords in the UK |
| Core problem | A single pain point | Tracking rental income and expenses |
| Value proposition | A clear promise | See your profit and tax position instantly |
| Minimal features | Only what supports the promise | Add income, add costs, auto totals |
| Feedback loop | Learn from real usage | Short survey after first use |
| Success signal | One measurable outcome | Users complete setup and return |
The term MVP is often linked to startups and apps, but it applies to almost any business model.
In the US, a service firm can test a new offer with a small group of clients. In the EU, a retail brand can validate a new product line through pre orders or limited releases. In the UK, a B2B company can run a small pilot with one industry segment.
The point is the same: a minimum viable product is a disciplined way to test demand and reduce uncertainty before scaling.
See also: Minimum Viable Brand: Proven Guide to Build an MVB Fast – 7 Day Framework
Key Aspects of a Minimum Viable Product
A minimum viable product succeeds or fails based on a small set of defining characteristics. These aspects determine whether an MVP produces reliable learning or simply adds noise to the product development process.
Focus on a single, meaningful problem
Every minimum viable product must be anchored to one clearly defined problem. The goal is not to address multiple pain points but to validate whether a specific issue is important enough for users to act.
Products that attempt to solve several problems at once often struggle to generate clear signals. A focused MVP makes it easier to understand why users engage or disengage, which is essential for accurate market validation.
Clear value proposition from the first interaction
A minimum viable product must communicate its value immediately. Users should understand what the product does and why it matters within their first interaction.
This is particularly important in global markets where attention is limited and alternatives are abundant.
Research referenced by international economic bodies such as the OECD consistently shows that products with a clear and immediate value proposition experience higher early adoption rates.
Minimal functionality with purposeful design
A minimum viable product includes only the features required to deliver its core value. Each feature must support a specific learning goal.
This does not mean the product should feel broken or unfinished. Instead, it should feel intentional. A well designed MVP appears simple, not incomplete, and guides users directly to the action that matters most.
Real users and real usage data
A minimum viable product only works when it is used by real people in real conditions. Feedback based on opinions alone is unreliable. Behaviour is the most accurate signal.
Key aspects of this include:
- Observing how users interact with the product
- Tracking completion of core actions
- Identifying friction points in the experience
Global studies from organisations such as the World Bank highlight that early behavioural data is a stronger predictor of long term adoption than stated interest or surveys alone.
Fast feedback and short learning cycles
Speed is a defining aspect of a minimum viable product. The faster feedback is collected, the faster decisions can be made.
An effective MVP supports rapid iteration, allowing teams to adjust features, messaging, or positioning without significant rework.
This is especially valuable in markets like the US and EU, where competitive pressure and customer expectations evolve quickly.
Measurable outcomes tied to decisions
Every MVP should be built with specific success signals in mind. These signals are used to decide whether to continue, adjust, or stop.
The table below shows how key aspects translate into measurable signals.
| MVP aspect | What to observe | Why it matters |
|---|---|---|
| Problem focus | Users complete the core task | Confirms problem relevance |
| Value clarity | Time to first meaningful action | Indicates understanding |
| Feature scope | Usage concentrated on core feature | Validates prioritisation |
| User behaviour | Repeat use or return visits | Signals early traction |
| Feedback speed | Time from launch to insight | Enables faster decisions |
Key Benefits of a Minimum Viable Product
The value of a minimum viable product lies in what it enables businesses to avoid as much as what it helps them achieve.
When used correctly, a minimum viable product creates economic, strategic, and operational advantages that apply across industries and regions.
Reduced cost and financial risk
One of the most immediate benefits of a minimum viable product is cost control. By limiting development to essential functionality, businesses avoid large upfront investments before demand is proven.
This matters globally. Data consistently shows that capital constraints are one of the leading causes of early business failure, particularly for small and growing firms.
Faster time to market
A minimum viable product shortens the gap between idea and market exposure. Instead of waiting for a fully developed solution, businesses can launch earlier and begin learning from real users.
In competitive markets, speed often determines who captures attention first. According to OECD research on innovation driven growth, firms that validate concepts early are better positioned to adapt and scale ahead of slower competitors.
Stronger product market fit
A minimum viable product improves the chances of building something people actually want. By observing real behaviour, teams can refine the product based on evidence rather than assumptions.
This benefit is particularly relevant in international markets where customer needs vary by region. Early validation helps businesses avoid scaling products that resonate in one market but fail in another.
Better decision making through data
Minimum viable products support evidence based decisions. Instead of relying on opinions or internal debates, teams can use measurable outcomes to guide next steps.
This approach aligns with global best practices promoted by institutions such as the OECD and the UN, which emphasise data led innovation as a driver of sustainable business growth.
Efficient use of teams and resources
An MVP keeps teams focused. Designers, developers, and marketers work toward a single objective rather than spreading effort across multiple unproven features.
This clarity reduces wasted effort and improves alignment, especially in distributed teams. It also allows leadership to assess performance based on outcomes rather than activity.
Improved investor and stakeholder confidence
A tested minimum viable product provides tangible proof that an idea has traction. For startups seeking funding or internal teams pitching new initiatives, real usage data carries more weight than projections.
According to data referenced by the US Small Business Administration, businesses that validate demand early are more likely to secure follow on funding and long term support.
The table below summarises how these benefits translate into practical business outcomes.
| Benefit | Business impact | Why it matters |
|---|---|---|
| Lower upfront cost | Reduced financial exposure | Preserves capital |
| Faster launch | Earlier market feedback | Increases adaptability |
| Better fit | Higher adoption potential | Reduces failure risk |
| Data driven insights | Clear go or stop decisions | Improves outcomes |
| Resource efficiency | Focused execution | Saves time and effort |
| Stakeholder confidence | Stronger credibility | Supports growth |
Components of a Successful Minimum Viable Product
A minimum viable product only works when its core components are deliberately designed to support learning and decision making.
These components ensure the MVP is credible to users, measurable for teams, and useful for guiding what happens next.
A clearly defined target customer
Every successful minimum viable product is built for a specific group of users. This is not a broad market or demographic category but a clearly defined customer profile with a shared problem.
Businesses that skip this step often misread results. Global market studies show that early stage products with a tightly defined initial audience produce clearer adoption signals than those launched to wide, unfocused markets.
A single core value proposition
A minimum viable product must make one promise and deliver on it. This promise should be easy to understand and directly tied to the problem being tested.
If users cannot quickly explain why the product exists, the MVP is unlikely to generate reliable insights. Clarity at this stage improves engagement and helps distinguish genuine interest from casual curiosity.
Essential features only
A successful minimum viable product includes just enough functionality to support its value proposition. Every feature should have a clear reason for existing.
Features that do not contribute to learning dilute results and slow progress. In practice, this means resisting the urge to add enhancements that feel useful but do not test a key assumption.
A simple and reliable user journey
Even with minimal features, the user experience must be intentional. Users should be guided smoothly from first interaction to the point where value is delivered.
This is especially important in international markets where attention spans are short and alternatives are readily available.
Research across EU digital markets shows that early friction often leads to abandonment before meaningful data can be collected.
Measurement and feedback mechanisms
A minimum viable product must include a way to observe behaviour and capture feedback. Without measurement, there is no learning.
This typically includes:
- Tracking completion of the core action
- Monitoring repeat usage
- Capturing qualitative feedback at key moments
A decision framework
A successful MVP is built with a clear decision in mind. The product exists to answer a specific question, and the outcome should guide what happens next.
The table below shows how minimum viable product components support clear decision making.
| Component | Purpose | Outcome enabled |
|---|---|---|
| Target customer | Focus learning | Clear adoption signals |
| Value proposition | Define relevance | Meaningful engagement |
| Essential features | Limit scope | Faster iteration |
| User journey | Reduce friction | Accurate behaviour data |
| Measurement | Track outcomes | Evidence based insights |
| Decision framework | Guide next steps | Scale, refine, or stop |
Minimum Viable Product vs Prototype vs Proof of Concept
These three terms are often used interchangeably, but they serve very different purposes.
Understanding the distinction is essential for choosing the right approach at the right stage of product development and avoiding wasted effort.
What is a Prototype?
A prototype is an early visual or functional representation of a product. Its primary purpose is to explore design, usability, and user flow before anything is built for real use.
Prototypes are commonly used to:
- Test user experience and interface design
- Validate workflows and interactions
- Communicate ideas internally or to stakeholders
They are not intended for market validation. Users interacting with a prototype are reacting to a concept, not adopting a solution.
What is a Proof of Concept (PoC)?
A proof of concept is used to test feasibility. It answers the question of whether something can be built from a technical, operational, or regulatory standpoint.
A PoC is typically internal and focuses on:
- Technical viability
- Integration with existing systems
- Compliance or regulatory feasibility
In sectors such as fintech, health, and infrastructure, proof of concept exercises are often required before any market facing product is considered.
How a Minimum Viable Product differs
A Minimum Viable Product is fundamentally market facing. It is designed to test demand and behaviour, not just ideas or feasibility.
While prototypes and proofs of concept answer internal questions, a minimum viable product answers an external one: will users adopt this solution?
It is released to real users, used in real conditions, and measured using real data. This makes it the most reliable way to validate whether a product is worth scaling.
Side by side comparison
The table below highlights the practical differences.
| Aspect | Prototype | Proof of Concept | Minimum Viable Product |
|---|---|---|---|
| Primary goal | Test design and usability | Test feasibility | Test market demand |
| Audience | Designers and stakeholders | Internal teams | Real users |
| User interaction | Simulated | Limited or none | Real world usage |
| Data collected | Qualitative feedback | Technical results | Behavioural data |
| Business decision | Refine design | Proceed technically | Scale, iterate, or stop |
Choosing the right approach
The choice depends on the question you are trying to answer:
- Use a prototype when you need feedback on how something should work
- Use a proof of concept when feasibility is uncertain
- Use an MVP when you need evidence that customers will adopt and engage
Many successful businesses use all three at different stages, but problems arise when they are confused or used out of sequence. Selecting the right tool protects time, capital, and focus.
The 7 Types of Minimum Viable Product
Not every idea should be tested in the same way. Choosing the right minimum viable product type determines how quickly you learn, how reliable the data is, and how much effort is required.
Each type is designed to test a specific assumption, which is why selecting the right one matters.
Landing page MVP
A landing page MVP tests interest before a product exists. It presents a clear value proposition and invites users to take an action such as signing up, joining a waitlist, or requesting access.
This type is useful when the primary uncertainty is demand. High intent actions signal whether the problem resonates strongly enough to justify further development.
Concierge MVP
A concierge MVP delivers the value manually instead of through software or automation. Users receive the outcome promised, but the process behind the scenes is handled by people.
This approach is effective when the goal is to understand customer needs deeply before investing in systems. It is commonly used in services, B2B offerings, and early stage platforms where workflows are still unclear.
Wizard of Oz MVP
In this model, the product appears automated to users, but the core functionality is operated manually behind the scenes. From the user perspective, it feels complete.
This type helps test whether users care about the result, without the cost of building full infrastructure. It is especially useful when automation is complex or expensive.
Single feature MVP
A single feature MVP focuses on one capability and does it well. Everything else is removed.
This approach works best when one feature represents the main value of the product. It allows teams to measure engagement around that feature without distractions or secondary functionality.
Piecemeal MVP
A piecemeal MVP combines existing tools and services to deliver value without building new technology. The experience may not be seamless, but it serves the purpose of testing adoption.
This type is ideal when speed matters more than polish and when the goal is to validate behaviour rather than infrastructure.
Fake door MVP
A fake door MVP tests interest in a feature that does not yet exist. Users are presented with an option, button, or message, and their response is measured.
This method is useful for prioritisation. It helps teams understand what users want most before committing development effort.
Pre order or crowdfunding MVP
This type tests willingness to pay. Users are asked to commit financially before the product is built.
Pre orders and crowdfunding campaigns provide strong signals of demand and pricing sensitivity, making them valuable for physical products and capital intensive ideas.
The table below summarises what each type is best suited to test.
| MVP type | Primary assumption tested | Best used when |
|---|---|---|
| Landing page | Interest and demand | Idea stage validation |
| Concierge | Problem depth and workflow | Services and B2B |
| Wizard of Oz | Outcome value | Automation is costly |
| Single feature | Core usage | Feature led products |
| Piecemeal | Behaviour | Speed is critical |
| Fake door | Feature demand | Roadmap decisions |
| Pre order | Willingness to pay | Revenue validation |
How to Build a Minimum Viable Product – Step by Step
Building a minimum viable product is about applying structured thinking to reduce uncertainty and learn quickly.
The steps below follow a logical sequence that supports clarity, speed, and reliable decision making without unnecessary complexity.
Step 1: Define the problem worth solving
Every product begins with a problem, but not every problem is worth solving. Start by clearly stating the issue in practical terms, focusing on who experiences it, how often it occurs, and why existing solutions fall short.
At this stage, avoid jumping to solutions. The goal is to confirm that the problem is real, specific, and meaningful enough to justify attention.
Step 2: Identify the target user
A minimum viable product must be built for a clearly defined user group. This is not a broad audience but a specific segment that shares the same problem and context.
Clarity here improves the quality of insights later. When the target user is well defined, usage patterns and feedback are easier to interpret and act on.
Step 3: Clarify the core value proposition
Next, articulate what value the product will deliver if it succeeds. This should be a simple statement that connects the problem to a clear outcome.
A strong value proposition answers one question: what will be better for the user after using this product?
Step 4: Decide what to include and what to exclude
This step determines scope. List all possible features, then remove anything that does not directly support the core value proposition.
A useful way to approach this is to ask:
- Does this feature help test the main assumption?
- Can learning still happen without it?
If the answer to the second question is yes, the feature does not belong in the MVP.
Step 5: Choose the most suitable MVP type
Select the MVP type that best matches the assumption you are testing. If the uncertainty is demand, a landing page may be sufficient. If it is workflow or behaviour, a concierge or single feature approach may be more appropriate.
The goal is alignment between the question you want answered and the method used to answer it.
Step 6: Build using the fastest viable approach
Build the product using tools and methods that prioritise speed and reliability over perfection. This may involve no code tools, simple custom builds, or manual processes.
What matters is that users can experience the promised value without friction or confusion.
Step 7: Release to a controlled audience
Launch the MVP to a small but relevant group of users. This could be early adopters, existing customers, or a niche community aligned with the problem being tested.
A controlled release helps ensure that feedback reflects genuine usage rather than curiosity driven traffic.
Step 8: Measure behaviour and outcomes
Observe how users interact with the product. Focus on actions rather than opinions.
Useful signals include:
- Completion of the core task
- Repeat usage
- Drop off points in the journey
The purpose of measurement is to understand what users do, not what they say they might do.
Step 9: Decide the next move
Use the data collected to make a clear decision. This may involve refining the product, adjusting positioning, testing a new assumption, or stopping entirely.
An MVP has done its job when it provides enough evidence to guide the next step with confidence.
The table below summarises the process and its intent.
| Step | Purpose | Outcome |
|---|---|---|
| Define problem | Establish relevance | Clear focus |
| Identify user | Narrow learning | Actionable insights |
| Define value | Align expectations | Meaningful engagement |
| Set scope | Control effort | Faster build |
| Choose type | Match method to risk | Reliable validation |
| Build | Enable usage | Real interaction |
| Release | Test in context | Authentic data |
| Measure | Learn from behaviour | Evidence based decisions |
| Decide | Move forward or stop | Reduced uncertainty |
Examples of Famous MVPs
Looking at well known products through the lens of their early launches helps clarify what effective validation looks like in practice.
These examples show how simple, focused early versions were used to test demand before scale, not to impress with features.
Airbnb
Airbnb began with a basic website offering short term accommodation in the founders own apartment. There was no complex platform, payment system, or automated booking flow.
The early version tested one assumption only: would people pay to stay in a strangers home? The answer came quickly through real bookings, not surveys. That signal justified building the platform that followed.
Dropbox
Dropbox validated demand without building a full product. Instead of launching software, the team released a short explainer video demonstrating how the product would work.
Viewers signed up in large numbers, confirming interest in a simple file syncing solution. This approach saved significant development effort and proved that the problem resonated before infrastructure was built.
Uber
Uber started as a limited service connecting riders and drivers through a basic interface. The service worked in a small area and relied on manual processes behind the scenes.
The early launch focused on a narrow use case rather than mass adoption. By observing repeat usage, the team gained confidence that convenience and speed were strong enough drivers to justify expansion.
Facebook was initially restricted to a single university. The product offered only a handful of features, centered on creating profiles and connecting with peers.
This limited rollout made it easier to observe behaviour and refine the experience. Strong engagement within a defined group indicated that the core idea had broad potential.
Amazon
Amazon launched as an online bookstore with a narrow catalogue. The early focus was not on becoming a general retailer but on proving that customers would buy books online with confidence.
Once purchasing behaviour was established, the model expanded into new categories. The initial version reduced risk by validating trust and logistics at a small scale.
What these examples have in common
Despite differences in industry and scale, these early launches share key characteristics. Each focused on testing one critical assumption and avoided unnecessary complexity.
The table below summarises what each early version was designed to validate.
| Company | Early focus | Assumption tested | Outcome |
|---|---|---|---|
| Airbnb | Simple listings | Will people pay to stay in homes | Confirmed demand |
| Dropbox | Demo video | Is there interest in file syncing | Strong sign ups |
| Uber | Local service | Will users choose on demand rides | Repeat usage |
| Closed network | Will users engage consistently | High retention | |
| Amazon | Book sales | Will customers buy online | Scalable trust |
Common Minimum Viable Product Mistakes to Avoid
A minimum viable product is meant to reduce risk, not introduce new ones. Many MVPs fail not because the idea is weak, but because avoidable mistakes distort learning and lead teams in the wrong direction.
Building too much, too soon
One of the most common mistakes is overbuilding. Teams often add features to feel competitive or complete, even when those features are not required to test the core assumption.
Excess scope slows down launch, increases cost, and makes it harder to understand what actually influenced user behaviour. When everything is included, nothing is clearly responsible for success or failure.
Solving multiple problems at once
An MVP should focus on one problem only. Attempting to address several use cases at the same time leads to diluted results and confused users.
When adoption is low, teams struggle to diagnose why. Was the problem unclear, the solution weak, or the audience wrong? Narrow focus makes learning clearer and decisions easier.
Relying on opinions instead of behaviour
Feedback is useful, but behaviour is decisive. A frequent error is giving too much weight to what users say rather than what they do.
Positive comments, survey responses, or encouragement from peers can create false confidence. Usage data, completion rates, and repeat engagement provide far more reliable signals of demand.
Testing with the wrong audience
Early validation only works if the product is tested with people who genuinely experience the problem. Testing with friends, colleagues, or a broad general audience often produces misleading results.
When the wrong users are involved, interest may appear high while real market demand remains unproven.
Measuring the wrong signals
Not all metrics are useful at the MVP stage. Tracking numbers that look impressive but do not inform decisions leads to poor judgement.
Examples of weak signals include:
- Total sign ups without usage
- Page views without actions
- Social engagement without conversion
Strong signals are directly tied to the outcome the product exists to test.
Ignoring negative results
Another common mistake is treating poor results as a reason to collect more data rather than make a decision. An MVP is meant to produce clarity, even when the outcome is uncomfortable.
Delaying decisions wastes time and resources. Clear evidence that an assumption is wrong is valuable and should trigger change.
Treating the MVP as a finished product
An MVP is not the end goal. Teams sometimes invest heavily in polishing early versions instead of learning from them.
This mindset turns a learning tool into a maintenance burden and slows progress. The purpose is insight, not longevity.
The table below summarises these mistakes and their consequences.
| Mistake | Why it happens | Impact |
|---|---|---|
| Overbuilding | Fear of launching incomplete | Delayed learning |
| Multiple problems | Desire to appeal widely | Confused signals |
| Opinion driven feedback | Seeking validation | False confidence |
| Wrong audience | Convenience | Invalid results |
| Weak metrics | Poor measurement focus | Bad decisions |
| Avoiding failure | Emotional attachment | Wasted resources |
| Over polishing | Perfection mindset | Lost momentum |
Conclusion
A minimum viable product provides a disciplined way to test ideas in real conditions before committing significant resources.
When built with clear intent, an MVP reduces uncertainty, sharpens decision making, and creates a foundation for sustainable growth.
Ultimately, the value of an MVP lies in what it teaches. Whether the outcome is validation, refinement, or a clear stop decision, the insight gained early saves time, capital, and effort over the long term.
We want to see you succeed, and that’s why we provide valuable business resources to help you every step of the way.
- Join over 23,000 entrepreneurs by signing up for our newsletter and receiving valuable business insights.
- Register your business today with Entrepreneurs.ng’s Business Registration Services.
- Tell Your Brand Story on Entrepreneurs.ng, let’s showcase your brand to our global audience.
- Need help with your marketing strategy? Get a Comprehensive Marketing and Sales Plan here.
- Sign up for our Entrepreneurs Success Blueprint Programme to learn how to start and scale your business in just 30 days.
- Book our one-on-one consulting and speak to an expert about structuring and growing your business.
- Visit our shop for business plan templates and other valuable resources to guide you.
- Get our Employee-Employer Super Bundle NDA templates to legally protect your business and workforce.
- Advertise your business to over a million entrepreneurs through our different advertising packages.
Frequently Asked Questions
What is a minimum viable product in simple terms?
A minimum viable product is the simplest version of a product that allows a business to test whether people actually want it.
It is built to learn from real user behaviour, not to showcase every possible feature. The focus is on proving demand and reducing uncertainty early.
How long does it take to build a minimum viable product?
The time required depends on the problem being tested and the MVP type chosen. Some MVPs can be launched in days, such as landing pages or manual services, while others may take a few weeks.
The key principle is speed to learning, not development duration.
How much does a minimum viable product cost?
There is no fixed cost. A minimum viable product can range from very low cost experiments to more involved builds, depending on scope and tools.
What matters is that the cost is significantly lower than building a full product before demand is validated.
What features should be included in a minimum viable product?
Only features that directly support the core value proposition should be included. If a feature does not help test the main assumption, it does not belong in the MVP.
This keeps learning focused and avoids unnecessary complexity.
Is a minimum viable product only for startups?
No. While startups use MVPs frequently, established businesses also rely on them to test new products, services, or markets. Any organisation launching something new can benefit from early validation.
How do you know if a minimum viable product is successful?
Success depends on the question the MVP was designed to answer. Common signals include users completing key actions, returning to use the product again, or demonstrating willingness to pay.
A minimum viable product is successful when it provides clear evidence to guide the next decision.
Can a minimum viable product fail?
Yes, and that outcome can still be valuable. If a minimum viable product shows that demand is weak or assumptions are wrong, it prevents larger losses later. Early failure, when properly measured, saves time and resources.
What is the difference between a minimum viable product and a beta product?
A minimum viable product is built to test assumptions and generate learning, while a beta product is usually a near complete solution being refined before full release. The intent and success criteria are different.
Do you need technical skills to build a minimum viable product?
Not always. Many MVPs are created using simple tools, manual processes, or existing platforms. Technical complexity should only be introduced when it is necessary to test the assumption in question.
What should happen after a minimum viable product is launched?
After launch, the focus should be on analysing behaviour, reviewing outcomes, and making a clear decision. This may involve refining the product, testing a new assumption, or deciding not to proceed further.
