When Leadership Wants the Wrong Thing

It happens on every project. Someone senior — a VP, a director, sometimes the CEO — has a strong opinion about what to build. They’re not wrong because they’re stupid. They’re wrong because they’re too far from the work to see what you see. But they have the authority, and you have the data that says their direction is a mistake.

This is the most political moment in product leadership. And I am, by my own admission, not great at politics.

The Wrong Way to Push Back on Leadership

Early in my career, my approach was simple: present the data, explain why the direction was wrong, and assume the strength of the argument would carry the day. Sometimes it worked. When it didn’t, I was confused — the data was clear, the logic was sound, why wasn’t the decision changing?

Because decisions at the leadership level aren’t purely rational. They’re shaped by commitments made to other leaders, promises to the board, personal reputation, and a dozen political dynamics you don’t see from where you sit. Presenting data that contradicts a VP’s direction isn’t just a logical exercise — it’s a social one.

I learned this the hard way. A VP was pushing a feature that our usage data clearly didn’t support — the kind of pet initiative that gets momentum because a senior person believes in it, not because customers need it. I laid out the data in a room full of their direct reports. Charts, numbers, the full case. Clear and correct and completely tone-deaf. The room went quiet in that particular way that means you’ve made someone lose face in front of their team. We eventually went a different direction — the data won. But that VP stopped returning my messages for three months. I needed their support on the next initiative. I didn’t have it. Being right and being effective aren’t the same thing.

How to Challenge Leadership Without Burning Bridges

Align privately first. Never surprise a senior leader with a challenge in public. If you have data that contradicts their direction, bring it to them one-on-one first. “I’m seeing something in the data that I want your perspective on.” This gives them space to change their mind without losing face.

Frame it as shared risk. Not “you’re wrong” but “I’m worried about the risk we’re taking.” Leaders respond to risk language. They don’t respond well to being told their instinct is bad.

Bring an alternative, not just a critique. “I don’t think Feature X will work” is a dead end. “Here’s what the data says, and here’s what I think would get us to the same outcome with less risk” — that’s a conversation a leader can engage with.

Know when to disagree and commit. Sometimes you’ve made your case, the data is clear, and leadership decides to go the other direction anyway. That happens. In those moments, the professional move is to commit fully to the decision and make it succeed — not to sabotage it by being half-in.

The Line Between Disagreeing and Walking Away

There’s a difference between “leadership wants the wrong feature” and “leadership wants to do something unethical or harmful.” For the first one, disagree respectfully and commit. For the second one, that’s a different conversation entirely and your job is to be the voice of reason regardless of the political cost.

Most of the time it’s the first one. And most of the time, the skill isn’t having the right answer — it’s delivering a hard truth in a way that the person with decision-making authority can actually hear.

Managing Up as an Outside Consultant

As a consultant, this dynamic is amplified. You’re brought in as an expert, but you have less organizational context and less political capital than anyone in the room. If you push too hard, you’re “the consultant who doesn’t understand our culture.” If you don’t push hard enough, you’re “the consultant who just agrees with everyone.”

The balance is the same as it is internally: earn the right to be heard through listening first, then deliver your perspective with honesty and respect. On my last consulting engagement, I spent two weeks building relationships before I brought a difficult finding to the leadership team. When I said “the data suggests your current direction won’t work,” the room didn’t go quiet. The VP leaned forward and said, “OK, what do you think we should do instead?” That’s the version of this I’m still learning to get right.