Jargon Buster / MVP (Minimum Viable Product)
MVP (Minimum Viable Product).
Brand, Web & DesignThe simplest version of a product that real users can use, built to test whether an idea deserves more investment.
What is an MVP?
An MVP (minimum viable product) is the simplest version of a product, tool or service that real users can use and that delivers enough value to test the core idea. The term was popularised by Eric Ries in The Lean Startup. The aim is learning: release something small, see how people actually use it, then decide what to build next based on evidence instead of assumption.
Why it matters
Building a full product before anyone has used it is the most expensive way to find out you were wrong. An MVP lets a business test demand for a new client portal, booking tool or internal AI assistant for a fraction of the full cost, then invest further only in what proves useful. It also gets value into users' hands sooner, which builds momentum and internal support for the project.
What good looks like
- One core problem Solve a single, specific problem well and leave the nice-to-haves for later releases.
- Real users Put it in front of the actual people it is for, customers or staff, as early as possible.
- Defined success measure Decide in advance what usage or result would justify building more.
- Quality where it counts Keep scope minimal, but make what you ship reliable and secure.
- Planned next step Budget for iteration after launch, because the MVP is the start of the work.
The honest view
MVP is widely misused as an excuse for shipping something poor. "Minimum" refers to scope; it does not license bugs, weak security or a confusing interface, because users will judge the idea by the experience. The opposite problem is just as common: the MVP collects features during planning until it is effectively the full product, built slowly and at full cost. If your MVP will take six months, it is probably not minimal. AI-assisted build tools have made genuinely small first versions much quicker to produce.
What to do about it
Write the single problem your product idea solves in one sentence, and name who has it. Then list every feature you have imagined and cross out anything that is not essential to solving that problem for those people. Decide what result after four to six weeks of use would convince you to keep going. Brief the build on that short list, with time and budget held back for the second iteration.
Related terms.
Discovery Phase
The research and planning stage at the start of a project that defines what to build, for whom and why.
Brand, Web & DesignSee more UUX Design
Designing how a website or product works for the people using it, so tasks feel clear and easy to complete.
Brand, Web & DesignSee more NNo-Code and Low-Code
Ways to build websites, apps and automations with visual editors and ready-made blocks instead of hand-written code.
AI & AutomationSee more WWireframe
A simple layout sketch of a page showing structure and content priority before any visual design is applied.
Brand, Web & DesignSee moreGot a question about your own setup? Let's talk.
Your first call is with our founder, Rhodri Williams.