Pushing back on unrealistic sponsor expectations is one of the first skills a project manager learns. A decade in, it can feel like the whole job. But when a whole PMO decides that sponsors are the problem, learned helplessness pushes PMs right back into the Coordinator roles they say they don’t want.
When I first started teaching PM fundamentals classes to PMOs more than a decade ago, about 2% of the deck was dedicated to questions like: “What if my sponsor has forced me into a fixed end date before I’ve planned the project?”
Each year since, I’ve adapted the material to the real questions people ask. And each year, that 2% has ballooned. The more industries and companies I work with, the less I talk about RACIs, logs, and registers. Instead, I’m talking about how to “influence without authority” — which is usually code for the question underneath it: What do I do about my sponsor?
It’s an important conversation. But I think your PMO is ready for a different one. Why do your PMs arrive at that question already certain the sponsor is the problem? And what is that certainty costing you?
Let’s start here: the frustration is earned
When I first started helping organizations improve their PM capabilities, it was rare — incredibly rare — that project managers were in the room when business cases were built, charters were written, and schedule and budget assumptions were made.
Early PM participation is much more common now, but for many, it’s too little too late. Project managers have been backed into a corner so often that even when included, they suspect their presence is honorary. They’re in the room, but they don’t think they have the standing to substantively push back on assumptions.
So they don’t.
And the project gets underway with a sponsor who lays down delivery targets as edicts and obsessively monitors progress, without slowing down to understand what makes the work complicated (or complex) to execute.
I had to laugh when, in 2018, PMI published a Pulse of the Profession noting that inadequate sponsor support was the primary cause of failed projects in one in four organizations. Organizations where more than 80% of projects had actively engaged sponsors reported 40% more successful projects than those where fewer than half did.
When I read that research to PMs and PMO leaders, I must have heard two dozen times: “Please don’t show that to my sponsor.”
“We don’t have time to do this right. But we do have money to build it twice.”
Look, there are great sponsors out there — the kind who listen when key assumptions are invalidated. And there are PMs who’ve earned the credibility (or are persuasive enough) to right the ship before it leaves port.
>But both those scenarios (the sponsor who listens, the PM who pushes back) assume one thing: the project manager has the real knowledge, and the sponsor’s job is to listen.
That’s only true some of the time. Sometimes, the sponsor is right. The project really can be done in six months. And sometimes the sponsor has to be right — not because of their authority, but because their job is to land a strategic objective that hinges on being first to market, recognizing revenue sooner, plugging a compliance gap before fines hit, or getting AI tools in place before “shadow AI” starts leaking company secrets.
When your PMs can’t see this — when they’re arguing about what’s unrealistic instead of what would have to be true to hit the objective — they look like an obstacle, not a strategic partner. And when your PMO doesn’t coach the difference, the whole function looks like a coordinating body rather than an accelerator.
A PM told me recently that her sponsor, years ago, literally said to her: “We don’t have time to do it right. We do have money to build it twice.”
It’s tempting to read that line as a confession. (In her case, knowing the players, it probably was.)
But just for a moment, read it as a strategy instead. If being first to market is worth more than the cost of rework, building it twice is a rational bet. The first release gets something workable but imperfect (maybe really imperfect) into the world. The second cleans up the mess. The value of speed, in that case, beats the value of getting it right the first time.
Project managers tend to optimize for clean, quality delivery. Sponsors tend to optimize for a strategic imperative. Both can be right inside their own frame, and much of the animosity I see comes from each side mistaking a role difference for the other side being wrong.
It’s the same collision whether the fight is about the date, the scope, the budget, or the quality bar. The PM is protecting the work, the sponsor is protecting the outcome.
When “realism” is really resignation
When a team keeps running into a sponsor’s competing drivers, it can go a few ways.
Ideally, the project manager navigates the tension between the strategic imperative and a workable plan. That takes courage, finesse, and business acumen — business acumen too few project managers have, according to this PMI report.
But more often, the PM does one of two things. They wear armor into every meeting, ready for a fight about unrealistic expectations. Or they go quiet and hunker down, coordinating the plan the sponsor wants instead of shaping the one the project needs.
Here’s the part that’s easy to miss: both of those look like realism from the outside. “You don’t understand, the sponsor won’t listen.” “We’ve tried, it never changes.” “I’m just being realistic about what’s possible here.” Said once, about one sponsor, that’s judgment. Said as a settled belief about every sponsor, it’s something else — it’s resignation that has learned to describe itself as experience.
The tell is whether the belief is still testable. Realism updates when the facts change. Resignation has already decided how the story ends, so it stops looking for the levers that might change it. That’s learned helplessness in a more respectable outfit — and it’s contagious. One PM who’s given up is a performance conversation. A whole PMO that’s given up is a culture.
And that culture is the real cost. An entire function of PMs who are either adversarial or passive is not the PMO you want anywhere near your most important strategic work. With coordination-only PMOs already an expiring breed, that’s a perception you can’t afford.
What if we hit the sponsor’s date — and it worked?
So how do you unhook your team from thedefault belief that the sponsor is wrong and the PM is right — long enough to see where they might be wrong, the levers they can actually pull, and a path that balances the strategic imperative with delivery reality?
There’s a technique I think works for this. Gary Klein gave us the premortem almost twenty years ago: before kickoff, imagine the project has failed spectacularly, then explain why. It works because it gives pessimism a respectable seat at the planning table.
Run it in reverse.
Imagine it’s three months after delivery. The project was a wild success. You hit the sponsor’s deadline, nobody worked themselves into the ground to do it, and stakeholders feel it was well worth the effort and expense. How did you pull it off?
Have the team brainstorm in three buckets:
- Sponsor assumptions that turned out to be true.
- Risks that never materialized — or that the team mitigated up front.
- Concessions the team negotiated with the sponsor early.
Then turn each bucket into a decision:
- Assumptions: Which ones really could be true, and how would you validate them? Which are false for sure, and can go back to the sponsor with evidence?
- Risks: Which can you realistically mitigate up front, and what would that take?
- Concessions: Which are worth asking for — and do you have what you need to make the ask persuasively?
The brainstorm gives you raw material; the second pass turns it into a game plan. It can be a team activity, or something the PM chases down personally, pulling people in as needed.
Done in good faith — and not as a fancier way to conclude the sponsor was wrong — this gives a team a real path to negotiate between constraints that looked immovable. But it only works if the PMO can coach collaboration. If it can’t, I worry the PMO is authoring its own decline.
If You Only Do One Thing
Pilot the reverse premortem with your PMs. Pick one active project where the sponsor’s constraints feel immovable, and put more than one PM in the room. This is a muscle the whole team needs, not a solo move. Set one ground rule before you start: the session only counts if it produces something actionable — an assumption to validate, a risk to mitigate up front, a concession worth asking for. “The sponsor was wrong” is not an allowed conclusion. You’re not running it to prove the date is impossible. You’re running it to find the version where you hit it, however improbable, because it’s the perspective needed to lead the tension instead of bracing against it.