On the first day of a large program you count the people you depend on, and then you count the ones who actually work for you, and the second number is close to zero. The vendor consultants report to the vendor. The client's finance analysts report to the controller. The integration team belongs to IT. The sponsor outranks you. Twenty-some people will determine whether this program lands, and you cannot fire, promote, reassign, or directly order a single one of them.

This is the part that breaks managers who have only ever led inside their own org chart. The instinct is to manage: assign the task, expect it done, escalate when it isn't. That instinct assumes authority you do not have here. On a program, the org chart is a fiction. The reporting lines run somewhere else, and the only thing that crosses them is influence.

So we stopped trying to be the manager of the program and started trying to be the person on it worth following.

You cannot fire anyone on the program. You lead them anyway, or it doesn't move.

Borrowed authority spends fast

You can escalate. Once, maybe twice on something that matters, you can go to someone's real boss and have a task reprioritized. But escalation is borrowed authority, and it spends fast — every time you use it you teach the team that the way to get your attention is to make you go over their head, and you spend a little of the credibility that made people want to help you in the first place. Lead by escalation and you become the bottleneck every decision routes around.

Real authority on a program is not granted by the org chart; it is earned at the level of the individual. People follow the lead who makes their job clearer, removes the thing blocking them, and is right often enough that betting on their judgment pays off. That kind of authority does not deplete. It compounds.

How you lead without the power to command

Influence sounds soft until you watch it fail, and then you see how specific it actually is. These are the levers that move people who do not report to you:

Leading people you can't command
  • Make the ask unmistakable. Ambiguity reads as optional. The person who knows exactly what is needed, by when, and why, will usually do it. The person who has to guess will deprioritize you.
  • Be worth betting on. Credibility is the currency. Be right, be straight about what you don't know, and people will extend you the benefit of the doubt that authority can't buy.
  • Make the right path the easy path. Remove the friction, prep the decision, do the unglamorous setup. People move toward whoever makes their work lighter.
  • Credit in public, correct in private. You have no carrots and no sticks except reputation. Spend it generously upward and carefully downward, and people will want to be on your program.
  • Escalate rarely, and to the real owner. Save the borrowed authority for the few things that genuinely need it, and aim it precisely. Used sparingly, it still works. Used often, it stops.

None of these require a title. All of them require showing up as someone whose involvement makes the work better, which is the only thing that reliably moves people who answer to someone else.

The cost of leading by command

Try to command a team you don't own and you get the worst outcome on a program: compliance on paper and resistance underneath. People do the literal task and nothing around it. They wait to be told instead of bringing problems forward. They route around you to their actual boss. The status report stays green while the program quietly stops moving, because the people doing the work decided, reasonably, that you were someone to manage rather than someone to follow.

It is the same instinct as leading the room rather than answering it — and it connects to aligning competing interests, because you cannot align people you have first alienated by pulling rank you don't hold.

It ties back to the ledger

The program lands because two dozen people who didn't have to chose to make it land. Not because anyone was ordered, but because the lead was clear, credible, and made the right thing easy enough that doing it was the path of least resistance. That is the whole job, and it never appears in a plan. You lead the people you can't fire by being the person they would have followed without the title.