You cannot use power responsibly if you cannot see it.

Most people navigate organizational power through instinct. They know who matters, who blocks, who influences, who must be consulted, who is trusted, who has the founder's ear, who controls budget, who can make a meeting happen, and who can quietly make work impossible.

Instinct helps. It is not enough.

When the work is important, build the map.

A power map is not a political hit list. It is an operating tool. It shows where execution capacity lives, which powers are needed, which powers are missing, and how to move work without relying on hidden dynamics, manipulation, or heroic escalation.

Start with the work

Do not map power in the abstract. Map it around a real outcome.

Power only matters in context. The power required to ship a product change is different from the power required to change pricing, redesign a process, resolve a customer escalation, hire an executive, adopt AI tools, cut a project, or change a planning rhythm.

Write the outcome clearly:

  • What important work needs to happen?
  • By when?
  • Why does it matter?
  • What will change if it succeeds?
  • What will continue if it stalls?

The clearer the work, the clearer the power map.

Inventory your own power

Start with yourself, not because you are the center of the system, but because self-deception is expensive.

Rate your current power for this work from 1 to 5 in each area:

  1. Formal authority: do you have the role or mandate to decide?
  2. Influence: can you shape beliefs and behavior among key people?
  3. Legitimacy: do people accept your involvement as warranted?
  4. Expertise: do you understand the domain enough to guide tradeoffs?
  5. Trust: do people believe you will handle the work fairly and competently?
  6. Resources: do you control budget, people, time, tools, data, or attention?
  7. Information: do you have the context others need?
  8. Network position: can you reach the people who matter?
  9. Narrative: can you explain why the work matters in a way that holds?
  10. Follow-through: do people have evidence that you turn commitments into action?

Then write one sentence: “For this work, my strongest source of power is ___, and my weakest necessary source is ___.”

That sentence prevents fantasy.

Map the players

List the people and groups whose power affects the work.

For each, identify:

  • what they control;
  • what they care about;
  • what they fear;
  • what they can approve;
  • what they can block;
  • what they can delay;
  • what they know;
  • who trusts them;
  • what cost they would bear;
  • what would make their support legitimate.

Do not reduce people to obstacles. Most stakeholders are protecting something real: customers, risk, architecture, morale, budget, quality, commitments, workload, reputation, or strategy. If you cannot name what they are protecting, you do not understand their power.

Map decision rights

Write down who can say yes, no, or not yet.

Approval power, veto power, delay power, recommendation power, and exception power should be explicit. If they are not explicit, make your best hypothesis and test it.

Ask:

  • Who owns the final decision?
  • Who frames the options?
  • Who must approve?
  • Who has a legitimate veto?
  • Who can delay without saying no?
  • Who can escalate?
  • Who can grant exceptions?
  • Who owns consequences after the decision?

If nobody can answer these questions, your first power move is not persuasion. It is decision-rights clarification.

Map dependencies

Identify every critical dependency outside your direct control.

For each dependency, name the owner, scarcity, criteria, queue, timeline, escalation path, and cost of delay. Then ask whether the dependency owner has been brought in early enough to shape the path responsibly.

Late dependency discovery creates avoidable power conflict. Early dependency mapping creates options.

Map coalitions

Ask who needs to move together.

A coalition is not everyone who likes the idea. It is the set of people whose authority, influence, legitimacy, resources, trust, or execution capacity must combine for the work to happen.

For each coalition member, write:

  • why the work matters to them;
  • what tradeoff they need named;
  • what commitment is required;
  • what credit or protection they deserve;
  • what would cause them to withdraw support.

This turns coalition-building from relationship fog into operating design.

Map trust and legitimacy risks

Power fails when people do not believe it is being used legitimately.

Ask:

  • Who might see this work as imposed, self-serving, risky, or unfair?
  • Who has been excluded from shaping something they will have to own?
  • Where might authority exceed trust?
  • Where might influence look like manipulation?
  • Where could credit be misallocated?
  • Where could dissent be punished or ignored?

Fix these risks early. Legitimacy is easier to protect than rebuild.

Choose your 90-day power moves

A power map is useful only if it changes action.

Choose three moves for the next 90 days. Good moves usually fit one of these categories:

  1. Clarify authority: make decision rights, veto criteria, or escalation paths explicit.
  2. Build legitimacy: bring affected people into the framing earlier; explain tradeoffs; make process fairer.
  3. Unlock dependencies: secure capacity, define standards, or create a visible queue.
  4. Strengthen coalition: align the people whose support actually determines motion.
  5. Increase trust: improve follow-through, credit sharing, discretion, or transparency.
  6. Change narrative: explain why the work matters in terms that connect strategy to real operating consequences.
  7. Delegate power: give someone closer to the work the authority and context to move faster.

Avoid moves that only increase your personal control. The goal is not to become indispensable. The goal is to make the work move responsibly.

Ethical guardrails

Before acting, run the power map through five tests:

  • Clarity: will this make roles, decisions, or tradeoffs clearer?
  • Momentum: will this help important work move, not just help me win?
  • Accountability: will the people with power own consequences?
  • Capability: will this make others more able to act, not more dependent?
  • Legitimacy: would the move still look defensible if explained honestly to affected people?

If a move fails these tests, rethink it.

No credit theft. No hidden punishment. No hoarding information to create dependence. No side-channel manipulation. No blocking without owning the cost. No using trust as a weapon.

Power used well should leave the system stronger.

The final audit

For your current important initiative, complete this page:

  1. The work that must move:
  2. The decision that matters most:
  3. The formal decision owner:
  4. The informal power holders:
  5. The vetoes and delays:
  6. The critical dependencies:
  7. The coalition required:
  8. The legitimacy risks:
  9. The trust assets:
  10. The ethical risks:
  11. The three 90-day power moves:
  12. The first conversation to have this week:

That is your power map.

If the page feels too abstract, force it into one concrete sentence per line. A useful power map should tell you what conversation to have, what decision to clarify, what dependency to unlock, what coalition to strengthen, what risk to name, and what not to do even if it would help you win faster.

The hard truth

Power is not dirty because it exists. It becomes dirty when it is hidden, hoarded, denied, or used without accountability.

Strong operators build power maps because they want important work to move clearly, legitimately, and responsibly. They do not chase power for its own sake. They build enough execution capacity to make the work happen — and enough ethical discipline to make the organization stronger in the process.