I approached this book with the same level of expectation that I would have approached another “buzzword-filled” guide to products, the kind that tells you to be customer-driven but never actually explains what that looks like in action. What I got instead was a guide that gets straight to the point and shows you how to think, talk, and plan in a way that actually gets results. The authors make a simple argument that hits hard. Most teams do not fail because someone cannot write a user story or run a retro. They fail because the conversations that inform their goals are unclear from the very beginning. “Let’s improve the experience,” or “Let’s drive engagement,” and everyone agrees, even though nobody is thinking about the same thing.
The book fixes this with a mix of clear language, tight syntax, and visual maps that bring alignment out into the open. The VERB + NOUN concept may seem trivial at first, but once you begin applying it, you’ll see just how big an impact it has on the room. You stop speaking in generalities and begin speaking about concrete actions you’d like the customer to take and how you’ll know they’ve accomplished it. The examples are biting, and the comparisons are effective without being preachy.
Get Connecting Goals to Impacts and Outcomes by Claude Hanhart Here!
My favorite part is the section on mapping. Empathy Mapping, Impact Mapping, Journey Mapping, Value Stream Mapping, and Story Mapping are not presented as shiny frameworks but as tools that pull the fog out of the conversation. When you put these maps on the wall everyone can finally see where the gaps, assumptions, and contradictions live. It becomes much harder to hide behind pretty language.
The deliverables section is also strong. The book walks through pitches, future press releases, user stories, examples, epics, and even defect documentation in a way that feels grounded in real work. Nothing feels theoretical or academic. You can take almost any chapter and apply it in your next planning session.
The final part ties everything back to strategy through living documentation, hypothesis writing, and OKRIs. This part is especially useful if you have watched your roadmap drift away from your goals without anyone noticing.
If you work in product, design, engineering, research, or leadership, this book will make your conversations tighter and your outcomes clearer. It gives you language and structure that make teams faster without making them sloppy. It is one of the most practical product books I have read in a long time.