3. Reading the collection back

§Read the six whitepapers in a row and a single argument shows through them, one that is invisible while you are inside any single stage. The argument is that product work is the discipline of deciding what to build under uncertainty, and that the discipline is a chain of ways to earn the right to build. Each whitepaper is one gate in the chain. Each gate stops a team from building something it has not earned. This chapter reads the chain back, stage by stage, and shows how each hands the next a document that the next argues with.

§ 3.1Foundation: who is answerable#

§The first whitepaper answers a question the others assume: who holds this. Its claim is that product at a startup is not a role but a responsibility, the ownership of strategy, vision and execution at once, held by one accountable person on a team of one to five. It hands the rest of the collection a person. Every later gate needs someone answerable to stand at it, and Foundation names them. Without it, the chain has no one to walk it.

§ 3.2Discovery: the judgment before the method#

§The second whitepaper is about judgment, not process. Its claim is that teams fail discovery not for lack of a method but for lack of the judgment to tell a problem from a solution, to treat learning as continuous rather than a phase, and to know which method's assumptions fit a company of five. It profiles the lineage, Design Thinking, Jobs to Be Done, Lean, Agile, the Double Diamond, and asks of each what it gave, what it assumed, where it breaks. It hands the third whitepaper a way of thinking, so that the practice has judgment behind it rather than ritual.

§ 3.3Sprint: earn insight, then test evidence#

§The third whitepaper is the practice, and it is where the phrase "earn the right to build" is most literal. Insight is earned: from research into who tried before, from conversations about what people did rather than what they would do, from synthesis until patterns outrank anecdotes. Then evidence is tested: options before choices, the cheapest thing that can be wrong in a stranger's hands, every assumption sorted into validated, open or discarded. It hands the fourth whitepaper a written position: a tension map and a two-act memo. The position is a document that can be argued with, which is the only kind worth handing on.

§ 3.4Strategy: commit by excluding#

§The fourth whitepaper turns the position into a direction, and its claim is Rumelt's: a strategy that does not exclude is a wish. It builds a ladder from mission to first unit of work, each level the input to the next, each level saying what it will not do. It hands the fifth whitepaper a first version and a set of bets, each with the critical question that would prove it wrong. The exclusions are the strategy, and they are what make the first version small enough to be a real test rather than a compressed fantasy of the whole vision.

§ 3.5Business Design: prove it pays#

§The fifth whitepaper asks the question the first four defer: when it exists, is it a business? Its claim is that desirable is not enough, that a first version people love and that loses money on every user is a gift. It holds desirability, feasibility and viability as three sets of hypotheses, each with a number and a date, and collects them into one list of what has to be true, sorted by what would kill the business first. It hands the sixth whitepaper that list, which is a set of claims waiting to meet behavior.

§ 3.6Experimentation: the first version is a hypothesis too#

§The sixth whitepaper says the discipline does not stop at launch; the instrument changes. Before launch you tested with prototypes and strangers; after, with a live product and real behavior. It runs loops, validation before growth, retention before everything, each loop a hypothesis with a threshold set in advance. It takes the fifth whitepaper's list and checks its rows against behavior, and it feeds the results back up the chain: confirmed bets become foundations, refuted ones trigger the iterate-or-pivot decision, and the strategy ladder is rebuilt on firmer ground.

§ 3.7The chain is the method#

§Marty Cagan's four risks, value, usability, feasibility, viability, are one way to see why the chain has the shape it does: each gate retires a risk, and a risk not retired at its gate is retired in production, expensively, by customers. Discovery and Sprint retire value and usability. Strategy sequences the retirement. Business Design retires viability. Experimentation confirms all of them against behavior. Foundation puts a person in charge of the sequence.

§That is the collection, read back as one argument. The next chapter draws out the five rules that recur at every gate, because a chain this long has a few principles that hold all the way down it.