A recent client told me they were concerned about having a reputation for always saying no.

I felt that in my bones…because that used to be me.

That’s 2015 me chatting with a sales guy weeks after launching Amazon Echo and Alexa.

Echo was growing. Sales were outpacing supply. Roadmap requests were coming at me every day.

I had built high judgment with a habit of quickly rejecting requests that I intuitively knew either wouldn’t work, were unrealistic, or would require tradeoffs that weren’t worth it.

It felt like I was doing the right thing. Fast prioritization, focused on delivering results.

I wasn’t just saying no. I was protecting the plan!

But that's not how it felt to the people around me.

Here’s a direct quote from my key stakeholder:

“There has been a noticeable shift in JG’s tone this year from ‘let me see how I can make happen’ to ‘sorry…we don’t have resources and can’t make it happen’”

That was from a promo doc under “reasons not to promote”.

Don’t ask me how I got my hands on that, okay?

I got promoted anyway and this feedback needed to be acted on right away.

If you've ever been told you're "too rigid" or "hard to work with" on prioritization, you know the sting.

You know the roadmap is right. You know the trade-offs.

But somehow, the person asking for a new feature walks away thinking you just don't get it.

That perception can quietly erode your influence.

So how do you hold the line on priorities without becoming the person everyone avoids?

Here’s what I did and how I coached my client through it:

Flip the script

Most PMs defend their roadmap when challenged.

They explain the rationale. They walk through the constraints. They justify why this is more important than that.

It feels logical. But to the stakeholder, it sounds like: "No, and here's why you're wrong."

The fix isn't to say yes more often.

It's to stop defending and start asking.

The stakeholder-led prioritization technique

When someone requests a new feature or initiative, don't quickly react. Instead:

Show them the current top 2-5 priorities the team is working on
Ask which item they'd remove to make room for their request
If they suggest removing something, ask whether their request would achieve that item's success metrics better
Let them make the case for why their request is the most important thing

That's it. Four steps.

You haven't said no. You haven't even pushed back.

You've simply made the trade-off visible and asked them to do the hard thinking.

Why this works

It removes the "no" from the conversation entirely.

You're not gatekeeping. You're collaborating on what matters most.

It forces real prioritization thinking.

Most people who request features haven't thought about what they'd sacrifice. When you ask, it changes the conversation.

It changes future behavior.

Once stakeholders know you'll ask them to defend the trade-off, they stop coming with half-baked requests. They arrive prepared.

The best PMs don't say no. They make the cost of yes impossible to ignore.

Tie everything to outcomes

This technique works best when your roadmap items are clearly tied to measurable outcomes.

OKRs. Revenue targets. Retention goals.

When someone proposes something new, the question becomes: "Does this get us closer to our agreed targets than what's already planned?"

That shifts the debate from subjective opinion to objective analysis.

No more "I think this is more important" back-and-forth. Just data and outcomes.

I've already shared how a stakeholder map can help you understand who to manage and how.

This technique is the next step: what to do when those stakeholders challenge your priorities.

One more thing: keep a changelog

Here's a small habit that will save you more grief than you'd expect.

Start a simple decision log for roadmap changes.

Every time a priority shifts, write down:

What changed
Why it changed
Who requested it

It takes 30 seconds.

But when someone questions a decision weeks later (and they will), you have the receipts.

No guessing. No defensiveness. Just: "Here's what we agreed, and here's why."

Try this, this week

The next time someone challenges your roadmap, resist the urge to defend.

Instead, show them the priorities and ask: "Which of these would you deprioritize to make room?"

Watch what happens.

Stop being the PM who always says no