openskills.info

Leading Without Authority

Getting things done through people who don't report to you and never will.

Most of the work that matters at any organization crosses a boundary you don't control. You need a decision from another team, effort from people with their own priorities, or a change from someone who outranks you. None of them have to do what you ask. Leading without authority is the skill of getting that work moving anyway — not by borrowing someone else's power, but by understanding what the people you need actually care about, and making the thing you want a reasonable use of their attention. It's the normal condition of most senior work, not a special case, and the people who are good at it rarely look like they're doing anything forceful at all.

Mostly Harmless

The Org Chart Invoker

Meets every hesitation by locating a line on the org chart that might, if read generously, imply the request is mandatory. "Well, this is technically owned by our group." Uses the word "technically" a great deal. Each invocation converts a person who might have helped into a person now interested in the precise boundaries of what they are obliged to do, which is a considerably shorter list. Has never noticed that the phrase does most of its work on the speaker, who finds it reassuring, and none at all on the listener.

The Permanent Volunteer

Discovers that asking other teams for work is uncomfortable and solves this by doing all of it personally, at night. Ships the first version single-handed and is quietly proud of it. Six months later is the only person who understands any of it, the sole support rota, and completely unavailable for anything new — having built, with enormous effort, a bottleneck in the shape of themselves. Describes this situation as being very busy, which is accurate and not the interesting part.

The Shadow Escalator

Receives a "not this quarter" and, rather than asking what would change that, mentions it to the person's manager — casually, in another meeting, as context. It works, once. The task gets done grudgingly and to the letter. Every subsequent request from the Shadow Escalator is now handled with the care and speed reserved for people who are known to go around you. The technique works exactly once and then continues to be used.

The Consensus Hostage

Will not move until everyone agrees, and has redefined "everyone" upward twice since the project began. Schedules a further alignment session whenever a single participant expresses a reservation. Mistakes the absence of objection for a mandate and the presence of one for a veto, and so waits, indefinitely, for a unanimity that no organization of more than four people has ever produced. The project is not blocked. It is simply never quite ready to start.

Scenarios

Another team's engineer is the only person who can unblock you, and their backlog is full. What would you do — escalate to their lead to have it prioritized, or find out what their team is currently measured on and whether your request can be framed as helping with that?

You're running a cross-functional project where three of the five contributors report elsewhere. One has quietly stopped attending. What would you do — raise the attendance issue with their manager, or ask them directly what changed and whether the project still makes sense from where they sit?

You believe a decision that's already been made is wrong, and it was made two levels above you. What would you do — argue that it's wrong, or find out what the decision was optimizing for and whether you can show a route that serves that same goal better?

Takeaway

  • Find out what the person you need is actually measured on, and connect your request to it. If you can't, you're asking for a favor — ask for it as one.
  • Trade. Offer something they value: cover, information, a dependency removed, credit in front of the right person.
  • Ask "what would have to be true for this to move up your list?" instead of asking again more urgently.
  • Go to someone's manager only after you've asked them directly, and tell them you're going to. Surprise escalation buys one outcome and costs every future one.
  • Distinguish who has to agree from who has to not object. They're different lists, and treating the second like the first is how things stall forever.

Go deeper

Awesome Links