All issues
Ship Notes · SN #04·18 Jan
Build the right thing first
The order you build in decides how early you learn. Two notes on front-loading the risk instead of the easy parts.
1. Build the riskiest part first
Tackle the part most likely to sink the project before anything else — the unproven integration, the unclear workflow, the assumption everything rests on. If it's going to fail, find out in week one, not week ten.
2. Fake it before you build it
A clickable prototype or a manual back-end can answer “do people actually want this?” without the cost of building it for real. Ship the illusion, learn from it, then build only what survives contact with users.
Previous issue
SN #03 — Boring infrastructure, fast teams