Preface: Why this book now

You could learn product management in 2015. Read a blog. Shadow a PM. Write a PRD. Get a job.

You cannot learn it that way in 2026. Not because the blogs are wrong. Because the job moved.

What changed

Speed. A junior PM with good prompts can produce in an afternoon what used to take a team a month. The artifact is no longer the moat.

Proof. Data, prototypes, user research synthesis — all cheap and fast. “We think” loses to “we tested” faster than ever. So does “we tested” if the test was sloppy.

Power. Engineers and designers have the same AI you do. Your value isn’t generating the work. It’s deciding which work is worth generating.

The job didn’t disappear. It moved up one abstraction layer. And that move made it harder to learn by watching, because the visible parts — the docs, the decks, the dashboards — got easier, and the invisible parts — the judgment, the conflict, the conviction — got more exposed.

What this book is

This is not “how to be a PM.” It is “how to know if you want to be one.”

Architect? (Crites and Ward 2014) asked: Do you like the work? Do you like the problems? Do you like who you become doing it?

Same test. New profession.

The job is ambiguity managed through narrative, delivered by someone willing to take the blame. AI made the delivery faster. It did not change who takes the blame.

If you finish this book and decide PM isn’t for you, that’s a good outcome. Better to know before you take the job, before you spend two years in the wrong room.

If you finish and you’re still in — good. Clarity is the first asset of the job.

Let’s start.

References

Crites, Roger K., and Cara Ward. 2014. Architect?: A Candid Guide to the Profession. MIT Press.