Skip to content
Playbook
AdvancedPillarHRManagerPeopleOps

Power & politics at work: a step-by-step HR playbook (with scripts)

A 7-step playbook HR can run when politics turn toxic — map the power bases, diagnose the game, intervene with scripts for the manager, the influencer, the…

16 min read
On this page
60-Second Summary
  • Politics is not a moral failing — it’s what happens when goals are interdependent, resources are scarce, and authority is ambiguous. You don’t eliminate it; you channel it.
  • Step 1 is a power map: for each player, list their five French & Raven bases (legitimate, reward, coercive, expert, referent) plus informational power.
  • Step 2 is to name the game: empire-building, credit-grabbing, blame-shifting, gatekeeping, coalition-building, or information-hoarding. Each has a specific counter-move.
  • Step 3–6 are intervention scripts you can lift verbatim: for the executive sponsor, the toxic influencer, the demoralized manager, and the bystanders who are watching to see whether HR will act.
  • Step 7 closes the loop — change the structural conditions (clarity of decision rights, RACI, comp transparency) so the same politics don’t re-emerge in 90 days.

Most HR training treats politics as something to deplore. That’s a luxury position. In real organizations, politics is the residue of three structural facts: goals are interdependent, resources are scarce, and authority is ambiguous. Your job isn’t to wish that away — it’s to channel power so the work gets done and the people who do the work aren’t demoralized.

What workplace politics actually is

Jeffrey Pfeffer’s working definition (Managing With Power, 1992): ‘the processes, the actions, the behaviors through which potential power is utilized and realized.’ Politics is downstream of power. If you want to change the politics, you have to change who holds power, on what basis, and over what.

The HR lens

Don’t ask ‘is this person political?’ Everyone in an organization is political — they have to be. Ask: (1) which bases of power are they drawing on, (2) is the game zero-sum or positive-sum, and (3) what structural condition is making this profitable behavior?

Step 1 — Build the power map

Before any intervention, write down the power map. For each player in the situation (usually 4–8 people), score their power on each base from 0 (none) to 3 (dominant). Use French & Raven’s five plus informational power.

BaseWhat it looks likeHow to spot it
LegitimateAuthority from role/titleWho signs the offer letter, the budget, the PIP
RewardControls comp, promotion, plum projectsWho decides bonus pool allocation
CoerciveControls punishment, exit, exclusionWho can get someone fired or sidelined
ExpertKnows something nobody else knowsWho gets paged at 2am when prod breaks
ReferentPeople like and want to please themWho do new hires gravitate to in the first week
InformationalSees information others don’tWho is in the room when the decision is made

The power map almost always reveals the surprise: the formal org chart and the real power chart are not the same. The CTO might be legitimately powerful but referent-weak; the principal engineer who joined four years ago might be expert + referent + informational, which is a stronger combination than the CTO’s title alone.

Step 2 — Name the political game

Most political behavior fits a small number of recurring patterns. Naming the game in writing — to yourself first, then to the sponsor — converts a vague ‘there’s a lot of politics on this team’ into a diagnosable problem.

GameTellWhy it’s profitableCounter-move
Empire-buildingInsists every adjacent function should report to themHeadcount = status & compTighten scope; reward depth not breadth
Credit-grabbingFirst to email the exec with results; uses ‘I’ for team winsVisibility drives promotionMake contribution attribution explicit in reviews
Blame-shiftingPre-emptively documents others’ errors; ‘as I warned…’Avoids accountability costPre-mortems & decision logs with named owners
Gatekeeping‘You have to go through me to reach X’Manufactures informational powerPublish org charts, decision rights, escalation paths
Coalition-buildingCaucuses before every meeting; surprise alignment in the roomWins decisions before they’re debatedSurface dissent on purpose; pre-reads + silent reading
Information-hoarding‘Let me handle the comms’; resists shared docsAsymmetry = leverageDefault-open documentation, shared dashboards

Step 3 — Align the executive sponsor (script)

You cannot run a political intervention without an executive sponsor who understands the diagnosis and is willing to spend political capital. Misalignment here is the #1 reason HR interventions fail.

Script — HR to executive sponsor

‘I want to walk you through what I’m seeing on [team] before we agree on action. Three observations: (1) [Player A] is drawing heavily on coercive and informational power — specifically [example]. (2) The game I see is [game name] — here’s why it’s profitable: [structural reason]. (3) Two structural conditions are making this rational: [decision rights ambiguity] and [comp opacity]. I’m recommending a three-part intervention: a direct conversation with [A], a re-empowerment of [manager], and a structural fix to [decision rights]. I need you to (a) endorse the conversation with [A] explicitly so they don’t bypass me to you, and (b) not undercut the structural fix in the next exec meeting. Can you commit to both?’

If the sponsor will not commit to both, you don’t have a sponsor. Stop the intervention. Document the conversation. Revisit when conditions change.

Step 4 — Confront the toxic influencer (script)

Toxic influencers are usually high-expert + high-referent + high-informational. Frontal attacks fail because their referent power converts colleagues into defenders. The conversation must be specific, behavioral, and tied to consequences the person actually cares about (which is rarely money — it’s status and access).

Script — HR + manager to the influencer (60 minutes, 1:1, documented)

