Don't be the PM who agrees with everyone

There’s a type of PM who never causes friction. They validate ideas in meetings. They say yes to stakeholder requests. They find something to like in every proposal. Everyone enjoys working with them.

And over time, people stop bringing them the real problems.

It feels collaborative to agree. It feels respectful, supportive, inclusive. But when agreement becomes your default, it stops being a choice - it becomes a habit. And a PM who agrees with everything isn’t helping the team think more clearly. They’re just reflecting back whatever the room already thought.

People notice this faster than you’d expect. Once they clock that you’ll say yes to whatever they bring, they stop bringing you the hard calls. Why would they? They already know the answer.

The PM who agrees with everyone gets liked. They don’t get trusted.

Trust in a PM isn’t built by being easy to work with. It’s built by being honest - even when that’s uncomfortable.

When you push back on an idea, you’re doing something useful. You’re forcing the thinking to get sharper. You’re signalling that your agreement actually means something. When you agree with everything, your agreement doesn’t count for anything.

There’s also a subtler cost. Stakeholders and teammates start filtering what they tell you. They share the polished version, not the messy one with the real doubts still in it. You stop getting early signal. By the time you hear about the problem, it’s already a crisis.

Start small. Pick one meeting this week and decide in advance that you’ll raise at least one genuine concern - not to be difficult, but because something actually doesn’t add up.

Notice how it lands. Most of the time, if you frame it as a question rather than a verdict, people engage rather than defend. But avoid the obvious PM question - “what problem does this solve?” People have a ready answer for that, and if the idea is exciting enough, the answer is just “who cares, it’s a great idea.”

The more useful move is to go with their energy, not against it. Ask what changes if this gets built. Ask what customers can do that they couldn’t do before. Ask what success looks like in six months. These questions are harder to brush off - and they surface whether there’s real substance behind the idea without feeling like a challenge.

Over time, this will build your reputation as a person worth listening to. A person whose opinion means something, because they don’t just give it away.

Pushing back doesn’t mean being combative. You’re not looking for arguments - you’re looking for the best outcome.

Done well, disagreement doesn’t damage relationships. It builds them. People remember the PM who helped them to avoid issues - not the one who said yes, then had to reopen the discussion later when changing course was far more expensive.

That’s a skill - it takes practice. But it starts with accepting that your job isn’t to make everyone feel good about their ideas. It’s to help the team make better decisions.

Product Notes is free and lands every week. Subscribe to get it in your inbox.