AdvancedHRPeopleOpsManager

Influence without authority: a step-by-step playbook for HR & staff functions

HR, security, and platform teams have to get things done without owning the people who do the work. A 6-step playbook with scripts for stakeholder mapping…

13 min read

On this page▾

Step 1 — Build the stakeholder map
Step 2 — Identify currencies
Step 3 — Run the first conversation
Step 4 — Design the coalition
Step 5 — Diagnose resistance
Step 6 — Close and credit

60-Second Summary

Cohen & Bradford’s ‘Influence Without Authority’ frames influence as a currency exchange — you offer what stakeholders value (inspiration, task, position, relationship, personal) in return for what you need.
Step 1 is a stakeholder map with three axes: influence, interest, stance. The mistake is treating high-influence/low-interest stakeholders like the rest — they need different treatment.
Coalitions of 3 are more durable than coalitions of 7. Recruit the smallest set that can win, then expand.
Resistance is information. The four resistance types — political, technical, emotional, structural — each need a different response.

Staff functions live or die on influence. You don’t own the engineers who must adopt the new policy, the managers who must run the new process, or the budget that funds the new initiative. The good news: there’s a craft to this, and it’s learnable.

Step 1 — Build the stakeholder map

Quadrant	Influence	Interest	Treatment
Champions	High	High	Co-design with them; they amplify
Sleeping giants	High	Low	Brief them in private; one ask, no surprises
Engaged supporters	Low	High	Give them roles; they bring energy
Periphery	Low	Low	Keep informed via broadcast; don’t over-invest

Add a third axis: stance (for / neutral / against). A high-influence stakeholder who is currently against you is more important than five low-influence supporters. Spend the time accordingly.

Step 2 — Identify currencies

Cohen & Bradford’s five currency families. For each stakeholder, guess their top two.

Currency family	Examples	What you can offer
Inspiration-related	Vision, ethics, excellence	Frame your ask as a shared mission moment
Task-related	Resources, support, info	Take a task off their plate; bring data they’d have to gather
Position-related	Recognition, visibility, reputation	Public credit; intro to the exec they want to reach
Relationship-related	Acceptance, understanding, personal support	Time, listening, advocacy in their absence
Personal-related	Gratitude, ownership, comfort	‘This is yours’ framing; reduce their cognitive load

Step 3 — Run the first conversation

Script — first 1:1 with a stakeholder

‘Thanks for the time. I’m not here to ask for anything today — I want to understand your world so my asks later are useful, not annoying. Three questions: (1) what are you trying to ship in the next 90 days that I should not get in the way of? (2) what’s a recurring pain you wish someone would just take off your plate? (3) when [function] has worked well with you in the past, what did they do that I should copy?’

Take notes. Send a one-paragraph recap within 24 hours. Don’t make any ask in the first meeting unless one falls into your lap.

Step 4 — Design the coalition

List the minimum set of supporters needed to win the decision. Usually 3.
For each, identify the currency you’re trading and your specific ask.
Sequence the asks — start with the easiest yes; use their yes as social proof for the next conversation.
Pre-wire the meeting. Surprises kill influence work. Every person in the room should know your ask before they walk in.

Pre-wiring is not the same as the political ‘pre-aligned coalition’ pattern. The difference: you tell everyone, including likely opponents, the same thing in advance. No one is ambushed.

Step 5 — Diagnose resistance

Type	What it sounds like	What it really is	Response
Political	‘[Other VP] won’t like this.’	Concern about power consequences	Get other VP on board first; come back
Technical	‘This won’t work because [detail].’	Real implementation gap	Co-solve the detail; bring an engineer
Emotional	Tone shift, terse replies	Felt threat — identity, control, fairness	Slow down; 1:1 first; ask what would feel different
Structural	‘We can’t — comp / system / policy says…’	Real constraint	Find the constraint owner; that’s your real meeting

Step 6 — Close and credit

Influence is a long game. The way you close one ask determines the next ten.

Send a written recap within 24 hours. Decisions, owners, dates.
Credit publicly, blame privately. Name the stakeholders in the all-hands email; surface concerns 1:1.
Close the loop on what their input changed. ‘Because you flagged X, we changed Y.’ This is the single most underused move in staff-function influence.

Written by Pawan Joshi.Sources cited inline.

First published 15 Jun 2026See site changelog →