Leading Without Authority: How to Get Things Done Across Silos You Do Not Control

Ask a senior leader where their work actually gets stuck and very few will say their own team. They will say the handover to operations. The dependency on engineering. The compliance review that takes six weeks. The regional director who agreed in the meeting and then did nothing.

This is the defining feature of modern senior work. Your accountability is vertical — you own the outcome — but your dependencies are horizontal, sitting with people who have their own targets, their own pressures, and no structural reason to prioritise you. The organisational chart says you are responsible. It does not say anyone has to help.

Most leaders respond by escalating, which works once or twice and then quietly makes things worse. Escalation is a withdrawal from a relationship account you will need again next quarter. The alternative is orchestration: making it genuinely easy and worthwhile for other people to do the thing you need, and building the conditions where they will.

1. Map the Real Decision Path, Not the Org Chart

Before you ask anyone for anything, work out who actually has to move. This takes twenty minutes and is skipped almost universally.

For any cross-functional outcome, identify four groups. The decider — the one person who can genuinely say yes, which is frequently not the person who attends the meeting. The doer — whose team’s hands are on the work and whose capacity is the real constraint. The blocker — the function that can stop this regardless of anyone else’s enthusiasm, usually risk, legal, security or finance. And the influencer — the person whose private opinion the decider checks before committing.

Two things surface almost every time. You have been lobbying the wrong person — typically the friendliest one rather than the decisive one. And there is a blocker you have not spoken to at all, who will surface late and expensively.

Fixing both before you begin is the single highest-leverage move in cross-functional work.

2. Translate Your Priority Into Their Currency

The most common failure in cross-silo influence is arguing the merits of your objective to someone who is not measured on it. You are asking them to spend their capacity on your scorecard, and explaining more forcefully why your scorecard matters will not change the arithmetic.

So find out what they are actually measured on this year — genuinely find out, by asking, rather than assuming. Then work out, honestly, how your request connects. Sometimes it advances one of their targets, and you should lead with that. Sometimes it removes a recurring irritation their team complains about. Sometimes it gives their people visible exposure to work they want.

And sometimes there is no connection at all. That is important information, not a failure. If your request is genuinely pure cost to them, stop trying to persuade and start negotiating openly — offer resource, offer sequencing that suits them, offer reciprocity, or accept that this needs a decision above you both and take it there cleanly rather than through attrition.

Pretending a cost is a benefit is the fastest way to become someone whose emails get deprioritised.

3. Lower the Cost of Saying Yes

People do not decline requests because they are unreasonable. They decline them because the request is expensive to process — ambiguous scope, unclear ask, unknown time commitment, no visible end.

Reduce that cost deliberately. Bring a specific ask rather than a topic: not can we talk about data access but I need two days of an analyst’s time in the first fortnight of October to do X; here is the brief. Bring the first draft, the outline scope, the proposed governance — so their contribution is to react rather than to originate. State the end point explicitly. And make the exit obvious: people commit far more readily when leaving is easy, and they leave far less often than you fear.

A useful discipline before any cross-functional ask: could the recipient act on this in under ten minutes without asking you a clarifying question? If not, you have not finished preparing, and you are about to spend social capital compensating for your own vagueness.

4. Build the Relationship Before You Need It

Influence without authority is almost entirely a function of pre-existing trust, and trust cannot be manufactured in the meeting where you need something.

The leaders who move things across silos most easily have usually done something unglamorous and consistent: they maintain a small number of standing relationships with their genuine dependencies. Half an hour a month, no agenda, mostly listening. They know what those functions are worried about. They have, at some point, helped without being asked and without invoicing the favour.

This is not networking, and it is not transactional. The mechanism is simpler than that — you cannot translate your priority into someone else’s currency if you do not know what their currency is, and you only learn that in low-stakes conversation.

Choose four to six people whose cooperation your outcomes genuinely depend on. That is two to three hours a month. It is the highest-return time in most senior diaries and the first thing to get deleted when the week compresses.

5. Make the Progress Visible — and Share the Credit Early

Cross-functional work dies quietly. Nobody cancels it; it simply stops being anyone’s priority, usually about five weeks in, when the initial energy has gone and no milestone has landed.

Two habits prevent this. First, create a visible, lightweight artefact that everyone can see — a single page showing what is done, what is next, who owns it and what is blocked. Not a governance apparatus. One page, updated fortnightly, sent to everyone including the blockers. Visibility creates gentle, non-escalatory accountability that no chasing email achieves.

Second, attribute contribution generously and publicly, and do it early rather than at the end. Naming someone’s team in front of their director in week three costs you nothing and materially changes what you get in week ten. Leaders who hoard credit find their second cross-functional initiative markedly harder than their first. Leaders who distribute it find the opposite — people start volunteering.

Orchestration, in the end, is not a soft skill in the dismissive sense. It is the operating system of senior delivery. The leaders who master it are not the loudest or the most senior in the room. They are the ones other people find it easy, and worthwhile, to say yes to.

If you are working on this and want a structured way through it, book a discovery call with us or explore our coaching, advisory and training services.

Frequently Asked Questions

What do I do when someone agrees in the meeting and then does nothing?

Treat it as a signal that the request never made it onto their real priority list rather than as bad faith. Go back and check three things: whether you were speaking to the person who actually allocates that capacity, whether the ask was specific enough to be actioned without further thought, and whether it connects to anything they are measured on. Public, lightweight progress tracking usually resolves the rest without escalation.

When is it right to escalate a cross-functional blockage?

When there is a genuine, irreconcilable conflict of priorities that only a shared senior leader can arbitrate — not when you are simply being deprioritised. Escalate openly and jointly where you can, telling the other party you are doing it and why. Escalation used as pressure works once and makes every subsequent request harder.

How much time should I spend on relationships with teams I do not manage?

Identify the four to six functions your outcomes genuinely depend on and hold a standing thirty minutes a month with each. That is two to three hours monthly. It consistently returns more than the same time spent chasing, because it is the only way to learn what those functions are actually measured on and worried about.