Product experts: How I would build a useful learning list
Our reviewers evaluate writing services independently. Learn how we stay transparent, our methodology, and tell us about anything we missed.
Define expertise by useful practice
I would be careful with any list of “best” product experts. A visible profile, a large audience, or a polished framework does not automatically show that someone’s advice fits my context. I look for people who explain customer problems, decisions, trade-offs, evidence, and what they learned when an approach did not work.
I would also check whether the person’s experience matches the kind of work I need to do. A startup founder, enterprise product leader, researcher, consultant, and design specialist may each offer valuable insight, but they are not interchangeable.
Follow selectively
I would choose a small set of voices across different disciplines and compare their assumptions. When someone makes a strong recommendation, I would ask who benefits, what constraints are assumed, and which measure would show progress. I would prefer specific case reasoning over generic certainty.
I would keep a note of ideas worth testing, with the source and context attached. That makes it easier to distinguish a useful principle from a memorable quote. I would not let an expert’s reputation override customer research, product data, or the judgment of the team doing the work.
Build my own judgment
The point of following experts is not to outsource decisions. I would apply one idea at a time, observe the result, and revise my view. I would also learn from practitioners whose work is less visible but close to the customers and systems I am trying to improve.
My bottom line
I follow product experts to broaden my questions and sharpen my judgment, not to copy a persona. The Product HQ product manager certification builds a structured foundation, and the Product HQ newsletter shares practical guidance.
