Informal authority runs quietly underneath every org chart. How to spot it, how to read it, and why formalizing it always backfires.
Today, we will continue talking about the important role of managing stakeholders in your project.
So, you looked at the project, you found the quiet stakeholder, and you started the conversations early. Good. That already puts you ahead of most.
And then one day, a decision everyone had agreed on quietly comes undone. Nobody on your list changed their mind. The sign-offs are all still there. But something shifted, and you can't quite trace where.
Let me tell you where...
There was a person you never talked to. Their name isn't on the RACI chart. They don't sit on your steering committee. On paper, they have nothing to do with your project. And yet, somehow, three of the people who do matter all checked with this person before they committed to anything.
That is informal authority. And it runs almost every organization quietly, underneath the official one. You know this person. Maybe it's a senior engineer with no management title, but fifteen years in the building and a memory of why the last three versions of your idea failed. Maybe it's the person whose desk everyone stops at on the way to the coffee machine. Maybe it's someone in a completely different team whose blessing, for reasons nobody ever wrote down, simply matters.
They're not on any chart. But when they think something is a bad idea, people listen. Not because they have to. Because they trust this person more than they trust the org chart.
The org chart shows you who reports to whom. It tells you almost nothing about who trusts whom.
And projects don't move on reporting lines. They move on trust lines.
You can have every formal approval in place and still watch a project stall for weeks, for reasons nobody can name, because one person who was never in the room had a quiet doubt.
So how do you find them?
First of all... You watch! Observation is also a Project Management skill. A quite of skill that does not appear in certification programs.
You notice who people glance at before they answer a hard question. You listen for the phrase "let me just check with someone first," and you pay attention to who that someone is. You notice whose name keeps coming up when you weren't the one who brought it up. Informal authority is rarely loud. It doesn't need to be. The influence does the talking.
There's a simple test I use. When I float an early idea, I watch the room for a half-second pause before people respond. That pause usually means someone is mentally checking the idea against what a third person, who isn't there, would think. Find out who that third person is. That's your real stakeholder.
Now, here is the part most people get wrong. Once they finally spot this person, they try to make it official. They put them on the stakeholder map. They give them a role, a title in the project, and a recurring meeting. And it backfires every time.
Because the moment you formalize informal authority, you kill the thing that made it work. Their power was never positional. It was relational. The second you turn it into a box on a chart, it stops being trust and starts being process. And process is exactly what these people are trusted to see through.
So you do the opposite. You bring them in the way their influence already flows. Quietly. Early. Informally.
A coffee, not a calendar invite. A "I'd really value your read on this before I take it any further." You're not asking for a sign-off. You're asking for an honest take, and you're signaling something underneath the question. That you see how things actually work here. That you know the real map isn't the one HR drew.
That signal matters more than the input itself. People with informal authority earned it partly by paying attention to who respects the real dynamics and who only respects the formal ones.
When you come to them with genuine curiosity instead of a checklist, you're telling them which kind of project manager you are. And that tends to come back to you later, in a meeting you're not even in, when your idea comes up and the quiet doubt doesn't.
There's a risk here, and it's worth naming. Informal authority can be a wonderful thing or a quietly destructive one. The same person who can carry your project can also sink it from outside the room, with no accountability, because none of this is written down anywhere. Your job is not to neutralize them. It's to understand them. To know what they care about, what they've seen go wrong before, and what would make them an ally instead of a silent veto.
Most of the time, they want the same thing the quiet stakeholder wanted in the first place. To be seen. To be asked. To not find out about something important after everyone else already has.
The truth is, every project runs on two maps. There's the official one, with its roles and approvals and reporting lines. And there's the real one, the web of trust and history and quiet influence that actually decides what happens. The first map is handed to you. The second one, you have to draw yourself, slowly, by paying attention.
Most project managers only ever read the first map. The good ones learn to read in the second.
So before your next decision, ask yourself one quiet question.
Who is the person everyone checks with before they say yes, and have you ever actually talked to them?
Posted on: July 27, 2026 01:00 AM |
Permalink
