Interactive graph
Minimum Viable Product
Table of Contents
Ship the smallest version that proves someone actually wants this - polish comes after proof.
Key Concept
- The smallest thing I can ship that tests the idea - not a polished fantasy.
- I would rather publish a rough note or prototype and learn than polish in private for months.
- Client work: Selling Static Sites is the same loop - one pilot site on Free Tier Hosting Stack before I package tiers and upsells.
Level 1 - Recognize
A minimum viable product is the smallest shippable version that tests whether anyone wants the idea.
Level 2 - Explain
Like baking one cupcake before you make a whole wedding cake, rough proof beats polished fantasy in private.
Level 3 - Use
Publish the rough note or prototype, watch reaction, iterate - months of private polish without a user is avoidance.
Level 4 - Connect
The smallest release must still test demand: too little scope gives a false signal, while too much delays the learning that Drafting in Public makes possible.
Level 5 - Create
Create a Lean Startup test, Ship It to real users, and extend what earns attention into Evergreen Notes or a fuller product.
Examples
- I sat on a half-planned birthday party for three months - we ordered pizza, one banner, kids had a blast, learned more than another month of Pinterest.
- We ran one new play in scrimmage before printing playbooks for the whole league - learned more in forty minutes than another week of polish.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Evergreen Notes | when rough ship beats two-year polish |
| extends | Creative Output | Ship the smallest version that tests the idea instead of polishing a fantasy in private |
| extends | Free Tier Hosting Stack | Ship the smallest live site - free tier stack covers the first slice |
| extends | Lean Startup | Ship-to-learn loop Ries named |
| extends | Selling Static Sites | Client MVP lane - sell the smallest site that solves the job |
