MVP is often used as an excuse for something half-hearted. It's not.
An MVP, minimum viable product, is the smallest version of a system that is really usable and from which you learn whether the approach is correct. It is not about less quality but about less size: one process completely finished, instead of ten processes half done. What you learn determines what you build next.
IN COMMON LANGUAGE
Small in size, not in quality
The most common mistake is to interpret an MVP as a sloppy first version. That results in something that no one wants to use, after which the conclusion is that the idea didn't work: while the execution was the problem.
Small means: fewer functions, completely finished. One workflow that works from start to finish, with a decent interface and working error handling.
The point is learning. After six weeks of use you will know which assumptions were correct. Almost always, part of what seemed indispensable beforehand turns out to be barely used: and that is exactly the budget that you have not wasted.
WHY IT MATTERS
When this is the right route
For a process that you are not yet clear on, or for an idea of which you do not yet know the value, an MVP is almost always cheaper than a complete specification.
With something you have been doing manually for years and know in detail, it is less necessary. Then you know what needs to be done and delivering it step by step is enough.
- One process completely finished — not ten processes half.
- Real users, real work — a demo does not provide useful information.
- Think in advance about what you want to learn — otherwise you won't measure anything afterwards.
- Six to eight weeks — shorter learns too little, longer is no longer an MVP.
- Be prepared to delete — half of the wish list turns out to be unnecessary afterwards.
FREQUENTLY ASKED QUESTIONS
More about an MVP
Is an MVP cheaper?
The first delivery moment is cheaper, but not automatic at all. The savings come from not building something that will not be used afterwards, and in practice that is a large part of any wish list.
Can I extend an MVP later?
If it's built for that, yes. We build an MVP as a real first version of the final system, not as a throw-away prototype: that saves a rebuild later.
What if the MVP is disappointing?
Then you have learned for a fraction of the budget that the approach is incorrect. That's a good outcome, even if it feels different. The alternative is the same discovery after the full budget.
CONTINUE READING
Of course, continue reading about this subject.
Small start?
Tell us what you have in mind. We cut it into a first version that you can use within weeks.