Finding something worth building, and killing the rest cheaply. The half of the job that happens before anybody writes code, and the half most teams compress into a week because it produces no visible output.
| # | Lesson | The question it answers | |
|---|---|---|---|
| 01 | Finding a Problem Worth Solving | Which demand signals mean something, and which are noise? | ✅ |
| 02 | Interviews That Are Not Useless | Which questions produce facts, which produce flattery, and how many people is enough? | ✅ |
| 03 | Jobs, Alternatives and Doing Nothing | What do they do today, including nothing, and why would they stop? | |
| 04 | Sizing a Problem | How many people, how often, and how much does it cost them now? | |
| 05 | Writing the Problem Statement | How do you write one page that is falsifiable and contains no solution? | |
| 06 | The Riskiest Assumption | Which belief, if wrong, makes everything else irrelevant? | |
| 07 | Cheap Tests Before Expensive Builds | What can you learn in a week that would otherwise take a quarter? | |
| 08 | Reading Support and Sales as Data | How do you use the channels that already exist? | |
| 09 | Quantitative Discovery | What can the warehouse tell you that interviews cannot? | |
| 10 | Killing Ideas Early | How do you say no to your own idea, in writing? | |
| 11 | Discovery as a Habit, Not a Phase | How does this become continuous rather than a stage? | |
| 12 | The Discovery Readout | What does the document look like, and who reads it? |