I used to think logic would sell my ideas.

I’d do more research than anyone else. I’d build the business case tying every feature to impact. I’d rehearse an amazing pitch that laid it out perfectly. And I’d confidently walk into the room thinking, “This just makes sense. Anyone can see it.”

But then someone would explode before I could get 3 slides into my polished presentation. They would push back hard on something minor that wasn’t even the point of what I was presenting. And now the room is focused on something else entirely, and I’m standing there thinking, “Where is this coming from? What is happening?!”

It took me years to figure out that it had nothing to do with the quality of my thinking. It had everything to do with a system I couldn’t see (yet).

Every organization has two operating models

There’s the one that’s spoken aloud in the town halls. The intangible OKRs and stretch goals. The mission statement that tells us nothing. The values posters in the conference room.

Then there’s the real one. The one where people optimize for survival rather than strategy.

Your VP of Engineering pushes back on your roadmap because their bonus is tied to uptime, not new features. Your operations stakeholder kills your “efficiency” proposal because the last person who took a big swing in that area got fired. Your product council rubber-stamps anything from the revenue team and yet scrutinizes everything from the platform team.

None of this is written down anywhere, and it not only decides what gets built but also who gets ahead.

The pattern is the same nearly everywhere - companies big and small, product or services, B2B or B2C. The product managers who get stuck are rarely less talented or illogical. It’s that they’re less aware of what’s actually driving decisions around them. They’re arguing with data when the real obstacles are fear, hidden incentives, or political capital they haven’t figured out yet.

They can feel it around them but can’t quite articulate it.

The question that uncovers the system

I started asking a question that I stole from my product discovery questions that makes those things we feel become visible as well.

“What would your boss’s boss have to do to get fired?”

And also the reverse: what would they have done well to get promoted?

People don’t always know the OKRs cascaded down through the company. But they know the gossip. They understand what people care about through their words, their actions, and the things that make them visibly uncomfortable in meetings.

I had been using this technique when interviewing customers who didn’t have clear goals and realized it worked with my organization as well. Sure enough, when I started looking at every stakeholder through this lens, I could see what mattered most to them and adjusted my approach accordingly.

This isn’t cynicism. It’s pattern recognition. When you know that your VP cares about customer retention because their predecessor got fired over churn numbers, you stop pitching features as “innovation” and start pitching them as “retention insurance.” Same feature, very different effect.

How one PM spent three months arguing with data

I coached a PM at Amazon who had spent three months trying to get a simple multilingual feature approved, but her manager kept blocking it. The data was there for a logical decision: 600 feature request upvotes, user survey results, and the engineering effort was straightforward.

Yet nothing moved, no matter how logical the case was.

So we dug into the incentive system. Her manager was focused on internal productivity - that was his track record. That’s what he was known for, but this feature was meant to help external-facing teams and customers directly. To him, customer-facing work felt like risky, unfamiliar territory. It wasn’t that he disagreed with the data or logic. It was that his brand, what had led to his success thus far, was attached to internal efficiencies, and this was too far outside of that model for him. Fear. Unfamiliarity. Off-brand (inconsistent with identity).

She needed to flip those emotions around by reframing the idea: position the feature as a revenue-enabling extension of internal productivity, not as a customer request. Same feature, very different effect. She had spent three months arguing the data when the right framing could have shortened that to weeks.

Why this keeps happening

PMs are trained to build business cases: Quantify the opportunity. Show the ROI. Present the data.

All of that assumes your audience is a rational actor, making decisions based only on factual information and in the best interest of the customer and the company.

Spoiler alert: they’re not.

They’re a human being making decisions based on career risk, relationship dynamics, and what happened the last time someone in their position took a similar stance. (and those are just the fear-based motivations!)

Organizations like these are not the exceptions; it’s how most actually work - incentive systems invisible to the people inside and discovered only after the employee becomes too bitter or tired to do anything about it. The PM who doesn’t see the system keeps trying harder with better data and burning out in the process, but the PM who sees the system can use it to their advantage - for their customers, their company, and their careers.

How to map the incentive system around you

You don’t need a consultant or a 360 review app. You need conversations, observation, and curiosity.

Start with 1-on-1s. Sit down with one stakeholder at a time, 30 minutes requested max. Ask a specific question about a specific topic. DO NOT ask to “pick their brain” or just chat. That’s a signal the conversation will be a waste of time for them.

Instead, say something like, “I’m trying to understand how decisions get made about [their area of expertise]. I heard you know a lot here.” (Flattery goes a long way, but make it subtle.) Then let them talk. At the end: “Who else should I talk to about this (or different topic)?”

Then they refer you, either with a warm introduction, or you reference their name. This way you carry their credibility into the next conversation, which makes it easier to get in and get better information. Within a month, you’ve met 10-15 people and built relationships before you ever need to ask for support in a tense meeting.

For every stakeholder you work with regularly, answer two questions: What would their boss have to do to get fired? What would their boss have to do to get promoted? The answers tell you what your stakeholder is optimizing for, even if they can’t articulate it themselves.

And when you present a proposal and someone pushes back, stop focusing on what they said. Focus on what triggered the emotion. Was it the budget number? The timeline? The word “risk”? The fact that it touches another team’s territory? The trigger tells you what they’re protecting, even if it’s just their ego.

Then test your map with something small before you bet big on it. Frame an idea using the incentive language you’ve identified and run it by them. If the response is positive, your map is working. If not, you need more data either from them or their peer.

The real skill gap

Your product skill doesn’t matter much if you can’t read the audience you’re presenting to in advance.

I’ve watched PMs with strong analytical skills and solid product instincts get stuck for years. They keep building better decks, running more analyses, and adding more data points. And yet the same proposals keep dying as the same stakeholders talk over them in meetings.

The ones who break free stop asking “why don’t they agree with my logic?” and start asking “what are they really considering that they’re not saying?” While some call it a “soft skill,” it’s really a core of business acumen for product managers: translating your product work into language the audience cares about.

Map the hidden incentives first. Then the roadmap and positioning come after.

So here’s what I’d try this week: Pick one stakeholder who has pushed back on something recently. Don’t go back with more data. Instead, have a 30-minute conversation with someone who works closely with that stakeholder. Ask: “What do they keep harping on with their team? What are they being measured on? What happened the last time their team took a big swing?”

The new knowledge won’t show up as words in your deck exactly, but it will change how you pitch the next one.

-Brennan