Turning a decision into something shipped. The mechanics of scope, sequence, the documents that change what gets built, and the week in which everything changes and you have to decide what to cut.
| # | Lesson | The question it answers | |
|---|---|---|---|
| 01 | Writing a PRD That Gets Built | Which sections change what gets built, and which are read by nobody? | ✅ |
| 02 | Scoping and the First Version | What does minimum actually mean, and what does it never mean? | ✅ |
| 03 | Sequencing Work You Do Not Control | How do you order work across people who do not report to you? | |
| 04 | Estimates and What They Are Worth | Why is negotiating an estimate harmful, and what do you do instead? | |
| 05 | Technical Debt as a Product Decision | When is it yours to weigh in on, and how? | |
| 06 | Handling Change Mid Build | Something changed in week three. What do you cut, and who decides? | |
| 07 | Quality, Testing and What Ships Broken | What level of defect is acceptable, and who decides that? | |
| 08 | Launch Readiness | What has to be true before it ships: docs, support, pricing, legal, rollback? | |
| 09 | Rollouts, Flags and Canaries | How do you ship something risky without shipping it to everyone? | |
| 10 | The Post Launch Readout | What do you measure at seven, thirty and ninety days? | |
| 11 | When a Project Is Late | What are the four honest options, and which do teams avoid? | |
| 12 | Shipping Nothing | When is cancelling the right call, and how do you do it well? |