Office Politics 101: Read the Power Map Before You Talk Survival
Topic: Office Politics 101·4 Principles
"To subdue the enemy without fighting is the acme of skill." — Sun Tzu, The Art of War
This week's premise: Many engineers treat "politics" as a dirty word, believing "if I just do great work I'll be treated fairly." That is exactly the most dangerous naivety — it doesn't make you above politics, it makes you its victim. Office politics is not noble vs. base; it's about how power actually flows and how decisions actually get made. This week, four tools: a power map, the four political-player types, the stakeholder grid, and the reciprocal-altruism logic of political capital. Honestly: politics has moral gray zones, and we'll mark the cost of every move.
PRINCIPLE 01
Power Mapping: The Org Chart Won't Tell You Who Decides
Map the real decision path, not the reporting line
Power structureShadow orgSocialize
The Principle in One Sentence
The org chart shows reporting lines and accountability; it almost never tells you how a decision actually gets made. Real power flows along three hidden lines — information, resources, relationships. The second map you must draw shows: who can make things happen, who can stop them, and whose objection gets taken seriously. The overlap between the two maps is often under half.
From the Source
"Know the enemy and know yourself, and victory will not be at risk; know the ground and know the weather, and your victory will be complete."In an organization, the "ground and weather" is the power terrain — fail to read it, and even the best proposal hits invisible rocks.— Sun Tzu, The Art of War (Terrain)
Scene: You Socialized the Title, Not the Power
Situation: You (BigCat) propose a cross-team storage migration. The nominal decision-maker is platform director D. You send D the RFC and book a review.
Bad version (running on the org chart)
You only socialize it to D (the nominal owner). In the review, D says "technically I'm fine, but let's hear from the teams." Then a senior staff S you never briefed — D's most trusted source of technical judgment — raises three concerns on the spot. No conclusion; the proposal stalls for a month.
→ S has no decision authority but has veto-level influence. You socialized the title, not the power.
Good version (running on the power map)
Two weeks before the review, you grab coffee with S alone, walk him through the proposal, and ask "What would you be worried about?" — resolving his concerns privately or folding them into the RFC. Then you align with the PM most likely to block it. By the formal review, the key people are pre-wired and the meeting is just a rubber stamp.
Draw a Power Map (for your next push)
Who is the nominal decision owner? Who is the "shadow advisor" they quietly consult?
Who is the gatekeeper (controls information / budget / headcount flowing to the decider)?
Who is the connector (links many circles, best-informed)? Cross them = your information dries up.
Whose "silent objection" can quietly kill the proposal? (veto-level influence, no formal power)
Where does this decision actually get made — the formal review, or a hallway chat / Slack DM beforehand?
Common Mistakes
Mistaking title for power. The highest-ranked person often outsources judgment to an IC they trust.
First revealing the proposal at the formal meeting. Meetings are where you rubber-stamp, not persuade — persuasion happens beforehand.
Ignoring the gatekeeper (chief of staff, a senior staff). They decide whether you even reach the agenda.
Female Lens
Female Lens · Excluded from informal networks
The hidden lines of information often flow through informal networks (drinks, the smoking area, the after-work game). Research (Herminia Ibarra) shows women are more often excluded from these informal networks, and so learn later "where the real decision happens." The fix isn't forcing your way into the bar — it's deliberately building your own network: 2-3 fixed cross-team "no-agenda coffees" each week, used purely to read the terrain, not to discuss projects — turning what others get by accident into your deliberate routine.
PRINCIPLE 02
Owl, Fox, Donkey, Sheep — Locate Yourself First
The four political-player types
Baddeley & JamesPolitical awarenessSelf-location
The Principle in One Sentence
Political skill splits into two independent axes: political awareness (can you read power and motives?) × intent (acting for the common good, or only for yourself?). The two axes produce four player types. The classic engineer trap is being the "sheep": full of integrity, zero awareness — repeatedly sacrificed in games without knowing it. The goal is to be the "owl": high awareness + integrity.
From the Source
"Being politically unaware does not make you 'above politics' — it makes you a victim of it."— Simon Baddeley & Kim James, "Owl, Fox, Donkey or Sheep: Political Skills for Managers" (1987)
Four Quadrants: Awareness × Intent
Scene: Sheep vs. Owl Amid Reorg Rumors
Situation: Reorg rumors suggest a key project of your team may be moved to another group.
Sheep reaction
"I'll just focus on doing great technical work; politics isn't my business." → Three weeks later the project is moved, justified as "the other group has more bandwidth," and you never said a word to keep it.
Owl reaction
You don't play dirty, but you actively read the situation and act legitimately: (1) figure out who's pushing the move and why (genuine efficiency, or a director expanding turf?); (2) write a one-pager on the objective reasons the project should stay; (3) socialize it to the real decision owner before the decision meeting. You didn't manipulate — you just refused to be absent.
Locate and Upgrade Your Political Position
Which quadrant am I in right now? (Honestly — most engineers are sheep and deny it.)
That person on my team who's always better-informed yet keeps surprising me — fox or owl?
The last time I "focused on tech and ignored politics," was I truly above it, or a victim?
My next move — is it for the team / the facts (Owl), or just for my own turf (Fox)?
Am I being a "donkey" — selfishly and clumsily grabbing credit, going over heads, taking sides too early?
Common Mistakes
Mistaking "sheep" for the moral high ground. Not reading politics isn't purity; it puts your teammates' interests at risk.
Treating every political player as a fox. Many high-awareness people are owls — the ones you should learn from, not guard against.
Trying to jump from sheep straight to fox. Learn awareness before tactics — awareness + integrity is the owl, and that takes you far.
PRINCIPLE 03
The Power / Interest Grid — Spend Capital Where It Pays
Map stakeholders, then allocate finite energy
You can't invest equally in everyone. Place each stakeholder on two axes: power (how much they can sway the outcome) × interest (how much they care). The four boxes call for four entirely different strategies. The deadliest error is treating "high power + low interest" people as background scenery — they're quiet, until they get surprised and veto on the spot.
From the Source
"If you defend everywhere, you are weak everywhere."Political energy is finite force. Spreading it evenly across all stakeholders means too little force on the people who matter most.— Sun Tzu, The Art of War (Weak Points and Strong)
Four Quadrants: Power × Interest
Scene: A Proposal to Merge Three Teams' Services
Situation: BigCat proposes merging three teams' services onto one platform. Place each stakeholder on the grid —
Allocate energy by the grid
· Platform lead L (high power + high interest) → Manage Closely: weekly alignment, pull them in as co-owner.
· The overseeing VP (high power + low interest) → Keep Satisfied: they don't care about technical detail, but if surprised by someone at an all-hands they'll block instantly. Send a one-page exec summary, 30-second face-to-face sync — you're not seeking enthusiasm, just "no objection."
· A vocal senior engineer on a merged team (low power + high interest) → Keep Informed: they can't sway the decision but can set the tone on Slack; feed them detail, hear their concerns, and they may turn from objector into your best evangelist.
· An unrelated neighboring team (low power + low interest) → one FYI email suffices.
→ Cost of misallocation: pouring all your time onto the vocal engineer while forgetting to brief the VP — who gets surprised in review and vetoes.
Draw the Grid for Your Next Proposal
Have I scored each stakeholder on both "power" and "interest"?
Is there a "high power + low interest" person I haven't briefed yet? (most overlooked, most lethal)
For "high power + high interest" people, am I managing them as objects, or have I pulled them in as co-owners?
The vocal but low-power person — am I treating them as noise, or as a potential evangelist?
This grid shifts with reorgs / promotions — how often do I refresh it?
Common Mistakes
Treating high-power-low-interest people as scenery — until they get surprised and veto.
Spreading effort evenly — under-investing in your key allies.
Filing the grid away after drawing it once. Power distribution gets reshuffled with every reorg.
PRINCIPLE 04
Political Capital: Deposit Before You Withdraw
Reciprocal altruism and coalition-building
Dawkins · reciprocityTit-for-tatCoalitions
The Principle in One Sentence
Influence is not something you "have," it's something you "deposit." Every time you unblock someone, give public credit, or don't grab credit, you deposit into a relationship account; when you need to push something cross-team, you withdraw the sum of past deposits. This is reciprocal altruism: in repeated games, "extend goodwill first, give-and-take" wins long-term. But there's a hard constraint: you must not be the sucker — when you meet a taker who only withdraws, cut off supply decisively.
From the Source
"Don't be envious. Don't be the first to defect. Reciprocate both cooperation and defection. Don't be too clever."These are the four maxims of the tit-for-tat strategy that won Axelrod's tournaments: nice, provocable, forgiving, and clear.— Robert Axelrod, The Evolution of Cooperation (1984); popularized by Richard Dawkins, The Selfish Gene (Ch. 12, "Nice Guys Finish First")
Scene A: Spot and Recalibrate a Taker
Situation: Peer P comes to your team for help every few days (borrowing people, firefighting, reviews), but when you need them it's always "next week."
The boundary-less giver
You keep saying yes to everything. Three months later the team is grumbling, you're drained — and P's account is still in your debt.
Tit-for-tat: forgiving, but stop unconditional supply
"P, I'm glad to keep supporting you. But over the past two months, the things I helped with — when it was my turn to need X, it never got slotted in. Can we get X into your next sprint first? That way I can keep helping you down the line."
→ Make reciprocity explicit, give them one chance to return to cooperation (forgiving), while clearly ending one-way supply — no burned bridge, but the account must run both ways.
Scene B: Coalitions Are Built Before the Meeting, Not In It
Situation: Before a reorg you want to push a new direction, but on your own you don't carry enough weight.
One-on-ones before going public
Before the proposal goes public, privately approach 2-3 aligned, weighty peers individually: "I'm thinking of pushing X; the upside for your team is Y — what do you think? What would need to change for you to support it?" By the formal proposal, it's not you speaking alone — it's a coalition speaking.
Your Political Capital Account
In the past month, what "deposits" have I made to peers / other teams (substantive help, public credit, not grabbing credit)?
Is there a persistent "withdraw-only" taker around me? Am I still supplying unconditionally?
For my next big proposal, which allies have I pre-wired beforehand? Or am I planning to "let the proposal speak for itself" in the room?
Am I overdrawing some account (always asking the same person, never reciprocating)?
Is my "goodwill" tit-for-tat (can be ended reciprocally), or boundary-less (destined to be drained by takers)?
Common Mistakes
Being a boundary-less giver. Adam Grant's data: givers occupy both the top and the bottom of performance — the difference is whether they protect themselves from being drained by takers.
Only remembering relationships when you need something. Deposits must start long before you need to withdraw.
Building coalitions at the meeting table. The real alignment happens in one-on-ones beforehand.
Helping invisibly. You deposited but they never noticed — the balance is zero. Let your contribution be seen, in moderation.
Female Lens
Female Lens · Office housework is not political capital
"Office housework" — note-taking, ordering lunch, organizing team events, onboarding newcomers — these non-promotable tasks are disproportionately assigned to women (Linda Babcock's core research, The No Club). They look like "deposits" but are pseudo-capital that doesn't count toward promotion. Distinguish: a real deposit is high-visibility, strategically relevant help (unblocking a critical issue, covering an important demo); office housework is low-visibility work anyone could do. A script when assigned: "My bandwidth this quarter is committed to X (a strategic project). Can we rotate the lunch ordering / hand it to someone newer?" Learning to say "no" is how you stop selling your capital cheap.
Further Reading
Jeffrey Pfeffer · Power: Why Some People Have It—and Others Don't — the Stanford GSB power course; the most candid empirical take on org politics.
Marie G. McIntyre · Secrets to Winning at Office Politics — a practical playbook on player types and concrete tactics.
Simon Baddeley & Kim James · "Owl, Fox, Donkey or Sheep" (1987) — the original source of the four political-player model.
Richard Dawkins · The Selfish Gene (Ch. 12) & Robert Axelrod · The Evolution of Cooperation — the science behind reciprocal altruism and tit-for-tat.
Robert Cialdini · Influence — the reciprocity principle and the six weapons of influence.
Adam Grant · Give and Take — giver / taker / matcher, and "the giver who doesn't get drained."
Herminia Ibarra · Act Like a Leader, Think Like a Leader — informal networks and building the network that lets you "read the terrain."
Sun Tzu · The Art of War (Offensive Strategy / Terrain / Weak Points and Strong) — know-self-and-other, strike the void, subdue without fighting — mapped onto org games.
Open Questions
Reading power, building coalitions, pre-wiring — where's the line between this and manipulation?
The line is intent and transparency. Pre-wiring is "letting the right people know in advance and giving them a chance to voice concerns" — that's respect; manipulation is "hiding information and engineering an asymmetry for private gain." The same action (a pre-meeting 1:1) can be used by the owl to align on facts, or by the fox to set an ambush. Honesty has a real cost: sometimes transparency loses you a win you could have stolen by surprise — that's the price the owl accepts and the fox doesn't. A simple self-check: could you openly disclose what you did to all parties involved?
In companies that call themselves "flat / anti-hierarchy" (as many tech firms do), does the power map still hold?
Even more so. When hierarchy is formally weakened, power doesn't vanish — it moves into more hidden informal networks (who has dinner with the founder, who holds sway in a certain Slack channel, who gets quietly pulled in to decide). Politics in flat orgs is often harder to read, because there's no title as a clue. Pfeffer repeatedly notes that "flat" usually means the power map is hidden, not removed.
How should this (Western, direct) playbook be adapted for East Asian / high-context organizations?
In high-context cultures, the deposit-and-withdraw cycle of relationships is longer and more indirect; pre-wiring relies more on private settings and third-party introductions than on a direct one-on-one showdown. "Face" makes the cost of public objection extremely high — so "aligning beforehand" isn't a technique there but a necessity: any proposal that makes someone lose face in public is nearly doomed. Erin Meyer's The Culture Map breaks this down concretely.
When you judge that the politics of your org has gone "sick" (bad money drives out good, foxes rule), do you keep playing or exit?
First distinguish "local factional fighting" from "systemic rot." The former you can survive via coalitions, changing managers, or transferring; the latter — promotions tracking only allegiance, truth-tellers punished, a steady stream of good people leaving — when the signals are clear, a graceful exit (see Day 35) is often more rational than grinding it out. The hidden cost of staying isn't just the pain — it's that you'll slowly be domesticated by the environment into a fox or a donkey. A test: the last time you told the truth, were you rewarded, or were you marked?
Your Day 6 Action
Pick one cross-team thing you're currently pushing, and do two concrete things:
(1) Draw a power map (15 minutes, on paper): Who is the nominal decision owner, the shadow advisor, the gatekeeper, and the person with veto-level influence? Then use Card 3's grid to score each on "power × interest."
(2) Find the "high power + low interest" person you haven't briefed, and this week send them a one-page exec summary or book a 15-minute sync — the goal isn't enthusiastic support, it's that they "don't get surprised."
Reflection: Look back at a proposal that "failed / stalled" in the past year — did it lose on the merits, or because you socialized the title but missed the power?