Power & Politics
The thing technical people pretend doesn't exist — and then lose to. Power is simply the ability to get things done through others. Politics is the system that decides whose ideas win. You don't have to play dirty, but you do have to play.
🎯 By the end you'll understand
What organizational power really is, the seven sources you can draw on (French & Raven, plus informational and network power), the gap between the org chart and who actually decides, how to build power ethically, and the honest line between good politics and the manipulative kind that destroys trust.
KEY INSIGHTThe one idea to take away
Refusing to engage with politics doesn't make you above it — it makes you its reliable victim.
Smart, technical people tend to believe that the best idea should win on merit, and that "politics" is a dirty word for what less capable people do instead of real work. This belief feels noble. It is also why they watch worse ideas — backed by better-connected people — beat them again and again. Politics is not optional. Every group of humans deciding how to allocate scarce resources, attention, and credit is politics. The only choice you have is whether you participate consciously or get played unconsciously.
There is a vast middle ground between naive idealism ("I'll just be right and that will be enough") and Machiavellian scheming ("win at any cost"). That middle ground is principled influence: advancing genuinely good ideas through relationships, credibility, and a clear-eyed understanding of how decisions actually get made. That is the skill this lesson teaches.
DEFINITIONWhat power actually is
Strip away the menace the word carries and the definition is plain: power is the capacity to get things done — to influence outcomes and other people's behavior, with or without their initial agreement. It is not inherently good or evil. The surgeon, the firefighter, and the founder all need power to do their jobs. Power is just leverage on reality through other humans.
Organizational politics is what happens when people use that power — formal authority, relationships, information, expertise — to advance their goals inside the organization. It includes building coalitions, trading favors, shaping which problems get attention, and deciding whose version of events becomes "what happened." Most of it is invisible, and almost none of it shows up in your job description.
Authority is the formal right to direct others, granted by your position. Power is the actual ability to make things happen — which often has little to do with your title. The person everyone quietly checks with before a big decision may have no authority at all and enormous power. The newly promoted VP no one respects has the reverse. Confusing the two is the classic technical-leader error.
FRAMEWORKThe sources of power
The most durable model here is French & Raven's bases of power (1959), extended over time with two more that matter intensely in knowledge organizations. Where does your ability to influence actually come from? Seven answers:
Legitimate (position)
Power that comes from your title and role. "I'm the manager, so this is my call." Real, but shallow — it evaporates the moment you leave the role, and it commands compliance, not commitment.
Reward
Control over things people want: raises, promotions, budget, good projects, public credit. Effective, but breeds transactional behavior — people perform for the reward, not the mission.
Coercive
The ability to punish: fire, demote, withhold, embarrass. It works fast and corrodes everything. Use it and you buy short-term compliance at the price of long-term trust and honesty.
Expert
Power from genuine knowledge and skill others depend on. The engineer whose judgment is trusted, the one who actually understands the system. Earned, portable, and respected — the technical person's natural home.
Referent (relationships & respect)
Power from being liked, admired, trusted — people want to follow you. The most underrated by analytical minds and the most powerful of all, because it generates commitment, not just compliance.
Informational
Power from knowing things others need: who's leaving, where the budget really sits, what the CEO actually thinks. The person at the centre of the information flow holds quiet, real leverage.
Network
Power from who you know and who trusts you across the org. The connector who can get a "yes" from three departments by Friday has more power than most people with bigger titles.
Legitimate, reward, and coercive power are lent to you by the position — lose the role, lose the power. Expert, referent, informational, and network power are earned by you and travel with you anywhere. Technical people over-rely on expert power alone and ignore referent and network power entirely — which is exactly why they get out-manoeuvred by people who are merely "good with people."
CORE CONCEPTFormal vs informal power
The org chart is a map of formal power — the official reporting lines, who reports to whom, where authority is supposed to live. It is real, but it is the least interesting half of the picture. Overlaid on it is the informal power structure: the actual web of influence, trust, debts, and respect that determines what really happens. The two rarely match.
The director on the chart may rubber-stamp whatever a respected senior engineer recommends. A founder's old co-worker, three levels down, may have a private channel to the CEO that bypasses the entire hierarchy. The "real influence map" — who genuinely sways decisions — is something you have to read, because no one will ever draw it for you. (You'll build this map deliberately in Lesson 4.10.)
Formal power = the authority assigned by your position on the org chart. Informal power = the real influence a person holds through expertise, relationships, information, and network — regardless of title. Strategy meetings happen on the formal map. Decisions are often made on the informal one, in corridors and one-on-ones, before the meeting ever starts.
SEE ITWhere's the real power?
Here's the trap: you look at a situation, find the highest title, and assume that's where the power sits. Pick a scenario below and reveal the informal sources of power the org chart hides — and the ethical move to build power in that situation.
The lesson repeats in every case: the highest title is rarely the whole story. Power flows through expertise others depend on, relationships that earn trust, and networks that move "yes" through the building. Reading that flow — and earning your place in it honestly — is the entire game.
IN PRACTICEBuilding power — ethically
If the word "building power" makes you uncomfortable, good — that instinct will keep you honest. But discomfort is not a strategy. Here is how principled operators accumulate real influence without selling their souls:
Become genuinely useful
Be the person who solves the problem nobody else can, ships the thing, knows the system cold. Expert power is the cleanest foundation — and the one technical people can build fastest.
Build relationships and reciprocity
Help people before you need them. Reliable, low-cost favors create a bank of goodwill (Cialdini's reciprocity at work). This is referent and network power, compounding quietly over years.
Control valued resources and information
Sit at the centre of something people need — a critical system, a key dataset, a relationship with a major client. Being a useful node, not a bottleneck-on-purpose, is legitimate leverage.
Deliver results, visibly
Quiet competence is necessary but not sufficient. If no one knows what you did, you built no power. Take fair credit and make your contribution legible — that is not bragging, it's accuracy.
Ally with the powerful
Find the people who already have influence and whose goals align with good outcomes, and make yourself valuable to them. Borrowed power is real power — as long as you back the right ideas, not just the winning side.
You hate this. Fine. You don't have to schmooze or backstab. But you do have to: learn what your key stakeholders actually care about, build a few trusted allies, make your wins visible, and understand who really decides before you walk into the room. That's not selling out — it's the difference between your good ideas living or dying. You don't have to play dirty, but you must play.
CORE CONCEPTReading the political landscape
Before you act, map the terrain. Three questions reveal almost everything:
| Question | What you're actually mapping | How to read it |
|---|---|---|
| Who has power? | The real influence map — not the org chart | Whose opinion gets cited? Who do people check with before deciding? |
| Who owes whom? | The web of debts, loyalties, and alliances | Watch who defends whom, who hires whom, who reliably sides with whom. |
| Where are decisions really made? | Corridors and one-on-ones, not the meeting | If the meeting only ratifies a choice, the choice was made elsewhere — find that room. |
That last row is the one technical people miss most. They prepare an airtight argument for the meeting — and lose, because the decision was settled in three hallway conversations the day before, between people who never opened the deck. The work isn't just to be right; it's to be right in the rooms where it counts, before the formal meeting starts.
COMPARISONGood politics vs bad politics
"Politics" sounds dirty because we mostly notice the bad kind. But there is a clean version, and the distinction is not fuzzy — it turns on intent and whether the game is positive-sum or zero-sum.
| Dimension | Good politics | Bad politics |
|---|---|---|
| Goal | Advancing genuinely good ideas and outcomes | Advancing yourself, often at others' expense |
| Method | Relationships, persuasion, reciprocity, credibility | Spin, undermining, hoarding, backstabbing |
| Game type | Positive-sum — the org wins too | Zero-sum — your gain is someone's loss |
| Effect on trust | Builds it over time | Burns it; eventually catches up with you |
| Transparency | Would survive being made public | Depends on staying hidden |
A useful test: would you be comfortable if everyone saw exactly what you did and why? Lobbying allies for a project you believe in, explaining the same case to each stakeholder in their own language, building a coalition behind a good plan — all survive daylight. Spreading doubt about a rival, taking credit for others' work, hoarding information to make yourself indispensable — none of them do.
The painful truth: a mediocre idea championed by someone with relationships, credibility, and the ear of decision-makers routinely beats a brilliant idea presented by an isolated genius. This isn't because the org is stupid — it's because execution requires people, and people back what they trust. The answer isn't to whine about unfairness; it's to give your good ideas the political backing they deserve (you'll see this play out in Lesson 4.12).
WEAKNESSWhere this goes wrong
The classic technical-person failure: "I don't do politics." Refusing to engage doesn't exempt you — it just means you're playing blindfolded against people who can see. You'll lose resources, credit, and influence to people you consider less capable, and you'll never understand why. Naive idealism is not a moral high ground; it's a tactical surrender.
The opposite error. Manipulation, undermining, and zero-sum scheming can win in the short term — but they destroy trust, and trust is the substrate everything else runs on (Lesson 2.6). People remember. Reputations compound. The Machiavellian operator eventually finds that no one will extend them goodwill when they need it most. Power without trust is brittle and lonely.
"The data speaks for itself" — it doesn't; people interpret data through who they trust. And "I'm in charge, so they'll do it" — legitimate authority commands grudging compliance, not the committed effort that actually delivers. Expert power and positional power are both necessary and both insufficient alone. You need referent and network power too.
KEY INSIGHTWhere this connects in your course
- Stakeholder management (4.7) — the disciplined practice of mapping and serving the people whose power you just learned to read; politics is stakeholder work made honest.
- Organizational structure & the real influence map (4.10) — turning "informal power" into an actual map of who decides what, and how influence really flows.
- Trust (2.6) — the asset that good politics builds and bad politics destroys; the ceiling on how much power you can hold sustainably.
- Influence & persuasion (2.7) — the toolkit (reciprocity, credibility, framing) you use to convert relationships into "yes."
- Why good ideas lose (4.12) — the full anatomy of how mediocre-but-backed beats brilliant-but-isolated, and how to stop being the isolated one.
Power is not a dark art bolted onto leadership — it is the medium leadership operates in. The honest operator learns to read it, build it ethically, and spend it on good ideas. The alternative isn't purity; it's irrelevance.
GLOSSARYKey terms introduced
- Power
- The capacity to get things done and influence outcomes and others' behavior; neutral, not inherently good or bad.
- Organizational politics
- The use of power and influence inside an organization to advance goals — through coalitions, favors, information, and framing.
- Influence
- The ability to change others' beliefs, decisions, or behavior, ideally through persuasion and trust rather than force.
- Legitimate power
- Influence derived from one's formal position or title; lent by the role.
- Reward power
- Influence from control over things people want (raises, promotions, credit, good work).
- Coercive power
- Influence from the ability to punish or withhold; fast-acting and trust-destroying.
- Expert power
- Influence derived from genuine knowledge and skill others depend on; earned and portable.
- Referent power
- Influence from being respected, liked, and trusted, so people want to follow you.
- Informational power
- Influence from controlling or holding information others need.
- Network power
- Influence derived from the breadth and trust of one's relationships across the organization.
- Formal power
- Authority assigned by position on the org chart.
- Informal power
- Real influence held through expertise, relationships, information, and network, regardless of title.
ACTIVE RECALLCheck your understanding
Answer in your own words first, then reveal.
1Why is "I don't do politics" a losing position rather than a virtuous one?›
Because politics exists in every organization whether you engage or not. Refusing to participate doesn't make you above it — it makes you blind to it, so you lose resources, credit, and influence to people who can see the board you're playing on. Naive idealism is a tactical surrender, not a moral high ground.
2Of French & Raven's bases of power, which travel with you and which are merely borrowed — and why does it matter for a technical leader?›
Legitimate, reward, and coercive power are lent by your position — lose the role, lose the power. Expert, referent, informational, and network power are earned and portable. It matters because technical leaders over-rely on expert power alone and neglect referent and network power, which is exactly why they get out-manoeuvred by people who are "merely" good with relationships.
3What separates "good politics" from "bad politics"?›
Intent and game type. Good politics advances genuinely good ideas through relationships, persuasion, and credibility — it's positive-sum and builds trust. Bad politics advances yourself at others' expense through spin and undermining — it's zero-sum and burns trust. A quick test: would it survive being made fully public? Good politics does; bad politics depends on staying hidden.
4Why do good ideas so often lose to well-connected mediocre ones, and what's the right response?›
Because execution requires people, and people back what (and whom) they trust — so an idea with relationships and credibility behind it beats a brilliant idea presented by an isolated person. The right response isn't to resent the unfairness; it's to give your good ideas the political backing they deserve: build allies, make wins visible, and win the rooms where decisions are actually made.