the most underrated pm skill isn't what you think. after 7 years...

the most underrated pm skill isn't what you think.

after 7 years helping hundreds of product leaders, i've seen one capability consistently separate exceptional pms from merely good ones.

it's not roadmapping. not prioritization. not customer research.

it's tactical empathy. ↓

tactical empathy goes far beyond basic "understanding users."

it's systematically mapping & navigating the hidden motivations, fears & constraints of every stakeholder in your ecosystem.

it's why some pms get things done with seemingly magical ease while others hit invisible walls.

think of tactical empathy as your organizational superpower.

most pms treat resistance as an obstacle. exceptional pms see it as valuable data.

"that exec keeps pushing back on my roadmap" becomes "what underlying pressure is causing that reaction?"

this isn't manipulation or politics.

tactical empathy is authentically understanding perspectives to create better outcomes for everyone.

technical pms especially struggle here - thinking logic & data should be enough to drive decisions.

i made this mistake for years.

tactical empathy in action:

- engineers resist your feature → uncover the hidden technical debt concerns
- design team seems perfectionist → discover the previous failed launch trauma
- execs request seemingly random features → map to unstated business pressures

here's what tactical empathy looks like day-to-day:

1. before every meeting, spend 2 minutes considering each stakeholder's:
- current pressures & priorities
- career incentives
- past experiences with similar projects
- relationship dynamics with others present

2. actively listen for unstated concerns:

- "we need more time" often means "i don't believe in this direction"
- "let's be data-driven" can mean "i don't trust your intuition"
- "seems ambitious" might mean "my team is already overwhelmed"

3. document stakeholder patterns privately:

create a simple map of key players, their typical concerns, communication preferences & what motivates them.

review & update this regularly as you learn more.

this isn't shadowy - it's doing your homework.

4. adapt your communication style:

- engineering: explain the "why" before the "what"
- design: connect to user problems & quality standards
- executives: link to business outcomes & strategic priorities
- sales: highlight competitive advantages & customer wins

5. proactively address unstated concerns:

"i know reliability is top priority right now, so i've detailed how this feature minimizes production risk..."

this signals you understand their world & builds immediate trust.

but wait - i can already hear the objections:

"this sounds like playing politics"
"shouldn't good ideas stand on their own merit?"
"i don't have time for all this relationship management"

let me address each of these: ↓

objection 1: "this sounds like politics"

no. politics is advancing personal interests at others' expense.

tactical empathy is understanding contexts to create better collective outcomes.

it's the difference between manipulation & collaboration.

objection 2: "good ideas should stand on their own"

in theory, yes. in reality, ideas exist in human systems with competing priorities, limited resources & different worldviews.

the best product ideas die daily because pms can't navigate these realities.

objection 3: "i don't have time for relationship management"

you don't have time not to do it.

hours spent building detailed specs mean nothing if key stakeholders block implementation.

tactical empathy isn't extra work - it makes everything else work.

objection 4: "i'm a junior pm, i don't have the influence"

tactical empathy is even more crucial when you lack positional authority.

understanding what drives others gives you influence regardless of your title.

junior pms with this skill advance rapidly.

the career impact of tactical empathy compounds over time:

- short term: less resistance to your ideas
- medium term: faster delivery, bigger scope
- long term: stronger network, reputation as someone who "gets things done"

this is how pms become product leaders.

practical ways to develop tactical empathy:

- conduct "stakeholder interviews" just like user research
- debrief after contentious meetings to identify underlying dynamics
- find mentors who navigate organizational complexity well
- study negotiation & influence (not to manipulate but to understand)

the ai prompts for product work collection also includes specific prompts for stakeholder analysis & detecting underlying concerns in feedback.

using these to complement your natural empathy helps develop this muscle faster.

tiny.cc/ai-prompts

I hope you've found this thread helpful.

Follow me @nurijanian for more.

Like/Repost the quote below if you can:
x.com/99905661006335…