I used to think of a product manager as basically the person who connects teams and makes sure everything in the product cycle runs smoothly. But after reading this, I realized it’s way more than that. It’s not just about managing tasks, it’s also about how the team works together and stays aligned.
What stood out to me is how tricky that balance can be. There seems to be a thin the line is between leading effectively and overstepping in ways that could hurt the team. From the passage, it’s clear that PMs carry enormous responsibility without much authority, which forces them to rely on influence, trust, and collaboration rather than directives. However, if a PM pushes too hard or micromanages, they risk damaging relationships and morale, yet if they step back too much, the product and team could falter. That constant balancing act feels both daunting and delicate, almost like walking a tightrope where one misstep could have lasting consequences.
However, I feel like lots of these behaviors often stem from deeper organizational pressures. In my experience working on collaborative projects, I’ve seen peers (and sometimes myself) slide into over-control not out of arrogance but out of fear. I remember a time when, as part of a group project, I found myself taking on too much control, not because I thought I knew best, but because I was afraid of being overlooked or not contributing enough. This fear made me push harder to make my work visible and indispensable, even as I sensed it was causing frustration among my teammates. The book critiques the behaviors, but I think the more nuanced question is how organizational cultures unintentionally reward these unhelpful tendencies by valuing constant visibility over quiet influence.
If a company only cares about numbers, being noticed, and quick results, then product managers might feel forced to act in ways that don’t match what their team actually needs. It’s like there’s a conflict between wanting to look good to others and actually doing what’s best for the team. In places like this, the quiet but important skills like understanding people, being patient, and working behind the scenes usually get ignored, while louder, more obvious signs of progress get all the attention. This isn’t just hard for the product manager, it can also make the team less happy and less creative because people can tell when the leader focuses more on appearances than on truly listening. So, it makes me wonder not only how individual product managers can handle this tough balancing act but also what companies can do to encourage leaders who are patient, thoughtful, and supportive. If companies don’t change how they think about leadership, then product management could end up feeling more like checking off boxes than building something great with the team. Therefore, I want to ask the author, can a PM truly thrive as an adaptive, trust-centered leader if the company rewards visible outputs over subtle influence?
