After reading this, my understanding of a product manager’s job has changed. I used to think it was mostly about following clear processes and managing technical tasks, but now I see it’s much more complex. Product management involves a lot of relationship-building and decision-making in uncertain situations. You’re responsible for the product’s success, but without the authority to directly control people, so you have to rely on influence and collaboration.
One thing that really stood out is the need to handle ambiguity. I always assumed product managers had set roadmaps, but it turns out that much of the job involves figuring things out as you go. You often have to make decisions with incomplete information and balance the needs of users, the business, and the technical team. The role is about facilitating solutions, not dictating them, which is something I hadn’t fully appreciated before.
The descriptions of bad product managers, like the Jargon Jockey and Product Martyr, made me think about how easy it must be to fall into those patterns, especially when under pressure. It seems like the best PMs know how to avoid burnout and insecurity, which can lead to overworking or trying too hard to prove themselves.
If I could ask the author a few questions, I’d want to know more about handling the emotional toll of the job. How do you stay resilient when faced with constant ambiguity? And how do you bring people on board when they resist, especially if you don’t have much authority? I’d also ask how to manage the personal insecurities that come with the job—how do you stay confident and avoid falling into those negative behaviors?
Overall, this has shown me that product management is about leadership and adaptability, not just following frameworks. It seems tough, but it is a rewarding role if you can master the balance.
