When I wrote the first edition of this book, the hardest part of product management was the same as it had always been: deciding what to build, for whom, and why, and then getting a room full of smart, busy people to build it together. That is still the hardest part. What has changed is almost everything around it.
In the space of about two years, AI went from a feature on a few roadmaps to a working layer of the product team itself. By mid-2025, 88 percent of organizations told McKinsey they were using AI in at least one business function, up from 78 percent a year earlier, and 62 percent said they were at least experimenting with AI agents.1 Product managers now have tools that draft requirements, summarize a week of customer calls before breakfast, watch dashboards overnight and flag what moved. Some of those tools are good. Some are confidently wrong. All of them change what a product manager’s day looks like.
They do not change what a product manager is for. Someone still has to own the outcome. Someone still has to sit with a nurse at the end of a twelve-hour shift and understand why the software she was given makes her job harder. Someone still has to tell the CEO that the feature the biggest customer asked for is the wrong bet, and be right about it. AI makes the work faster. It does not make the judgment optional. If anything, the judgment matters more, because a team that can build twice as fast can also build the wrong thing twice as fast.
So this edition does three things the first did not.
It covers the numbers. The first edition promised chapters on profit and loss, unit economics and portfolio management, and did not deliver them. Chapters 6 and 7 do. A product manager who cannot read a P&L is negotiating with one hand tied behind their back.
It puts AI where it belongs: inside the work. Every chapter ends its main argument with a section called How AI changes this, and Chapter 17 is devoted to building AI products and leading teams that include AI agents. I have tried to be specific about what to hand to an agent, what to keep, and how to tell the difference.
It shows the work. Most chapters open with a scene from one fictional company, Brindlepath, followed through the whole book, and most include worked examples, templates and a one-page checklist. The figures are diagrams and charts you can use in your own planning, not decoration.
I have spent most of my career in product, much of it in healthcare, where the stakes are high, the buyers are many and the regulations are real. That shows in the examples. But the book is written for product managers in any kind of software. If you can ship a product that a hospital will buy, a clinician will use and a compliance officer will sign off on, you can ship almost anything.
Robert Merrell