George from 🕹prodmgmt.world Profile picture
Jan 9 15 tweets 3 min read Read on X
Engineers-turned-PMs keep making the same fatal mistake in stakeholder meetings:

They think logic will save them.

After mentoring a few folks, I've noticed a pattern no one talks about:
2/
If you bend too much or too lite, you lose influence.

Here's the painful truth about stakeholder resistance:

Your stakeholders aren't fighting your logic.

They're protecting themselves from threats you don't even see.
3/
When a VP says "We don't have resources," they're really saying "I have commitments I'm terrified of missing."

The instant you start defending your solution, you've already lost the game.
4/
Your beautiful charts showing user demand trigger their organizational trauma.

They've seen perfectly logical projects destroy quarterly targets before.

Worse yet - if you don’t even have the data, but you need some work done by internal teams.
5/
Let me show you how this plays out:

Junior PM: "Our data shows users desperately want this feature."

Stakeholder: "We don't have resources."

PM: [clutching their user research] "But the ROI..."

Game over. Trust destroyed.
6/
Here's how veteran PMs handle the exact same moment:

"Before I share the feature proposal, could you help me understand what your team is committed to this quarter?"

This isn't just being polite. You've just activated what negotiation experts call tactical empathy.
7/
The magic happens in what comes next:

"What I'm hearing is resource predictability is crucial. Would it be helpful to see how this feature might actually help your team deliver on existing commitments?"

You've transformed opposition into exploration.
8/
An even deadlier scenario:

The drive-by feature request.

Picture this:

Stakeholder: "Our top customer needs X feature by Q4"
PM: "That's not on our roadmap..."
Stakeholder: "This is a million-dollar account"

Your product vision just collided with revenue reality.
9/
Here's the counterintuitive approach that changes everything:

"I appreciate you bringing this to my attention. To ensure I understand the full context, could we schedule 30 minutes to dive deeper into the customer's needs?"
10/
This response leverages what negotiation experts call going to the balcony - creating space between stimulus and response.

But here's what you do in those 30 minutes that changes the game:
11/
You don't prepare a defense of your roadmap.

Instead, analyze similar requests from other top accounts.

Look for the underlying pattern that everyone else is missing.
12/
When you return, you've transformed a tactical feature request into a strategic opportunity:

"I've analyzed feedback from our top 10 accounts. They're all asking for variations of the same capability. Here's what I think is really happening..."
13/
Suddenly you're not the PM defending their roadmap.

You're the strategic leader identifying market patterns.

That senior PM in the corner? Now they're nodding.

This is how you build strategic capital - the ability to influence outcomes beyond your formal authority.
14/
One last weapon for your arsenal:

When stakeholders say "Just make it happen", respond with "Help me understand what trade-offs you're comfortable with. Here are the three options I see..."

You've redirected push-back into problem-solving.
I hope you've found this thread helpful.

Follow me @nurijanian for more.

Like/Repost the quote below if you can:

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with George from 🕹prodmgmt.world

George from 🕹prodmgmt.world Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @nurijanian

Jan 9
Product management has no clear progression, endless responsibilities, constant judgment calls.

That impostor feeling isn't a sign of inadequacy.

It's a sign you need a different learning system.

A thread on rebuilding confidence through systematic competence 💫
Reality check for product leaders first:

When your PM seems stuck in analysis paralysis or seeking endless consensus, they're not being risk-averse.

They're missing the systematic approach to building judgment.
Here's what's actually happening in your PM's mind:

"Everyone else seems to know what they're doing"
"I should already know how to do this"
"My background isn't right for this role"
"I'm going to get found out"

Sound familiar? Let's break this cycle.
Read 12 tweets
Jan 5
5 years ago, I was a PM with zero confidence.

Someone recommended "The Six Pillars of Self-Esteem" by Nathaniel Branden.

It changed everything about how I approach life.

Here's what actually works for building genuine product confidence ↓ Image
1/ Most PMs try to build confidence through Faking it

The hard truth:

All that, even if you get some validation, goes into an endless pit with no bottom.

Real confidence comes from developing self efficacy - that feeling that “whatever happens, I will figure it out.”
2/ There are 6 pillars, but I’ll focus on 3 that I find most useful for Product people

• Living consciously (facing reality, not wishful thinking)
• Taking responsibility (owning decisions, not deflecting)
• Acting with integrity (doing what you think is right) Image
Read 12 tweets
Dec 27, 2024
The "start with the problem" crowd is going to hate this.

But sometimes executives hand you the solution first.

And if you try to fight it, you've already lost.

Here’s how to win as a PM:
1/ typical advice isn't helping:
"resist quick fixes!"
"do thorough research!"
"focus on the problem first!"

real situation:
CEO: "competitors have mobile apps by Q3."
VP: "enterprise clients want mobile."
sales: "we're losing deals without it."

what's next?
2/
Your job isn't to prove others wrong but to enhance the vision with reality.

Real story:
PM: "We shadowed sales meetings instead of debating mobile."
Result: Found customers needed offline access more.
Win: Built offline-first; mobile became easier.
Read 12 tweets
Dec 25, 2024
Most people read strategy advice backwards.

They look at the final, polished rules and try to copy them.

But clarity comes from a deeper process.

Let's see if I can show you how to reverse engineer how smart strategists actually develop this clarity 🔍 Image
First principle: Clear strategy emerges from painful experience.

This Russian PE firm didn't start with perfect rules.

They likely:
1. Lost money to mafia-connected businesses
2. Saw competitors fail in unfamiliar industries
3. Watched others chase massive but hollow opportunitiesImage
Key insight: Strategic clarity comes from pattern-matching across failures.

I made this mistake as a PM. Started with vague rules like:

"Launch fast"
"Get user feedback"
"Be data-driven"
Read 11 tweets
Dec 24, 2024
PM advice: "Track user patterns!"

Cool. But HOW?

After years of fumbling through this myself and mentoring new PMs, let’s see if I can break this down into actionable steps, starting with: 👇 Image
1. Usage Patterns 📊

Drop-offs in flows:
• Set up funnel tracking (GA/Amplitude/Mixpanel)
• Track each step completion %
• Look for >20% drops between steps
• Record device/browser/time
• Tag user segments
Most overlooked drop-off signals:
• Time between steps (hesitation)
• Return visits to same step
• Help doc views mid-flow
• Support contacts during flow
• Session restarts
Read 35 tweets
Dec 22, 2024
The truth about becoming a Platform PM without an engineering background:

Most advice tells you to "learn to code" or "master system design."

I've found a completely different path that actually works.

A thread on what really matters 👇
1/ First, let's bust the biggest myth:

You DON'T need to be an expert in every technical area.

What you DO need:
• Deep expertise in 1-2 specific domains
• Understanding of technical limitations
• Ability to translate between business and tech
2/ The key is picking your technical focus areas wisely.

Common platform domains:
• API design/management
• Cloud infrastructure
• Security/identity
• Data pipelines
• Developer workflows
• Observability

Choose 1-2 based on your product's needs.
Read 11 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(