Apps & products
How to Plan an MVP Without Building the Wrong Product Faster
A useful MVP is the smallest complete experience that tests a risky business assumption with real users. It is not simply a low-quality version of the final product. Define the user, problem, expected behavior and evidence first; then include only the functionality required to run that test responsibly.
Guide diagramLARK / FIELD DIAGRAM
Name the assumption before listing features
Teams often begin an MVP with accounts, dashboards, notifications and settings because those elements resemble a product. Instead, state what must be learned. For example: will restaurant managers upload availability weekly if the system produces a public menu automatically?
The assumption should connect a defined user, behavior and value. If the team cannot state what evidence would change its mind, the release is not yet designed as a test.
Build one complete outcome
A user should be able to enter the experience, understand it, complete the core task and receive a meaningful result. Five half-built journeys generate more confusion than one coherent journey because failure could come from missing functionality rather than the underlying idea.
Minimum does not mean careless. Authentication, privacy, data integrity, accessibility and payment safety still require proportionate attention. Remove optional scope, not the trust required for legitimate use.
Use manual operations deliberately
Early products can keep low-volume processes manual behind the interface. A team might review submissions, create recommendations or reconcile exceptions manually while testing whether users value the result. This avoids automating a workflow before demand and rules are understood.
Manual work should be documented and measured. It becomes technical scope only when volume, response expectations or error risk justify automation.
Set evidence and decision thresholds
Define recruitment, observation period and measures before launch. Useful evidence can include task completion, repeated use, willingness to pay, time saved or a reduction in errors. Page views alone rarely prove a workflow product is valuable.
At the review point, decide whether to continue, revise the assumption, target a different user or stop. The purpose of an MVP is to improve decision quality—not to create emotional commitment to the first implementation.
Frequently asked questions
What does MVP mean?
MVP means minimum viable product: the smallest complete product experience capable of testing an important assumption with real users. It should be narrow but sufficiently reliable to produce trustworthy evidence.
How many features should an MVP include?
There is no universal number. Include only what is required for one target user to complete the core outcome and for the team to measure the intended assumption. Supporting features belong later unless they are required for safety or trust.
Should an MVP be a website or app?
Choose the lowest-cost format that can test the behavior. A responsive web product is often appropriate when native device features or app-store distribution are not essential. The format should serve the experiment.
From reading to deciding
Make the next decision concrete.
Send Amin the business context, current problem and required outcome. You will get a direct view of what should be clarified before anything is designed or built.