Review
Few product books earn a permanent spot on my recommend list. This one does. Perri names something I had felt for years but never had language for: the moment a team starts measuring itself by what it ships instead of what it changes.
She calls it the Build Trap. Project management habits creep into product teams, and velocity starts to matter more than value. Nobody sets out to build the wrong things. It happens because shipping is easy to measure and outcomes are not.
Getting out takes more than a new ritual. It means rethinking incentives, team shape, and how you define done. Perri's four levels of strategy, vision, strategic intent, product initiatives, options, give teams a way to stay aligned without needing permission for every decision.
The Product Kata section is the most practical part of the book. It is a repeatable way to stay attached to the problem instead of falling in love with your first idea. I still reach for it.
Top 10 product book. Recommended without reservation.
Key Takeaways
The parts worth keeping:
- Shipping features feels productive. Confirming they created value is the actual job. If nobody is researching customer needs or measuring the impact of what already shipped, that is the Build Trap.
- Red flags: user research gets skipped in favor of building more, roadmaps are stuffed with too many projects, deadlines matter more than customer metrics, and the team cannot agree on what matters most.
- Escaping it means shifting from managing outputs to managing outcomes. Being agile is not enough on its own. Agile makes shipping faster, it does not tell you if you are shipping the right thing.
- Organize teams around value streams, not APIs or technology boundaries. Once an API is stable, move the team on to bigger problems rather than keeping them staffed against it forever.
- You are not done when you ship. You are done when the outcome you set out to create actually happened.
The four levels of strategy
How a multi-year vision turns into what a team actually ships this week:
| Vision | Where the business is headed and what impact it wants to have, on a multi-year horizon |
| Strategic intent | The specific challenges standing between here and that vision |
| Product initiatives | The user problems worth solving in order to address that challenge |
| Options | The different ways a team could go about solving that problem |
Product Kata
The problem-solving loop Perri borrows from Toyota Kata, and the part of the book I still reach for:
| 1. Understand the direction | Company vision, strategic intent, and the product initiative in question |
| 2. Analyze the current state | Where the intent and the initiative actually stand today |
| 3. Set the next goal | The product initiative's near-term option and target |
| 4. Choose the step | Problem exploration, solution exploration, or solution optimization, depending on where you actually are |