What you'll take away
- 01 The "minimum shippable" frame and how to use it to compress a six-month build into six weeks.
- 02 How to defend a stop-line — the moment construction is done — against the team's instinct to keep adding.
- 03 Practical rules for the small build team, with examples from twelve products shipped and exited.
Once you have validated what to remove, the next discipline is harder. It is the discipline of building only what ships, and stopping the moment it does.
Build is the second volume of the four-book Subtract to Ship method. It is a working manual for the construction phase — not a long survey of frameworks, but a tight set of rules, examples, and stop-lines drawn from twelve products shipped and exited.
What this book covers
- The minimum shippable spec — what it actually contains, and what teams keep accidentally smuggling in.
- Stop-line discipline: how to recognize the moment construction is done, and how to defend it.
- Build-team shape: how small the team really needs to be, who owns the kill decisions, and how to run a weekly build review that does not slide into feature-creep.
Who it is for
Operators in the build phase — founders, heads of product, engineering leads. Innovation teams who have run a Subtraction Audit and now have to hold the line during construction. Anyone who has watched a clean spec get re-bloated three weeks into the work.
Series context
Build is the second of a four-volume set: Validate · Build · Grow · Scale. Read after Validate if you have already chosen what to ship; on its own if you are mid-construction and need the stop-line argument.
Tell me when it ships
Get a note when Subtract to Ship: Build is available.
Continue reading