You were in the room. You made your case. You brought the data, the logic, the experience, and a clear-eyed argument for the path forward. And they still chose the other direction.
Now you have to walk out of that room, gather up your team, and go execute on something you genuinely believe is wrong.
What you do over the next 48 hours is going to decide more about your career than that decision ever could.
Most people get this part backwards. They go quiet and resentful, slow walking the work and waiting to be proven right. Or they relitigate the decision to anyone who will listen, which usually means peers, friends, the team, even family at the dinner table. Both of those are career killers, and senior leaders are watching every single move you make.
Here is the part nobody tells you. Your boss does not need you to be right. Your boss needs to know that when they make a call you do not agree with, you are still going to execute it like a professional, and stay close enough to the work to catch the issues before they get big. That is the skill that separates directors from vice presidents, and vice presidents from the C-suite.
What to Do When Your Boss Makes a Decision You Disagree With
| Quick answer: When your boss makes a decision you disagree with, you have a 48-hour window that matters more than the decision itself. The right move is to commit publicly, execute professionally, stay close enough to the work to spot issues early, and surface those issues with options instead of complaints. The wrong moves are going quiet, slow walking the work, or relitigating the call to anyone who will listen. |
Most leadership content focuses on how to lead the team underneath you. The reality is, once you are in director or vice president level roles, the harder problem is leading up the chain of command. How you handle being overruled by senior leadership is one of the clearest signals an executive team has about whether you are ready for the next role.
This is one of the most common patterns I see in my executive coaching practice. A high performing director loses an argument to senior leadership, then quietly damages their own reputation in the weeks that follow, without ever realizing they did it. The decision they disagreed with was rarely the actual problem. The aftermath was.
Why Your Boss Doesn’t Need You to Be Right: A Real-World Example
| Quick answer: Your boss does not need you to be right. They need to know that when they make a call you disagree with, you will still execute professionally and stay close to the work. That trust is what gets you invited into the next decision, and eventually, the next role. |
A few years back, there was an SVP who got hired to lead a massive acquisition and integration along with all of the support functions across the business. This was tough for me to process, because the person had never done anything like it before. And here he was, thrust into a senior leadership role with responsibility for an integration of that scale.
I had been through about 45 acquisitions and integrations at that point, so I did not agree with the decision, and I said so. I shared my thoughts, I shared the risks, I laid out my concerns about putting somebody who had never done this in charge of something that big.
It did not matter. The decision was made, and he was going to lead it.
This was when I checked my ego and I supported him in the best way I knew how. I walked into conversations with him and said things like, hey, I see what you’re doing here, but in my experience that is actually not how it gets received, they like seeing it this way, or this is what has worked in the past. None of it landed. He was trying to put his dent in the universe and do it his way, so I made peace with that and decided I was going to execute, period.
And that is exactly what I did. Anything and everything he needed, I did it. I made the trips, I built the relationships, I mapped out the processes, and what that did is it kept me close to the project.
After a few months, people started to notice and quietly ask, wait, why is he supposed to be the one running this, but Sean is the one actually making things happen? That picked up momentum. A few more months go by, and I will never forget this. I was on a private jet with the CEO heading to one of our locations, and she point blank looked at me and said, Sean, I need you to step in and fix this.
Yes ma’am. I will make it happen, whatever it takes.
I picked up and moved down to that city for about a year, and we got the integration across the finish line. Was it frustrating? Of course it was, but that is exactly what real leadership looks like, and it is the kind of leadership that quietly builds the case for your next role while everybody else is busy looking for credit.
Three Common Mistakes Leaders Make After Being Overruled
| Quick answer: The three most common mistakes leaders make after being overruled by their boss are: pushing back with feelings instead of outcomes, treating the decision as a personal loss, and implementing the decision while mentally checking out. Each one quietly costs you executive trust, and most leaders do not realize it is happening until promotions stop coming. |
When directors and VPs hit a moment where their boss made the wrong call, I usually see them fall into one of three patterns. Each one will quietly cost you the next promotion, and most people do not even realize it is happening.
Mistake 1: Pushing Back With Opinions Instead of Outcomes
| Quick answer: Pushing back on your boss with opinions sounds like, I do not think this is a good idea. Pushing back with outcomes sounds like, here are the three options, here are the tradeoffs, and here is what I recommend. Executives move on tradeoffs and risk, not on feelings. |
This is when you walk in and say things like, I do not think this is a good idea, or I am not comfortable with this direction. That is not a case, that is a feeling, and executives do not move on feelings. They move on tradeoffs and risk.
The fix is to come in with data, not discomfort. Frame the cost of their path, frame the cost of your alternative, and put it in front of them. Walk in and say, here is what I am seeing, we have options A, B, and C, my recommendation is A, here is why, and here are the risks associated with B and C, how would you like to proceed? Then let them decide, because at the end of the day they are the ones responsible for the call. Your job is not to police the decision, and your job is not to veto it. Your job is to give them the clearest picture you possibly can, and then execute against the decision they make.
Mistake 2: Treating “No” as a Personal Loss
| Quick answer: When the decision goes against you, the test is not whether you were right. The test is whether you can disagree privately and still commit publicly. Senior leaders are watching how you handle losing more closely than how you handle winning. |
When the decision does not go your way, you have two common bad responses. You either go quiet and resentful, head down, and then carry that energy back to your team like, well, this is what we’ve got to do, which inspires absolutely nobody. Or you keep relitigating it, looking for the moment to say I told you so.
Senior leaders are watching how you handle losing. The fix is simple to say and hard to live, which is that you can disagree privately, but once a decision is made, you commit to execution and you support it publicly. Your team is watching, your peers are watching, and when things start to wobble, the rest of the leadership team usually knows exactly who made the call and who is doing their best to make it work. They might not say it out loud, but they see it, and they remember it when the next opportunity comes around.
Mistake 3: Implementing the Decision and Mentally Checking Out
| Quick answer: Implementing without engaging is the most expensive failure mode. By the time the cracks become visible, the damage is done, and saying I told you so afterward gets you nothing. The fix is loyal dissent: execute, stay close to the work, define your warning indicators in advance, and raise the flag early with options. |
This is the most expensive one of the three. You did what was asked, you did the bare minimum, you did not actively watch for cracks or warning signs, and by the time the problems surfaced the damage was already done. Then you wanted to scream, I told you so. Nobody cares. What people care about is results.
I will admit that early in my career, this was the failure mode I struggled with. I would still technically do the work, but I would make the snide comments, hedge my effort, and wait for the thing to fall apart. It did not serve the team, it did not serve the company, and it absolutely did not serve me. People started saying things like, Sean can get things done, but if he does not agree with you, good luck. That was an awful reputation to carry, and I had to fix it.
The fix is what I now call loyal dissent. You execute, and you stay close. Before you start, write down two or three indicators that would tell you the thing is going sideways, and then actively watch for them. When one of them shows up, raise your hand early, raise it professionally, and bring options. Your job is to make the pull the plug moment easier for the people above you, not harder.
How to Practice Loyal Dissent: A Framework for Executing What You Disagree With
| Quick answer: Loyal dissent is a four-step approach for executing a decision you disagree with: commit publicly, define your warning indicators before you start, stay close enough to the work to see them, and raise the flag early with options instead of complaints. Done well, it builds more executive trust than being right would have. |
Loyal dissent is not silence, and it is not compliance. It is a deliberate practice that lets you honor the decision while staying useful to the leaders who made it. There are four moves that matter:
- Commit publicly to the decision. Your team and your peers need to see you carrying the call forward as if it were your own.
- Define your warning indicators before you start. Write down two or three signals that would tell you the plan is going sideways, and decide what you will do when you see them.
- Stay close to the work. This is the difference between executing and being merely compliant. You cannot raise the flag early if you are not watching the field.
- Raise the flag with options, not complaints. When the warning indicators show up, walk back into the room with two or three paths forward and the tradeoffs of each.
Done consistently, loyal dissent builds more executive trust than being right ever would have, because it tells the people above you that they can hand you a hard call and trust that you will protect them and the business while you carry it out.
How Leading Up the Chain of Command Moves You From Director to Vice President
| Quick answer: Leading up the chain of command is the skill that separates directors who get promoted from directors who plateau. Once you are in director or VP-level roles, the ceiling is rarely your team. The ceiling is how senior leaders perceive your judgment, your composure, and your ability to execute decisions you disagree with. |
A lot of the leadership content out there focuses on how to lead down through the organization, and those skills matter, absolutely. But once you make it into director and vice president level roles, the real ceiling is who is above you, not who is below you. You have to learn how to lead up. You have to learn how to navigate difficult conversations and impossible situations, even when you know in your bones that the whole thing is about to blow up. You still have to execute.
This is the work I focus on every day in my executive coaching practice. The directors and VPs I work with are technically excellent. They are not stuck because they do not know their function. They are stuck because the executive team above them does not yet see them as a peer, and the fastest way to change that perception is to get exceptionally good at handling the moments where you disagree.
Your boss does not need you to be right. Your boss needs you to be useful when they aren’t.
Three Reflection Questions for Senior Leaders
The last time you disagreed with a decision from above, did you make your case with outcomes, or did you make it with opinions? Did you bring data, logic, and tradeoffs into the room, or did you lean into how you felt about it?
When the decision did not go your way, did you actually commit to it, or did you hedge? Were you finding ways to slow walk the work and wait for your moment to say I told you so?
And right now, today, are you close enough to the execution to catch the warning signs before they actually become problems? Because if you are not, you are not really executing, you are just compliant, and there is a meaningful difference between the two.
Work With an Executive Coach Who Has Lived This
If any of this is hitting close to home, this is exactly the work I do every day with directors and vice presidents who are ready to lead up the chain of command, not just down. Wolf Executives is built around executive advocacy for senior leaders in Houston and across the country who are ready to make the leap to the next role. Send me a message and let’s have a conversation about what is actually getting in the way.
Frequently Asked Questions
What should you do if your boss makes a decision you disagree with?
Commit publicly to the decision, execute it professionally, and stay close enough to the work to spot issues early. If you see warning signs, raise the flag with options, not complaints. Going quiet, slow walking the work, or relitigating the decision to peers will quietly cost you executive trust.
How do you push back on your boss professionally?
Push back with outcomes, not opinions. Walk in with two or three options, the tradeoffs of each, your recommendation, and the reasoning behind it. Then let your boss decide. Your job is to give them the clearest picture possible, not to police or veto the call.
What is loyal dissent in leadership?
Loyal dissent is the practice of disagreeing with a decision privately, committing to it publicly, executing it professionally, and staying close enough to the work to surface problems early with constructive options. It is the opposite of malicious compliance, and it is one of the most reliable signals of executive readiness.
How do you lead up the chain of command?
Leading up means handling disagreement with senior leaders in a way that protects them, the business, and the team. It includes framing recommendations in tradeoffs and risk, supporting decisions publicly even when you disagree, staying composed under pressure, and making the hard moments easier for the people above you, not harder.
Why do directors get stuck before the VP promotion?
Most directors get stuck not because they are bad at running their function, but because the executive team does not yet see them as a peer. The two skills that change that perception fastest are leading up the chain of command and handling disagreement well, especially in moments where they were overruled.
Where can I find executive coaching in Houston?
Wolf Executives is a Houston-based executive coaching practice focused on helping directors and senior leaders advance to vice president and C-suite roles. Coaching engagements are available in Houston in person and virtually for clients across the country.
About the Author
Sean Barnes is the founder of Wolf Executives, a Houston, Texas based executive coaching and leadership development practice. He has roughly 20 years of progressive leadership experience, having led functional teams across IT, Human Resources, Project Management, ESG, Safety, Transportation, and Leadership Development. Sean has been part of 48 acquisitions and integrations and two IPOs, and now coaches directors and vice presidents who are working to advance to the next senior leadership role.
Connect: LinkedIn (Sean Barnes), wolfexecutives.com
