Growth Path and Reading List
From beginner to leading a line on your own—what to shore up along the way.
From beginner to leading a product line on your own—what do you need to shore up along the way? Product judgment isn't built by reading. It's built by shipping things that break a few times. Books help you see which step you broke on—they don't walk the steps for you.
After reading, you should be able to answer:
- Which of the four stages you're currently stuck in
- What to read in each stage, and how to read so it sticks
- Why a failed project is worth more than a finished book
The four stages
Stage one: make it. Learn the tools, a technical base, and the product workflow—first solve "can I build this at all." The test: you can independently turn an idea into something that runs. Stage two: make it right. Requirements, judgment, and thinking models—know what to build and what to build first. The test: give you ten ideas, and you can rank which to do and why. Stage three: get it moving. Collaboration and process, so other people's output can be reused by you too. The test: when you're away, the work still moves forward. Stage four: explain it. Business, expression, and perspective—pull resources from the outside world. The test: you can explain your product so investors and partners actually get it. Each stage has its own bottleneck; figure out which one you're stuck in before deciding what to learn.
The reading list
Match books to the stages above. Reading one or two thoroughly per stage beats listing twenty. In stage one, read about process and tools: Marty Cagan's Inspired explains how product teams run, and Eric Ries's The Lean Startup explains how to validate with minimal cost. In stage two, read about judgment: Rob Fitzpatrick's The Mom Test teaches how to ask users so they tell you the truth, alongside the basics of KANO and user experience. In stage three, read about collaboration and organizations: Rework is about how small teams stay fast, and Frederick Brooks's The Mythical Man-Month explains why more people can make things slower. In stage four, read about business and history: Clayton Christensen's The Innovator's Dilemma explains why giants stumble, and Daniel Kahneman's Thinking, Fast and Slow maps the systematic biases in judgment. Judgment comes from practicing a model until you can reach for it without thinking, not from collecting titles. Before you pick any of these up, be clear: a title isn't a badge, it's a tool. The same book read without a concrete problem is a pastime; read with a problem in hand, it's a weapon.
How to read so it actually helps
Read with a specific question in hand. When you're stuck on something concrete, reading retains far more than a cover-to-cover pass—if you don't have a question, don't read yet. Use it once right after reading: after finishing KANO, sort your own need backlog into tiers; after reading The Mom Test, take its question list and interview three people. Reading that doesn't land on something concrete won't leave much after a week. You don't need to memorize methodology, just know where to look it up—that's also why this site exists: flip to a page when you need it, leave when you're done. Last, a failed project is worth more than a finished book: something you shipped that nobody used teaches you more than three books. The catch is you have to walk through why nobody used it—was the problem wrong, did you start building before validating, or did you build it and nobody ever knew? A failure you don't review is the same as never having tried. One more rule: after finishing a book, try explaining it to someone else. What you can't explain is what you haven't understood; being able to explain it is how you know the book has actually stuck.