MVP and proof of concept: validating an idea before you invest
Why to start small instead of building big, and how to know an idea is ready for the next step.
Every new product starts with a question: will anyone want it, and can it even be built? Answering with a full project is risky. Starting with a small validation — a prototype or a minimal version — is far cheaper.
The goal is not to build everything, but to test the riskiest assumptions as early as possible.
Proof of concept vs. MVP
A proof of concept verifies that something works technically. An MVP verifies that people want it. They are different questions and worth answering in that order — technical feasibility first, then value for users.
What the validation should contain
One key feature, one group of users and one measurable success criterion. Anything extra slows you down and distorts the result.
When to move to full development
Once you know it can be built and that users want it. The validation gives you the basis for the decision and the case for further investment.