Managing sideways: influence without authority

A large share of workplace frustration comes from needing something from someone who has no obligation to provide it. The skills that work here are specific and rarely taught.

Start with their objectives

The step that resolves most of it and is skipped almost universally.

People prioritise what they are measured on. A request that helps you and does not help them competes against everything that does.

Which makes the first question: what is this person accountable for, and does what I need connect to it?

Frequently it does and nobody has said so. Framing the request in terms of their objective rather than yours changes the answer without changing the request.

Where it genuinely does not connect, that is worth knowing early, because the honest route is then to make it someone's priority through whoever sets priorities.

Ask before you need it

Requests arriving with a deadline attached are experienced as impositions. The same request with time attached is a conversation.

Building the relationship before requiring anything from it is the least sophisticated and most effective technique available, and it cannot be done retroactively.

Make it easy

The practical lever.

A request that requires someone to work out what you want, gather context and decide an approach is expensive. The same request with the context supplied, the options laid out and a recommendation attached is cheap.

Doing that work yourself is frequently faster than the delay caused by not doing it, and it substantially raises the probability of a yes.

Reciprocity

Well documented in social psychology and straightforward in practice.

People help people who have helped them. Which means the useful position is to have been useful first, without keeping an explicit ledger — because an explicit ledger converts a relationship into a transaction and reduces the effect.

Noticing what someone needs and providing it before being asked is the version that works.

Credit

The most underused instrument.

Publicly attributing contributions, specifically and to the right people, costs nothing and is remembered.

Its opposite — allowing ambiguity about who did what — is remembered considerably longer, and it is the most reliable way to make future cooperation difficult.

Escalation, used properly

Going above someone is treated as a hostile act, and it is when done badly.

The version that does not damage the relationship: tell them you are going to, say why, and frame it as a prioritisation question rather than a complaint.

"We both have commitments that conflict and neither of us can resolve it at our level — can we take it to X together?" is a genuinely different act from going around someone quietly.

Escalating without warning is remembered permanently and is rarely worth what it achieves.

Understanding the constraint

Requests are refused for reasons that are frequently not stated.

Capacity, competing instructions, a previous bad experience, a technical obstacle, or a disagreement about the approach that has not been voiced.

Asking directly — what would need to be true for this to be possible — surfaces the actual constraint, and it is a far more productive question than repeating the request with more emphasis.

Occasionally the answer reveals that the request is unreasonable, which is also useful.

Written follow-up

Unglamorous and it does more than any technique.

A short note after a conversation stating what was agreed, by whom, by when, prevents the most common failure — two people leaving with different understandings and discovering it a fortnight later.

It also creates a record without being adversarial, provided it is written as a summary rather than as a demand.

When cooperation genuinely will not come

Worth naming, because the influence literature tends to assume every relationship is workable.

Where someone is actively obstructing, where there is a genuine conflict of interest, or where the organisation has set incompatible objectives, no amount of interpersonal skill resolves it.

That is a structural problem and the response is structural: change the objectives, change the reporting line, or escalate for a decision.

Continuing to apply influence techniques to a structural conflict is a common and exhausting mistake, and recognising the difference early saves a great deal.