Choose a book for the problem I have
I would not call one product management book the best for everyone. I choose reading based on the problem I am trying to solve: understanding customers, framing a strategy, improving discovery, working with engineers, or leading through uncertainty. A book is most useful when I can connect its ideas to a real decision rather than collect recommendations.
Before starting, I would check the author’s context and the age of the examples. Product practices change, and a confident framework still needs to be tested against the product, market, and team in front of me.
Read actively and compare ideas
I would keep a short note for each useful idea: what assumption it makes, where it might apply, what evidence would challenge it, and which small experiment could make it concrete. I would compare books that emphasize different lenses. A growth or business strategy book may not answer a discovery problem, and a delivery guide may not resolve a positioning decision.
I would also discuss the ideas with teammates. The goal is not to turn a reading list into a shared vocabulary exercise; it is to improve the quality of the questions we ask and the choices we make. If a recommendation includes a template, I would adapt it rather than copy it mechanically.
Make learning part of the work
I would choose one practice to try, define what I expect to learn, and revisit the result. If the idea does not fit our customers or constraints, that is useful information too. Reading should widen judgment, not replace research, customer conversations, or evidence from the product.
My bottom line
I use product books as prompts for better thinking, not as authority. The Product HQ product manager certification offers a structured foundation, and the Product HQ newsletter shares practical guidance. For a shorter starter pack, see the Product HQ guide and the PM Template Kit.