How to Map Power Structures in Any Organization

Most organizations hand you a chart on your first day. Boxes and lines, titles and reporting relationships, the whole tidy picture of who answers to whom. And then, within a few weeks, you notice something strange — the chart is wrong. Not factually wrong, exactly. The names and titles are accurate. But the map is useless for understanding what actually happens.

The person who controls the budget isn't the VP of Finance. The person whose email everyone answers within ten minutes doesn't have a senior title. The executive who looks powerful on paper waits for a nod from a peer before making any real decision. The org chart describes a legal structure. It does not describe where power actually lives.

I've come to think that reading power is one of the most useful skills a person can develop — and one of the most underdiscussed. It's not cynical to do this. It's just honest. And the good news is that in most organizations, the real structure isn't hidden all that deeply. It follows patterns. Once you know what to look for, you can sketch a fairly accurate picture in about thirty minutes.

Here's how.

Why the Org Chart Lies

Before we get to the method, it's worth understanding why the gap exists at all.

Formal authority — the kind that lives in org charts and job descriptions — is assigned. Real power is earned, accumulated, or inherited through things the org chart was never designed to track: relationships, information control, institutional memory, political alliances, and in some cases, just sheer force of personality.

A 2019 analysis by organizational network research firm Humanyze found that roughly 70% of critical work decisions in large companies are influenced by individuals who hold no formal authority over the outcome. The org chart captures the legitimate hierarchy. What it misses is the influence network — which is almost always more predictive of what actually gets done.

The two structures coexist in every organization I've looked at, and the gap between them is where most people get confused, blindsided, or stuck.

The Four Power Sources to Look For

Before you start mapping, you need to know what you're mapping. Power in organizations doesn't come from one place. In my view, it clusters around four distinct sources, and each leaves different observable traces.

Most of the organizational power plays I've observed collapse into combinations of these four. Someone with deep institutional memory but no formal authority is often more influential than a newly hired VP. Someone who controls information flow — who decides what the executive team sees and in what order — can effectively determine decisions without ever being in the room.

The chart gives you formal authority. The other three require observation.

The Thirty-Minute Map: A Step-by-Step Method

This isn't a research project. It's a structured observation exercise. You're not looking for proof — you're looking for patterns. Here's the sequence.

Step 1: Identify the Decision That Recently Surprised You (5 minutes)

Start with an anomaly. Think of a recent decision that seemed to come from an unexpected place — a policy that changed without explanation, a project that got greenlit when everyone expected it to die, a hire that bypassed the obvious candidates.

Anomalies are your entry point. They mark the places where the formal structure and the real structure diverge most visibly. Pick one that feels genuinely puzzling, and use it as your anchor for the rest of the exercise.

If you're new to an organization and don't have an anomaly yet, ask someone who's been there three or more years to name one. They'll have several.

Step 2: Ask the Meeting Question (5 minutes)

Look at the most important recurring meetings — the ones where real decisions get shaped, not just announced. Then ask two questions:

1. Who is always in the room, regardless of whether their title justifies it?
2. Who is conspicuously absent, despite having a title that should put them there?

Presence without justification points to informal power. Absence despite title points to diminished influence — or to someone who has deliberately stepped back because they already have what they need.

Research from MIT's Human Dynamics Lab consistently shows that communication patterns — specifically, who speaks to whom and with what frequency — are more predictive of team performance and organizational influence than role definitions. The meeting room is a visible, real-time expression of that dynamic.

Step 3: Follow the Information (10 minutes)

Power over information is often the most durable form of organizational influence. To trace it, ask:

• Who prepares the briefing documents? (Not who signs off on them — who prepares them.)
• When an executive needs to understand something fast, who do they call?
• Whose summary of a situation becomes the working version everyone adopts?

The person who frames the problem almost always shapes the solution. In my experience, this role is frequently invisible — it's held by a chief of staff, a senior analyst, or a long-tenured project manager who has no direct reports and a title that sounds mid-level. And yet they are filtering, synthesizing, and presenting reality to the people who make formal decisions.

Find the information brokers. They're almost certainly more powerful than their org chart position suggests.

Step 4: Watch What Happens When Someone Needs Something Cross-Functional (5 minutes)

Cross-functional requests — situations where someone needs cooperation from a department they don't control — reveal the relationship network faster than anything else. Watch who gets things done across silos. Do they call in favors? Do people just help them automatically? Is there friction or ease?

When you see someone move effortlessly across departmental lines, you're watching relationship capital in action. A 2020 study published in the Journal of Organizational Behavior found that individuals who bridge structural holes — gaps between otherwise disconnected groups — consistently hold disproportionate influence relative to their formal rank. Bridgers see information others don't, and they're trusted by factions that distrust each other.

The person who can pick up the phone and get the engineering team to reprioritize something without a formal escalation path? That's a power node.

Step 5: Ask Who Was Here Before (5 minutes)

Institutional memory is the least glamorous power source and often the most underestimated. Organizations, especially large ones, accumulate historical context that is held in people's heads rather than in any document. When something goes sideways, who does leadership quietly consult? When a policy question arises that nobody can quite answer, who gets the email?

Tenure alone doesn't confer this. But long-tenured individuals who have developed a reputation for knowing why things are the way they are — not just what the rules say, but the history behind them — carry a quiet authority that can outlast multiple leadership regimes.

