How to influence decisions when you have no formal authority
March 18, 2026
At the junior level, you do good work and tell your manager about it. At the senior level, you shape decisions, align stakeholders, and move organizations, most of which involves people who don't report to you and are under no obligation to do what you suggest.
This is where smart, high-performing people get stuck. They have the right ideas. They can't get them adopted.
Here's what works.
Why formal authority is overrated
People with formal authority can tell others what to do. What they can't do is make people want to do it well.
Influence without authority, building genuine buy-in, aligning interests, communicating in a way that makes people want to engage, produces better outcomes than mandates, even for people who have mandates available to them. The best leaders, the best consultants, the best cross-functional collaborators develop this skill deliberately.
The foundation: understand what everyone actually wants
The most common mistake in influence attempts is leading with your solution before you understand the other person's goals, concerns, and constraints.
If your proposal requires the engineering team to add two weeks to their sprint, and you haven't first understood what they're already prioritizing and what's driving those priorities, your proposal won't land. Not because it's wrong, but because it doesn't account for what's real for them.
The first step of any influence conversation is listening, not presenting.
Useful questions: - "What are the biggest pressures on your team right now?" - "What would make this kind of change difficult from your side?" - "What does a win look like for you here?"
These aren't manipulative. They're how you get the information you need to make a proposal that's actually viable.
Credibility is influence capital you spend and build
People follow people they trust. Trust, in a professional context, is built from:
Competence: you know what you're talking about Track record: you've been right before Reliability: you do what you say you'll do Good judgment: you acknowledge tradeoffs and limitations
The last one is underrated. The person who says "this approach has a real downside. Here's how I think we should address it" is more trusted than the person who presents every proposal as if it has no flaws. Acknowledging reality is a credibility builder, not a credibility cost.
If you're new to an organization or relationship, you don't have much credibility capital yet. You build it by delivering on small things, being honest about uncertainty, and demonstrating that your interests align with the broader team's interests, not just your own.
The structure of an influence conversation
Start with shared goals
Find the common ground before you get into the specifics of what you're proposing.
"We're all trying to ship before Q3 without burning out the team" is a statement most people can agree with. Starting here establishes that you're working toward the same thing they are, which changes the dynamic of the conversation from adversarial to collaborative.
Frame the problem before the solution
Tell people why something matters before you tell them what to do about it.
"Our current design review process is creating a two-day lag between ready-to-implement and ticket-created, which is compressing sprint planning" is a problem statement. It's observable and most people in the room can validate it.
Once people agree on the problem, they're much more open to your proposed solution, because they're now thinking about solutions alongside you rather than evaluating whether your solution is worth the disruption it requires.
Make the ask specific and easy to say yes to
Vague influence attempts fail. "We should probably do something about this" is not an influence attempt. It's a complaint.
A specific ask: "I'd like to run a two-sprint experiment where design reviews are done on Mondays and tickets created by Wednesday. Can I have your sign-off to try that?"
A specific ask makes it possible to say yes or no. It also demonstrates that you've thought through the implementation, which builds credibility.
Handle objections with curiosity
When someone pushes back on your proposal, the instinct is to defend it. Resist this.
Instead: "That's a fair concern. Tell me more about what's driving it."
This does two things. It gives you information you need to adapt your proposal. And it signals to the other person that you're actually listening, not just waiting for them to stop talking so you can make your case again.
If the objection has merit, update your proposal. If it doesn't, explain clearly why. Never dismiss an objection. Dismissing objections is how influence conversations turn into arguments.
Coalition-building: the organizational version
The most effective influence campaigns don't happen in a single meeting. They happen over a series of one-on-one conversations where you understand objections, adapt your proposal, build support one person at a time, and then bring the proposal to the group when you already have enough agreement to make it viable.
This feels slow. It's actually faster than trying to win a room cold.
Before any high-stakes proposal: - Identify the key stakeholders and decision-makers - Meet with each one individually, in advance - Understand their concerns and incorporate them where possible - Know where you have support and where you'll face resistance
By the time you're in the room, you're confirming decisions that have largely already been made, not trying to make them.
When your influence attempt fails
Sometimes you do everything right and the answer is still no.
This is okay. Your goal isn't to win every influence attempt. It's to be the kind of person whose influence attempts are taken seriously. That reputation is built over time, not in a single conversation.
When you lose: ask for the reasoning, acknowledge it, and ask what it would take to revisit it in the future. This signals maturity and keeps the door open.
Put it into practice
Try a free communication drill. Type your response, get AI feedback on clarity, confidence, and structure — no signup needed.
Try a free drill →