The projects I’m proudest of moving through a company, I moved without the power to make anyone involved do their part. The engineers reported to someone else. The salespeople had their own targets and their own boss. The people whose work I depended on could have ignored me, and on paper there was nothing I could do about it.
This is the normal shape of work. In any organization, the authority to make a binding decision can roll all the way up to the CEO. And yet the work gets done every day, at every level, by people who hold no such authority and don’t wait for it. If you wait for authority to line up behind you, you will wait forever.
That willingness to move is most of what separates people who lead from people who wait. This kind of leadership has nothing to do with seniority. Everyone in a company, at every level, has the chance to show it: you see a problem and go fix it, you see an opportunity and take it, rather than waiting to be told. But the people who try to do it by fiat, who start telling others what to do without the standing to back it up, learn fast that orders you can’t enforce get you nowhere.
The only way to get anything done without direct authority is to build consensus, and consensus is collaboration with a purpose. You build the idea together with the people who will have to carry it, until it belongs to all of them and not only to you. Do it well and people keep backing your projects, contributing to them, and showing up when you need them. It’s a craft, and it can be learned.
It always starts the same way. Someone has an idea, notices a problem, sees an opening. The temptation is to take that spark, work it into a finished plan on your own, and walk it straight to whoever can approve it. That is the slowest and least reliable path there is. When you present a finished idea cold, people respond to being sold to. They look for the flaws, they defend their own turf, they hold back rather than commit in front of others.
You don’t need a title for any of this. If the idea is yours and you sit three levels below anyone who could formally approve it, the path is the same. You bring a few peers and a couple of people above you along first, and you go forward together. Often you learn you never needed the approval at all. Enough people are already behind it, and it starts to happen.
The way you build that is one conversation at a time. Take the idea to a single person while it’s still forming. Bring it before it’s finished, because a half-formed idea, even one raised in a hallway with no materials at all, invites people to help shape it, while a polished plan invites only a verdict. A verdict is the last thing you want this early. What you want is their help, so you ask for it. When the person across from you can see the gaps, they reach in and start filling them, and the moment they add something, the idea becomes partly theirs too. People are invested in what they helped build.
You take their input, incorporate it into the plan, and, most importantly, you give them credit for it. Then you have the same conversation with the next person. An engineer sharpens the technical shape. A salesperson tells you why a customer won’t buy it as drawn. Someone in finance flags a cost you missed. Every conversation makes the idea better, and every one brings in another person who now has a stake in it.
By the time the idea reaches a formal decision, you’ve spoken with everyone who matters to it, one at a time. Each of them has left a fingerprint on it. The moment it gets presented for approval becomes a confirmation of something that already happened across those private conversations. You ask whether everyone’s on board, and they are, because they built it with you.
Two things make this work, and both run against instinct.
First, always work one person at a time. It’s tempting to batch, to pull a few people together and save yourself the calendar pain. Resist it. In a one-on-one, people can be candid. They will admit they’re unsure, ask the naive question, and float the half-formed thought, none of which they can do in front of a group without feeling like they’ve shown weakness. That candor is where the real collaboration happens, and collaboration is what creates ownership.
Second, give the credit away. When the idea comes up later, say out loud whose contribution made it better. This feels backward the first few times. You did the work, you drove it, and now you’re handing out authorship. The instinct says credit is a fixed pie and every slice you give away leaves you with less. The instinct is wrong. Credit you give away comes back as loyalty and momentum. The people you name become advocates in rooms you’ll never sit in. And the person who keeps making everyone around them look good becomes the one everyone wants on their project. That reputation compounds faster than any single idea you could have kept for yourself.
The same approach works when you need something from a team you don’t work with every day, one running hard on its own goals with no obvious reason to care about yours. The work here is to find where your goal and theirs overlap. Start by understanding what they’re trying to accomplish and what they’re measured on. Then bring your idea to them as something that helps them get there.
Say you need work from a team that has no goal attached to it. You don’t tell them they need one. You ask what they’re working toward, and you listen. Maybe you learn they’re under pressure on a number your idea would move. Now you have something to offer them, a way your idea helps with a problem they already own. That’s a conversation they want to have.
Some of this is about handling objections before they’re spoken, and this requires empathy. Put yourself in the other person’s chair and ask what would worry you in their position. Then raise it yourself, first. “The obvious problem here is the cost, and here’s how I’m thinking about it.” Or, “You’re going to worry the timeline is unrealistic, and you may be right, so let’s work through it together.”
This does two things, and both are about the relationship. It shows empathy, because you’ve taken their concerns seriously enough to name them before they had to. And it builds credibility, because the person willing to say out loud what’s weak about their own idea is far more trustworthy than the person insisting there’s nothing weak about it. Trust and shared goals are what you’re building. The agreement follows from them.
There’s a trap here to watch for. Pushback can be discouraging, but it’s what you really want. Just because people push back doesn’t mean there isn’t value in the idea. Everyone who tells you why your idea won’t work is giving you ammunition to adjust the idea in a way that will work. The hardest objections should come out in these conversations, while the idea can still change. Better to hear them now than after you’ve committed. You want the person who says the design won’t scale, or that the customer won’t pay. That resistance is how the idea gets stronger before it costs anything. And them feeling listened to, and you adjusting the idea to address their concern, is how they become an advocate, how they start being part of your team.
This process doesn’t end. The people who helped shape the idea, your informal working group, each have to build the same agreement inside their own worlds. The engineer has to bring the rest of engineering along. The salesperson has to win over the sales floor. The finance partner has to sell it up their own chain. Because they helped build the idea, they understand it from the inside, and they already know its weak points and how to answer them, since they raised some of those objections themselves. They leave your conversations with more than their agreement. They leave with what they need to go build consensus with the people you will never be in a room with. You pull them in early and give them real ownership for exactly this reason, so they become a group equipped to carry the idea further than you could reach on your own.
The production side of this work keeps getting easier. An LLM can help you draft the memo, run the analysis, and build the deck in a fraction of the time it used to take. The relationship building can’t be handed off. Sitting across from a skeptical colleague and earning their trust, finding the overlap between what you need and what they’re after, carrying an idea through one human conversation after another until a whole organization is behind it, that part stays yours. It’s the harder part, and the part worth getting good at. It’s also what leading without authority has meant all along.
Someday you may have authority, and you’ll discover that all these techniques and lessons are almost exactly the same at every level of your career. It’s all about building consensus, collaboration, and rallying people to solve a problem together. That never changes.
springload 