MVP

An MVP is not a full product with features stripped out, and it's not a landing page with nothing behind it — it's the smallest set of functionality that lets a specific type of customer solve a specific problem, built to learn whether the idea works, not to impress. The most common failure modes are building too much (features "just in case"), building too little (no real working product), and building for an imagined customer instead of a confirmed real one.

• —An MVP should ship in weeks, not months — if your feature list takes longer, you haven't cut hard enough.
• —Every feature beyond what the core "specific person, specific task, specific outcome" sentence requires belongs in a later version, not the MVP.
• —The goal of an MVP is learning, not impressing — a smaller MVP that ships faster teaches you more per week than a polished one that ships later.

This is the exact lesson that covers this term in depth — with examples, diagrams, and a hands-on exercise.