Ask someone you trust: who in this organization knows where the bodies are buried? The answer will tell you a lot.

How to Draw the Map

By the time you've worked through those five steps, you have enough raw material to sketch something useful. The map doesn't need to be elaborate. A rough network diagram — nodes for people, lines for influence relationships — is enough. Here's how to weight it:

• Double circle anyone who appears in multiple steps. They're a high-probability power node.
• Dotted line any relationship that runs across formal boundaries (different departments, different levels of hierarchy).
• Mark the information brokers separately — they deserve their own symbol because their power mechanism is different from relationship capital or formal authority.
• Note the anomaly you started with. Does your map now explain it? If yes, you have a working model. If not, you're missing something — usually an information broker you haven't identified yet.

The whole thing should fit on a single page. If it's getting complicated, you're probably adding too much detail too early. The first map is a hypothesis, not a finished picture.

What the Map Is Actually For

A power map isn't a tool for manipulation, and I want to be direct about that. The most useful application isn't "how do I get what I want?" It's "why do things work the way they do here?"

Understanding the real power structure helps you:

• Anticipate resistance — because you can see whose interests a change threatens before you propose it
• Route requests correctly — because you know who actually shapes the decision versus who signs the paperwork
• Calibrate your assumptions — because you stop being confused when the person with the biggest title seems strangely powerless
• Read organizational health — because the gap between the formal structure and the real structure is often a symptom of something worth paying attention to

That last one is worth pausing on. When the two structures are wildly misaligned — when the org chart has almost nothing to do with where power actually sits — that's usually a sign that the formal structure isn't working. Either it was poorly designed, or it's been eroded by years of informal workarounds, or leadership has quietly lost confidence in the people the chart says are in charge. Any of those is a meaningful signal.

The Patterns That Repeat

I've done this kind of mapping across a range of organizations, and a few patterns come up consistently enough to be worth naming.

The Shadow Advisor. Almost every leadership team has one — someone who holds no formal authority but whose opinion the CEO (or equivalent) weights heavily. They may have a functional role that seems unrelated. They often have a long personal history with the leader. Their influence is almost entirely invisible to people outside the inner circle, and it can be decisive.

The Veto Node. Some individuals can't create things, but they can stop things. They've accumulated enough institutional standing — through tenure, relationships, or sheer willingness to dig in — that routing around them costs more than working through them. They're not always senior. They're sometimes mid-level people who've been in the same seat for fifteen years. Their power is almost entirely defensive, but it's real.

The Connector. The person who knows everyone, crosses every silo, and holds no particular agenda of their own. They're often perceived as "political" by people who don't understand what they're actually doing, which is accumulating relationship capital as a primary resource. They get things done through social architecture.

The Stranded Executive. This one is sad to watch. A senior title, a large formal domain, and almost no real influence — because the organization has quietly worked around them. Their directives get nominally accepted and then passively ignored. Their budget exists on paper but never quite deploys as intended. They are usually the last person in the building to know this about themselves.

A Note on Using This Honestly

Mapping power is a form of clarity, and clarity can be used well or badly. The version of this I'd endorse is the one that helps you stop being confused about why things happen, and helps you work more effectively within a system while being honest about what that system is.

The version I'd push back on is the kind that treats the map as a targeting system — who do I need to neutralize, who do I need to win over, how do I route around the people I don't like? That approach tends to produce a certain kind of short-term success and a lot of long-term wreckage. People in organizations are not obstacles in a puzzle. They're people.

What the map gives you, at its best, is the ability to see a system clearly enough to participate in it honestly — to know what you're actually dealing with, rather than what the official version says you should be dealing with. That's a form of respect for reality. And organizations run on reality whether they acknowledge it or not.

FAQ

How long does it take to build an accurate power map? A rough working map takes about thirty minutes if you have a few weeks of direct observation to draw on. A map you'd trust for high-stakes navigation takes longer — usually two to three months of deliberate attention. The first map is a hypothesis; the later versions are tested against what you actually see happen.

Does this work in flat organizations or startups? Yes, and in some ways it's more important there. Flat organizations often have very strong informal hierarchies that are never named because the culture discourages acknowledging hierarchy at all. The power is still there — it's just less legible because there's no formal structure to compare it against. The same method applies; you just skip the org chart step entirely.

What if the person I identify as most powerful is someone I need to work with? That's exactly why the map is useful. Knowing who actually shapes decisions means you can engage the right people early, frame requests in ways that address their real concerns, and avoid the confusion of being told yes by someone who can't actually say yes.

Can a power map go out of date? Quickly. Power structures shift with leadership changes, organizational restructuring, and shifts in strategic priority. A map that was accurate eighteen months ago can be significantly wrong today. Treat it as a living document, not a finished artifact.

Is there an ethical issue with mapping power in an organization? I don't think observation is unethical. Every thoughtful person in an organization is informally mapping power already — they just usually do it unconsciously. Making it explicit and deliberate doesn't change the ethics; it changes the accuracy. The ethical question is what you do with the map, not whether you have one.

Last updated: 2026-06-20

Jared Clark is the founder of PatternThink, where he writes about the hidden structural patterns that shape institutions, organizations, and human systems. Read more at patternthink.com.