Why Influence Is the Only Skill That Actually Matters
Somebody told me early in my career that I owned my project.
Owned it. Like it was mine.
Like I could make decisions, adjust budgets on the fly, tell
people what to do, and hold the team accountable because—hey—it's my project.
Let me tell you what I actually owned:
The blame. When things went wrong, I owned that.
Here's the reality of project management that nobody puts in
the job description:
- The
people don't report to me
- It's
not my money
- It
wasn't my idea
- I
don't set the timeline
- I
don't control the strategy
And yet somehow, when the project goes sideways, everybody
looks at the PM and says, "Why didn't you see this coming?"
That's the contradiction at the heart of our profession.
And it's exactly why influence is the number one skill you need to develop.
Not scheduling. Not risk management. Not Agile
certification.
Influence.
You Can't Make Anyone Do Anything
Let me be really clear about something:
As a project manager, you cannot make anyone do anything.
You can't make your team work faster. You can't make your
sponsor change the date. You can't make your executive adjust the budget. You
can't make your stakeholders show up prepared.
All you can do is influence the outcome.
Here's how I describe our actual job: We increase the percentage
chance of hitting a date or budget by doing analysis, building plans,
framing decisions, and then influencing whoever we're speaking with—team,
sponsor, executive, customer—toward the outcome the project needs.
PMs operate in the influence space between silos.
We're the connective tissue. We're the translators. We're
the ones standing between engineering's reality and the sponsor's dream, trying
to close the gap without anyone getting hurt.
That's not authority. That's influence. And they require
completely different skill sets.
The Three Currencies of Influence
If you haven't read Cialdini's Influence: The
Science and Practice of Persuasion, go get it today. It feels like a sales
and marketing book. But think about what we do every day:
- Selling
a position to move a date
- Marketing
the case for a budget adjustment
- Persuading
a skeptical stakeholder to trust the process
We are in sales. We just don't call it that.
From my experience, PMs work primarily in three influence
currencies:
1. Credibility
People trust your judgment because you've earned it.
Not because of your title. Not because of your
certification. Because of your track record, your preparation, your
follow-through.
Credibility is the currency you build over time. And it's
the one that gets spent fastest when you overpromise, underdeliver, or show up
unprepared.
2. Reciprocity
You help others achieve their goals—and they help you
achieve yours.
I think this is the most powerful influence lever PMs have
access to. When you go to bat for someone, cover for them, solve a problem
before they ask, create opportunities for them to shine—you build something
that no org chart can give you.
Real influence is banked through real acts of service.
One important note though: Don't explicitly remind people of
what you did for them and then ask for something back. I'll come back to
this—Claude made this mistake in our live demo, and it's worth discussing.
3. Vision
You paint a picture of success so compelling that
people want to contribute.
This is why we develop dream statements, mantras, and team
motivation stories. We covered this in Episode 1. The reason I invest so
heavily in clarifying the why behind every project is because
people don't get inspired by Gantt charts.
They get inspired by a destination they believe in.
When they can see the win—when they can feel what success
looks like—influence becomes almost effortless.
Three Common Influence Mistakes (That Kill Your
Credibility)
1. Over-Relying on Logic
You build the perfect case. The math is airtight. The risk
analysis is complete. You walk into the meeting absolutely certain that any
reasonable person will see it your way.
And then the sponsor says, "We're making that date no
matter what."
Logic without emotional intelligence isn't influence. It's a
monologue.
2. Positional Pleading
"The CEO said so." "This is what the
executive team wants." "I have authorization from leadership."
That's not influence. That's borrowed authority. And it
erodes trust every time you use it, because people know you're not actually
speaking for yourself.
3. Passive Aggressive Escalation
"I guess I'll just have to escalate this to the
executive team." "I'll let them know we're going to miss the
date."
This is an influence killer. Nobody rallies around a PM who
threatens escalation. They shut down, get defensive, and you lose the
relationship.
Real influence doesn't require threats. It creates
alignment.
The DISC Secret Weapon
Here's something that transformed how I communicate with
stakeholders:
One message. Four different ways to say it.
DISC is a behavioral assessment framework with four
communication styles:
- High
D (Dominant): Bullet points, get to the point fast, no fluff
- High
I (Influential): People-focused, enthusiastic, what's exciting
about this?
- High
S (Steady): Change-resistant, needs context, what's the impact on
the team?
- High
C (Conscientious): Data-driven, detail-oriented, show me the
facts
If you bring a five-paragraph explanation to a High D, they
check out at sentence two.
If you lead with data and logic for a High S who's worried
about their team, you miss the real concern.
Meeting people where they are isn't manipulation. It's
respect.
And when you combine that with Socratic AI prompting—where
you give the AI context about the stakeholder's style and ask it to help you
craft the message—you unlock something powerful.
The Three Prompts (And What the AI Actually Gave Me)
I ran three influence prompts live using our Social Wishing
app scenario: We need to cut three MVP features—AI recommendations, in-app
messaging, and payment integration—to protect the launch date and save the team
from burnout.
Prompt 1: Influence Network Mapper (Your Non-Negotiable)
What it does: Maps the key influencers and
decision makers, identifies their positions and motivations, recommends
influence tactics for each, and builds you a conversation sequencing strategy.
What I got:
ChatGPT opened with:
"You're not trying to win an argument. You're trying
to align incentives around a shared risk. The hidden risk isn't feature loss.
It's execution failure."
That reframe alone is worth the price of admission.
The sequencing strategy it gave me:
- Engineering
manager first — Meet privately, turn frustration into structured
input. Ask them to quantify velocity trends, estimate burnout risk, and
calculate realistic delivery probability. "I need your help
protecting the team and protecting the date. I don't want this to become
an engineering versus business fight."
- Product
owner second — Pre-align before the CEO meeting. Convert
engineering evidence into risk framing.
- Marketing
director third — Build the narrative that gives the CEO something
to say publicly.
- CEO
last — Walk in with the engineering risk doc, the product owner's
alignment, and the marketing director's framing already in hand.
And then Claude gave me the closing guidance that absolutely
nailed it:
"You're not building consensus. You're building a
sequence of aligned conversations so that by the time you reach the CEO, the
decision feels inevitable rather than contentious. Each conversation should
leave the stakeholder feeling heard—not managed. The goal is that no one walks
into the CEO meeting as a surprise voice of opposition."
That's the playbook. Pre-wire every conversation
so the final meeting is a confirmation, not a confrontation.
Prompt 2: Stakeholder Persuasion Message Crafter
The specific situation: Convincing the executive sponsor—who
loves AI and sees it as a market differentiator—to launch without AI
recommendations.
What the AI gave me:
The core message:
"Launching AI recommendations before the user base
exists to train them guarantees this feature underperforms at the exact moment
it needs to impress the board."
The analogy:
"Netflix didn't launch with a recommendation engine.
They launched with the catalog. The recommendation engine came after they had
enough viewing data to make it work. An AI feature trained on zero user
behavior doesn't differentiate you—it could embarrass you."
And then the strategic opportunity flip:
"A post-launch AI reveal gives you two press moments
instead of one. We launched clean. We proved traction. Now we're releasing AI
1.1 with real usage data. That's a story—not a patch."
ChatGPT offered a different analogy:
"Launching without data-driven AI is like launching
a Tesla without Autopilot enabled."
Both are strong. Both give the sponsor something to say in
the boardroom. Leaders love a reference story that makes their decision
sound precise, not reactive.
Prompt 3: Reciprocity & Coalition Builder
Here's where I want to be honest about the tool
differences—because one of the most valuable things I can do in this series is
show you where AI gets it right and where it gets it wrong.
Claude's suggestion for the engineering manager:
"I backed their QA resource request. Now I need to
go to them first, privately, and name it directly: 'I went to bat for you on
QA. I need you to go to bat for me—and for the team—now.'"
I pushed back on that.
Don't explicitly call out the favor. The moment
you say "I did this for you, now you do this for me," you've turned
reciprocity into a transaction. And the next time you do something generous for
that person, they'll wonder what you're banking it for.
Real reciprocity doesn't need to be verbalized. It should
be felt.
ChatGPT handled it better:
"You backed their QA request. That built trust. What
they want now is team stability and credibility. Help them by making
sustainable scope the official position—not a quiet concern. If you carry the
political weight, they don't have to."
That's the difference. You're not reminding them
of a debt. You're aligning your ask with their interests and removing a burden
from their plate.
That's influence.
The Big Picture
Here's what I want you to take away from this episode:
You'll never have authority over the things that
determine project success. Budget, people, strategy, timeline—none of
it is yours.
But influence? That's entirely within your control.
Map your influence network. Understand what each person
cares about. Sequence your conversations. Build reciprocity through genuine
acts of service. Craft messages that meet people where they are.
And then watch what happens when a PM walks into a final
decision meeting where the outcome is already inevitable.
That's not manipulation. That's masterful leadership.
Your Non-Negotiable Experiment This Week
Use the Influence Network Mapper (Prompt 1)
on a real decision you need to influence this week.
Then have at least one conversation using
the strategy or message AI helps you design.
Here's what I want you to notice:
- Did
mapping the influence network reveal leverage points you hadn't
considered?
- How
did stakeholders respond when the message was framed around their priorities?
- Did
the sequencing strategy change how the final conversation landed?
Because here's the truth: The most effective PMs
I've ever met don't win by being the loudest or the most technically correct.
They win by knowing exactly who to talk to, in what order, with what message.
And now you have a thinking partner that helps you figure
all of that out in minutes.
Next time: The Three R's—Resistance, Revenge,
and Resentment. Why change initiatives fail, what happens when people get
caught in the Three R's, and how to use AI to navigate your way out.
Want these prompts ready to copy/paste? Head
to PMThatWorks.com for
the full library.
Now go map your influence network. The decision is waiting.
— Rick A. Morris
The Prompts (Copy/Paste Ready)
Prompt 1 - Influence Network Mapper
You are an organizational influence strategist and
stakeholder engagement expert.
First, ask me 4–5 questions about the decision I need to
influence, who's involved, what their interests are, and what resistance I
expect.
Then provide an influence strategy answering:
- Who
are the key influencers and decision makers in this situation?
- For
each person, what do they care about, what motivates them, and what
concerns might they have?
- What
is each person's current position? (supporter, neutral, or blocker) and
their level of influence?
- What
influence tactics should I use with each person? (credibility,
reciprocity, vision, data, coalition building)
- What
is my sequencing strategy? Who do I approach first, and how does that set
up the next conversation?
- What
message framing will resonate most with each stakeholder type?
Decision and context: [Enter Context]
Prompt 2 - Stakeholder Persuasion Message Crafter
You are a communication strategist specializing in
persuasive stakeholder messaging.
Ask me 3–4 questions about the stakeholder, the message I
need to deliver, their priorities, and what objections I expect.
Then craft a persuasive message by answering:
- What
is the core message in one sentence?
- What
framing will resonate most with this stakeholder's priorities? (data,
vision, risk mitigation, opportunity)
- What
story or analogy makes the message memorable?
- What
objections will they raise, and how do I preempt them?
- What
ask or call to action do I make, and how do I make it easy for them to say
yes?
Provide the message in an email or conversation script
format.
Stakeholder and situation: [Enter Context]
Prompt 3 - Reciprocity & Coalition Builder
You are a relationship strategist helping PMs build
reciprocity and coalition.
Ask me 3–4 questions about the people I need to influence,
what they care about, and how I've helped or could help them.
Then provide a reciprocity and coalition strategy answering:
- What
have I done (or could I do) to help each stakeholder achieve their goals?
- How do
I frame my ask as aligned with their interests—not just my project needs?
- Who
are the natural allies I should recruit first to build a coalition?
- How do
I leverage early supporters to create momentum with skeptics?
- What
specific conversation should I have this week to build reciprocity and
alignment?
Situation and key people: [Enter Context]
No comments:
Post a Comment