This post was inspired by a reader’s question.
Reader question: How did you overcome a difficult stakeholder?
It’s a question I get often.
But I want to start by reframing it.I don’t think in terms of “overcoming” people.
I think in terms of reducing friction so the work can move forward.With that in mind, here’s a real example.
A real situation
I once worked on a project where one stakeholder questioned almost every decision.
Scope, timelines, priorities, and even items that had already been agreed on.
From the outside, it could easily be labeled as resistance.
From the inside, it felt like constant pushback that slowed progress and drained energy.
Earlier in my career, I might have reacted defensively or escalated too quickly.
This time, I chose a different approach.
What I noticed
That stakeholder carried significant responsibility if the project failed.
But that responsibility had never been clearly discussed or made visible.
Decisions were happening in meetings, but they were not always documented clearly afterward.
Assumptions were shared verbally and then interpreted differently by different people.
From their perspective, the project likely felt risky and unclear.
That observation changed how I responded.
What I did differently
Instead of reacting to each objection, I focused on making decisions explicit.
I started documenting what had been decided,
what assumptions we were operating under,
what risks we were accepting,
and what tradeoffs we were consciously making.
Not to corner anyone.
Not to win an argument.
But to create shared understanding.
I also slowed conversations down.
Rather than debating everything in real time, I summarized discussions in writing and asked for confirmation.
Something important happened.
Once decisions were visible and ownership was clearer, the pushback reduced significantly.
Not because the stakeholder stopped caring, but because they felt safer.
What I avoided
I didn’t avoid difficult conversations.
I focused on making decisions clear rather than trying to accommodate every perspective at once.
And I avoided framing the situation as “this person is the problem”.
When alignment was still missing, I calmly escalated with facts and context, not emotion.
That approach preserved trust, even when decisions were uncomfortable.
And what if, after all that, they still don’t listen?
This is the part people don’t talk about enough.
Sometimes you do everything right.
You create clarity.
You document decisions.
You escalate appropriately.
And still, nothing changes.
When that happens, it’s important to recognize something difficult but necessary.
Not all problems are project management problems.
In some situations, stakeholders are not missing information.
They are not confused.
They are making a conscious choice.
At that point, the challenge moves beyond communication and into culture, governance, or accountability.
Those are factors a project manager can highlight, but not always fix.
One of the hardest lessons in this role is understanding where your influence ends.
You can do excellent project management work in a system that still fails.
That does not invalidate your approach.
It clarifies your professional boundaries.
What this taught me
Most “difficult stakeholders” are not trying to be difficult.
They are reacting to uncertainty, risk, or lack of clarity.
And sometimes, even when clarity exists, alignment still doesn’t happen.
My role as a project manager is not to force agreement.
It’s to make decisions, risks, and consequences visible, so that the organization can choose consciously.
Final thought
If you’re dealing with a challenging stakeholder, it doesn’t mean you’re failing.
It often means the project needs more clarity, not more pressure.
Rosana Inacio
Project Manager
Leave a Reply