Influence Without Authority

When you can't tell people what to do, trade: offer what they value in return for what you need.

Influence is an exchange: learn what the other side values, give first, and then ask.

To an executive

Much of the work that matters crosses teams you do not manage. Cooperation comes from offering what others value, such as recognition, resources and purpose, rather than from orders.

To an engineer

When a team resists your standard, find what it is protecting and offer something it values in exchange. Build goodwill by helping first, before you need support.

The idea

Architects rarely manage the teams who build what they design. Allan Cohen and David Bradford's Influence Without Authority describes how to get cooperation anyway. Their exchange model treats influence as a trade, based on reciprocity: people help those who help them.

The things people value are currencies. Cohen and Bradford group them into five kinds:

Inspiration — vision, doing something that matters.
Task — resources, help, information, getting the job done.
Position — recognition, visibility, reputation.
Relationship — understanding, acceptance, personal support.
Personal — gratitude, ownership, comfort.

Influence comes from offering the currencies the other person cares about, not the ones you do.

Why it works

Everyone is acting rationally from their position. A team that resists your standard is protecting something it values. Find out what, and you can usually offer it.

Reciprocity is a strong norm. Help given freely creates goodwill you can draw on later.

It replaces pressure with partnership. Escalation wins one argument and spends trust; exchange builds the relationship for the next one.

Where it applies

Driving adoption of a standard or platform across teams that don't report to you.
Getting time from busy experts or other departments.
Working with vendors and partners, where authority is limited by contract.

How to apply

Treat the other person as a potential ally, not an obstacle.
Understand their world: their goals, pressures and how they are measured.
Identify the currencies they value, and those you can offer.
Give first where you can — information, help, credit.
Ask clearly for what you need, and keep the relationship in balance over time.

Example scenario

An enterprise architect needed product teams to adopt a new event-publishing standard. Mandates had failed before.

She learned that the teams' biggest pain was being blamed for missing audit data. She offered a library that published events and wrote audit records for free, and credited the first adopting team in the quarterly review. Within two quarters, most teams had moved — and asked to help shape the next version.

Questions to ask

What does this person need to succeed in their own role?
What can I offer that they value — help, recognition, information?
Have I built the relationship before I need to ask for something?

When not to use it

Non-negotiable requirements such as security or regulatory controls, where you need clear authority and escalation, not a trade.

How it misleads you

Exchange that feels transactional or manipulative destroys trust quickly. The currencies must be real: help that genuinely helps, credit that is deserved. And a trade that only ever runs one way is not influence — it is a favour bank about to run dry.