MVP (Minimum Viable Product)

The smallest thing you can build that lets real users get real value and teaches you whether the idea works.

Example

One workflow, done properly, for one type of customer.

Minimum refers to scope, not to quality. A broken product does not test your hypothesis — it tests whether people tolerate bugs.

Prototype — A non-production mock-up used to test a design or an interaction, usually not built on real infrastructure.
Proof of concept (PoC) — A narrow build proving that something is technically possible.
Product-market fit (PMF) — The point at which you have built something a specific group of people genuinely want, evidenced by their behaviour rather than their compliments.

What an MVP actually is — Minimum refers to scope, not quality. A broken product does not test your hypothesis — it tests whether people tolerate bugs. (10 min)
Cutting scope without cutting value — How to decide what goes in v1, and the three questions that resolve most arguments about it. (12 min)
Prioritisation frameworks, and when each applies — RICE, ICE, MoSCoW and Kano. Not a dump of frameworks — a guide to which one to reach for and when none of them help. (12 min)
Build, buy, or do not do it at all — The most valuable engineering decision is usually not writing the code. Three questions that settle it. (10 min)
The map of the whole journey — Problem → idea → customer discovery → validation → MVP → first users → product-market fit → revenue → growth → funding → scale. Where you are decides what you should be learning. (10 min)