I use the metaphor carefully
Thinking of product managers as products can be a useful reminder that I have users, needs, constraints, and feedback. It becomes unhelpful when it turns people into optimization projects or suggests that a career can be managed like a simple funnel.
My version of the metaphor is about deliberate learning. I ask which partners depend on my work, what makes that work useful, and where the experience is confusing or costly. I do not treat a hiring manager as my only “customer”; teammates, customers, and the people affected by product decisions also matter.
What I would improve
I would choose a specific capability rather than “become a better PM.” Maybe I need to synthesize research more clearly, make smaller decisions faster, understand a technical constraint, or communicate trade-offs to executives. I would define an observable practice, such as writing a decision brief, running a sharper interview, or asking engineering for feasibility input earlier.
Then I would seek feedback from people who saw the work. I would compare my intention with the effect, look for patterns, and adjust. A single compliment or criticism is not a complete diagnosis.
Keep the work humane
I would not turn every interaction into a performance metric or promise that continuous improvement removes uncertainty. Product management includes judgment, context, and relationships that cannot be reduced to a personal score.
The useful question is simple: what problem am I trying to solve for the people I work with, what evidence would show improvement, and what small change will I try next?
My bottom line
I use this approach to make the work clearer, not to add process for its own sake. Start with the problem, make the trade-offs visible, and revisit the decision when evidence changes.
If you are building the fundamentals behind this kind of work, the Product HQ product management certification is a useful next step. I also share practical lessons in the Product HQ newsletter.