After doing the reading, the biggest thing that stood out to me is how weirdly undefined the product manager role is. It’s like everyone agrees a PM is important, but nobody can fully explain why in one sentence. The author makes it pretty clear that a PM’s job isn’t to be the boss of anyone or the all knowing visionary that magically solves everything. Instead, the job is basically to make sure the right conversations are happening, the right people feel supported, and the actual product decisions are grounded in what users need. So the job becomes about influence; earning trust, making things legible for everyone, and removing roadblocks so designers and engineers can actually do their best work and collaborate. What I see now is that a good PM is comfortable being uncomfortable. They’re fine with incomplete information, shifting priorities, changing constraints, and having to take action without full clarity. The job also seems to rely heavily on communication.
If I could ask the author a couple questions, the first one would be about burnout. PMs are constantly switching contexts and holding mental maps of everything happening in a product. How do you build guardrails around a role that could easily become 24/7 emotional labor? I’d also want to know how new PMs can tell the difference between being helpful and overstepping. Since the role has so many gray areas, it feels easy to accidentally take on too much, or to unintentionally micromanage because you’re scared something might fall apart.
The last question I’d ask is how PMs can avoid becoming one of the bad archetypes. It’s easy to say “don’t be the martyr, don’t be the hero, don’t be the Steve Jobs wannabe,” but it’s harder to notice when you’re slowly slipping into those habits. What are the early warning signs? And what’s the fastest way to course-correct when you realize you’re acting like one of the PMs the book gently makes fun of?
