How Did “Influence Without Authority” Become the PM Leadership Model?
Influence without authority. It shows up in every PM training program and leadership course you can find. But nobody dreamed it up as a goal. Someone looked at the PM role, noticed it carried no positional power, and offered a workaround: here’s how to get things done anyway.
That was fine for a while.
But as I argued in my last issue, the standard is shifting. The project managers who survive (and thrive) will own value delivery, not just scope. The response to that issue was strong. But one question kept surfacing in my inbox:
If we’re going to expect PMs to protect the business case, hold them accountable for maximization of benefits, and ask them to guide projects toward value “worth the effort and expense…shouldn’t they have some power?
It’s a good question, and one I’ve been noodling for the better part of a year. Let’s dive in.
What Happens When You Ask Coordinators to Think Like Executives?
The PM of the near future reconciles AI outputs with reality on the ground, weighs data against evolving business realities, and earns executive trust through decision-making. (ICYMI, I also explored this shift in the last issue).
PMI’s 2025 Pulse of the Profession report—based on a survey of over 5,000 project professionals across industries—frames it as a shift from “tactical troubleshooters” to “strategic value creators.”
PMI’s MORE framework goes further: the “O” stands for “Own project success beyond project management success.”
Own. Beyond execution and delivery.
But the org chart hasn’t moved. PMs still report to functional managers or PMOs in most organizations. They still don’t set budgets or define strategy. Many don’t see the business case until the project is already in flight (if they see it at all). And they definitely aren’t empowered to make the kinds of speedy decisions that protect projects from schedule bloat.
And now, the profession has upgraded the mandate without upgrading the structural support.
“Influence without authority” was fine for the version of the role that was primarily coordinative. You didn’t need positional power to run a meeting or produce a status report. But when the role requires protecting the business case, guiding a project toward value, making sense of what AI produces—influence alone isn’t enough. You need access. And I think, eventually, you need authority.
Do PMs Need More Authority—Or Just More Access?
I think this is a “for now” versus “where we’re heading” question.
Right now, access is the table-stakes fix. Organizations that aren’t doing this (or headed there) are putting their projects at significant risk. Here’s what it looks like:
Let PMs see the business case.
Heck, let them help build it. Rely on them to understand the investment thesis behind the project…and protect it. Most organizations could do this tomorrow. The fact that they don’t tells you something about how the org still sees the role.
I recently wrote two fictional scenarios for a course called Think Like a CEO, each illustrating a plausible 2030 future.
In one, a PM named Priya is running ROI analyses based on risk sensitivity, vibe-coding prototypes for clearer stakeholder communication, evaluating the merit of suggested changes, and making decisions that protect the P&L. While under the oversight of an executive, her role looks a lot like the PM-BA convergence I’ve written about before—and it’s closer to a Director role than an entry-level position. To do that job, Priya needs access to the business case, to the sponsor’s priorities, to the investment thesis. Without it, she can’t do the job.
In the second scenario, a PM named Marcus has moved into a portfolio management role overseeing four related capital projects. He’s making sequencing decisions to maximize returns, modeling out probabilities based on risks, and communicating directly with leaders across the organization to understand gaps between what AI reflects and what is actually happening.
He’s more tactical than an executive, but he’s also making decisions with P&L impact. If you’re going to hold someone accountable for that kind of judgment, they need the authority that goes with it.
Access is the minimum for where we are now.
If I’m right, authority is what the role will require in the future.
The distinction matters: access means PMs see the business case, sit in sponsor meetings, and understand the investment thesis. Authority means they make decisions with P&L impact—and the org chart reflects it.
As the title “Project Manager” gives way to “Portfolio Manager” in more organizations, the structural support has to follow.
The Skills PMs Will Need by 2030 Look a Lot Like a CEO’s
After the class read both scenarios, I asked them to list the skills a PM would need to succeed in either version of the future. Financial modeling. Strategic communication to C-suite stakeholders. Risk-based decision-making under uncertainty. Evaluating AI outputs and knowing when to trust them.
The list looked a lot like what you’d expect from someone running a business.
If the role requires executive ability, a model built for coordinators can’t carry the weight.
“Influence without authority” was designed for someone who needed to get a stakeholder to return a phone call.
It wasn’t designed for someone making portfolio-level investment recommendations to an SVP.
The Authority Gap Is Comfortable—and That’s a Problem
A lot of PMs don’t want more authority.
I’ve heard it. Twenty-year veterans worried about how fast the role is shifting. People who chose this career because they’re good at organizing and orchestrating. The “organizer-in-chief” identity runs deep, and for many PMs, the shift toward strategic judgment feels like someone moved the finish line while they were still running.
And accountability without authority, uncomfortable as it is, comes with a built-in shield. If the project fails, you can point to every decision you couldn’t make, every meeting you weren’t invited to. The authority gap gives you a ready explanation for every bad outcome.
Organizations have their own reasons to keep things as they are, too. Giving PMs real authority means restructuring reporting lines and rethinking who’s in the room when strategy gets set.
In most matrixed organizations—the kind you find across financial services, healthcare, and manufacturing—it’s easier to write “strategic value creator” in a job description than to redesign the org to support it.
So both sides have reasons to leave the model intact. And in the meantime, the profession keeps asking people to be accountable for outcomes inside structures that were designed for coordination.
Influence is an essential skill.
But a philosophy built to work around a limitation can’t survive once the role outgrows it.
And the role is outgrowing itself fast.
If You Only Do One Thing
Here’s the next step. Pick one PM on your team and ask:
“What would you do differently on this project if you had the authority to act on what you’re seeing?”
If the answer surprises you, that’s worth paying attention to.
The gap between what your PMs see and what they’re empowered to do about it is costing you more than you think.
Save and Share!
The last issue asked whether PMs should own value delivery. This one asks whether organizations are designed to let them. If you found this useful, forward it to someone who designs PM roles (or sits in one). Then, subscribe to get the next issue!