After reading Chapter One of Product Management in Practice, I see the product manager’s role as ensuring the success of both their product and their team. A PM exists to create impact for the business, users, and the people they collaborate with. What stood out to me in the reading is that this impact is not defined by a checklist of responsibilities. Instead, a PM must constantly figure out what needs to be done, often without clear instructions. To the author’s point that “that’s not my job” doesn’t apply to PMs, I would ask: how do you set boundaries when, as a PM, everything feels like your responsibility and you can’t simply step back from a task?
I also learned that PMs sit at the center of competing perspectives: designers, developers, business leaders, and end users. Their job is to align these groups, facilitate difficult conversations, and push toward outcomes that matter. This means the role is highly communication-driven, and the definition of success can vary widely depending on the company and context. As the author points out, there isn’t a single, cookie-cutter definition of what a PM is. Instead, we mostly see descriptions of what PMs do. This does raise questions for me about how to find more information early during the interview process. I would ask: How can PMs identify what kind of product management work they will be doing during interviews? And if we have a preference for certain types of PM responsibilities, how can we ensure a given company aligns with that?
One detail that changed how I view the role was the discussion of hours. Initially, the author mentioned working 60-hour weeks, which reinforced the stereotype that PMs are expected to work long hours. However, he clarified that this was more a reflection of his early lack of productivity and experience, not an inherent requirement of the job. I would ask the author what strategies helped you move from 60-hour work weeks to a more sustainable schedule of working 10–4 most days? His reminder that your success is not defined by the hours you work but by the impact you are making feels reassuring. It reframes the role around outcomes and makes me less anxious about pursuing PM work in the future.