‘[Name], thanks for making time. I want to be direct so you’re not guessing. I’m going to describe three behaviors I’ve observed, the impact, and what needs to change. Then I want to hear your response. (1) BEHAVIOR: In the last six weeks, you’ve held three pre-meetings with [colleagues] before the architecture review and arrived with pre-aligned positions. IMPACT: Three engineers told me they’ve stopped raising objections because they don’t see the point. CHANGE: Pre-meetings are fine. Pre-alignment that suppresses in-room debate is not. From now on, any pre-meeting position has to be shared in the doc 24 hours before the meeting. (2) BEHAVIOR: When [manager] made the call on [project], you escalated to [VP] without telling them. IMPACT: Their authority is now in question with their team. CHANGE: Escalations go to [manager] first or to me. If you escalate over them again without telling them, I will name it in your next review. (3) BEHAVIOR: You control the deploy pipeline access list and have not added [two engineers] who need it. IMPACT: They route requests through you, which makes you the bottleneck. CHANGE: Access list goes to platform team this week. Now — what am I getting wrong, and what do you want to push back on?’

Three rules for this conversation: (a) describe behavior not character — never ‘you’re political,’ always ‘this specific action had this specific effect’; (b) end every item with what changes, not just what’s wrong; (c) leave time for pushback — the goal is behavior change, not a confession.

Step 5 — Re-arm the demoralized manager (script)

The manager who has been outflanked by an influencer is usually in one of two states: learned helplessness (‘nothing I do matters’) or over-correction (‘I’m going to fire them’). Neither is the right state. Your job is to restore their sense of agency and give them three concrete moves.

Script — HR to outflanked manager

‘I’ve seen what’s been happening with [influencer], and I want to be clear: this is not a reflection of your competence. It’s a structural problem we let go on too long. Here’s what I’ve done and what I need from you. WHAT I’VE DONE: Aligned with [sponsor], had a direct conversation with [influencer] with these three commitments [list]. The sponsor is publicly endorsing your decision rights on [scope]. WHAT I NEED FROM YOU: (1) In the next architecture review, make a call in the room — even a 70%-confident call — and don’t soften it. I’ll back you. (2) In your 1:1 with [influencer] this week, restate the new ground rules in your own words. (3) Reach out to the two engineers who’ve gone quiet and ask them, specifically, what they’d raise if they thought it would land. Forward me what you learn.’

Step 6 — Signal to the bystanders (script)

The most underweighted audience in a political intervention is the bystanders — the 80% of the team watching to see whether HR will actually act. If you intervene invisibly, they assume nothing happened, and the next person who games the system gets the same green light.

You don’t need to publish the consequences. You do need to publish the standards. Use the next all-hands or team meeting to name — without names — the standard you’re holding everyone to.

Script — manager to team (90 seconds, at the top of a team meeting)

‘Quick standard-setting before we get into the agenda. A few of you have raised — directly and indirectly — that decisions on this team have started to feel pre-cooked. I’ve heard it. Here’s what we’re changing. Effective today: (1) decisions of [type] are mine to make in the room, not in side-channels; (2) pre-meeting positions go in the doc 24 hours ahead; (3) escalations over my head come back to me within 24 hours so there are no surprise reversals. If you see any of these violated, raise it to me or to [HRBP] — and I will act on it. End of standard-setting. Item one on the agenda…’

Step 7 — Fix the structural conditions

If you don’t change structure, the same politics re-emerge with a different cast in 6–12 months. The four structural levers, in order of leverage:

  1. Decision rights — write a RACI for the 5–10 most contested decision types on the team. Publish it.
  2. Information flow — default-open docs, shared dashboards, recorded decisions with named owners. Information hoarding stops paying.
  3. Reward criteria — make promotion criteria public and audit the last three promotion cycles for ‘visibility’ vs ‘contribution.’ If the political players got promoted, you’ve been training the behavior.
  4. Comp transparency — at minimum, publish bands. Opacity rewards backchannel negotiation, which is itself a political game.

Three worked scenarios

Scenario A — The principal engineer who runs a shadow org

Power profile: expert 3, referent 3, informational 3, legitimate 1. Game: gatekeeping + coalition-building. Sponsor move: CTO publicly delegates architecture decisions to the EM, not the principal. HR move: Step 4 conversation focused on pipeline access and pre-meetings. Structural fix: published architecture decision records with named decider; the principal is a contributor, not the decider.

Scenario B — The director who keeps absorbing scope

Power profile: legitimate 3, reward 2, coercive 2. Game: empire-building. Sponsor move: CEO names a scope boundary and refuses headcount increases inside the contested zone. HR move: re-write the director’s scorecard around depth metrics (retention, promo rates from within) not breadth (number of functions reporting in). Structural fix: org-design review every 6 months with explicit ‘what should NOT be in this org’ section.

Scenario C — The PM who shifts blame in writing

Power profile: informational 3, referent 2, legitimate 2. Game: blame-shifting via documentation. Sponsor move: VP Product stops accepting post-hoc memos as evidence. HR move: introduce pre-mortems with named owners — the same person who would later write the blame memo now has to sign the pre-mortem. Structural fix: decision log with two columns: ‘who made this call’ and ‘who was consulted.’

Closing principle

Politics is rational behavior under unclear conditions. Your interventions only stick if you change the conditions. A great HR partner is, on this dimension, an organizational designer.

Written by Pawan Joshi.Sources cited inline.
First published 15 Jun 2026See site changelog →