How to Communicate a Leadership Decision You Don't Agree With
A couple of weeks ago, a client brought a set of notes to our session. She had not written them, she had not been consulted on what was in them, and she was expected to deliver them to her teams right away.
She is a director at a tech company, based in the UK and responsible for EMEA operations. The notes set out a reorg that leadership at the US headquarters had decided on without involving her or any of her peers, and the change was taking effect immediately.
She was upset. She had no say in the decision, she didn't agree with it, and she agreed even less with how it was going to be implemented. She told me she felt like a soldier being handed orders, and that the whole thing felt like a violation.
She knew she could stand up in front of her team and act as if she supported it, but she didn't want to. It didn't sit right with her, and she was honest enough to say she's not a good actress and her team would know. She came to our session asking how she was supposed to communicate it at all.
I have heard some version of this story from clients many times since. A senior manager at a global consumer goods company told me she rehearsed her team announcement eleven times and still could not get through the second sentence without her voice changing. A director in financial services described himself as "the human shield" for a decision he thought would cost the business its best people. Both of them were good at their jobs. Both of them felt, for a few weeks, like frauds.
This situation comes up in my coaching practice more often than most people would guess, and leaders tend to shy away from discussing it with their peers because it can feel disloyal to the people above them, or like admitting they have less influence than they are supposed to have. Below I look at what the research says about why it is so difficult, and at some practical ways to approach the conversation with your team.
Why It's So Hard to Communicate a Leadership Decision
When you disagree with a decision you have to deliver, you are holding two loyalties at once. One is to the people above you who made the call. The other is to the people below you who will live with it. Most of the time those two loyalties sit comfortably together. In this moment they pull in opposite directions, and you are the one standing in the gap.
The stakes of how you handle it are higher than most leaders assume. Gallup estimates that managers account for at least 70% of the variance in employee engagement across business units. Your team will take its cue on this decision far more from you than from the all-hands email.
There is also good news in the research. In their Harvard Business Review article "Fair Process: Managing in the Knowledge Economy", W. Chan Kim and Renée Mauborgne studied how people respond to decisions across 19 companies. They found that people care a great deal about how a decision was made, often more than about the decision itself. According to Kim and Mauborgne, fair process rests on three things:
Engagement, meaning people affected by a decision had a chance to give input and challenge assumptions
Explanation, meaning everyone understands the reasoning behind the final call
Expectation clarity, meaning people know what is expected of them once the decision is made
When managers felt these were missing, the authors observed them holding back ideas and slowing things down. When they were present, people committed to decisions they had argued against.
The broader research on procedural justice says something similar. Studies going back decades show that perceived fairness of the process helps people accept outcomes that are less favorable than they hoped for, and that people care about process most when they do not get the outcome they wanted.
This means you have more influence than you might think, because even when the decision itself is out of your hands, a lot of what makes it feel fair to your team is still in them.
What Usually Goes Wrong in Leadership Communication
In my coaching practice I see leaders fall into one of three patterns. Most of us have a default, and it tends to show up under pressure.
The distancer. "Leadership has decided..." The decision is delivered as something that happened to the team and to you. It feels honest in the moment and protects your relationships in the short term. Over time, it tells your team that you have no influence upstairs, and they stop bringing things to you.
The performer. You present the decision with full enthusiasm and hide every reservation. People can usually tell. When the enthusiasm does not match what they see in your face or hear in your voice, they stop trusting the message and start reading the subtext instead.
The leaker. You say the right things in the meeting and then, in the one-to-ones or over coffee, you let people know what you really think. This one feels the most human and does the most damage, because it splits the team into those who heard the real version and those who did not.
Amazon made "disagree and commit" famous through Jeff Bezos's 2016 letter to shareholders, where he describes greenlighting an Amazon Studios project he had doubts about and telling the team he hoped it would become their most watched show. The phrase gets quoted a lot. In practice I find that leaders often skip the disagree part, or do it so quietly that nobody above them registered it, and then struggle with the commit part because they never felt heard.
How to Communicate Well
Make sure you have actually disagreed, upstairs and on the record. Before you say a word to your team, check whether the people who made the decision know where you stand and why. If you raised a concern once in passing, I would go back and raise it properly. Something like "I want to be clear that I have reservations about this, and here is what I am worried about. I will support it, and I want you to know the risks I see." This makes the commit part much easier, because you are no longer carrying an argument you never got to have.
Understand the reasoning well enough to explain it fairly. You cannot give your team a good explanation if you only understand your own side. Ask the decision makers what they weighed, what alternatives they rejected and why. A client of mine, a senior leader at a global tech company, found that once she understood the cost pressures behind a hiring freeze she still disagreed with it, but she could explain it without sounding like she was reading a script.
Separate your view from the decision, and be honest about which is which. You do not owe your team your full opinion, and you also do not need to pretend you have none. I think the most credible version sounds something like "This was not the call I would have made, and I made my case. The decision is made, and here is why it was made. I am going to put my energy into making it work, and I would like your help with that." Say it once, plainly, and then move on to what happens next. A few years after it happened, someone who used to report to me at the time came up to me and brought up a conversation I had had with our team. A cross-functional colleague we worked closely with had been let go. They were very productive and had great relationships across the team, and I did not agree with the decision or with how it was carried out. She told me how encouraging it had been to hear me say in a team meeting where I announced their departure that I saw it as a big loss, and to be asked whether anyone had thoughts on it or anything they wanted to say. I never spelled out my disagreement or criticized the decision. I made my view clear, respected that the decision had been made, and spent most of that conversation on what came next and who would take on which pieces of work. I also made sure the team knew it was still safe to speak up, even after watching someone who they loved and respected be let go.
Spend most of the conversation on what changes for them. This is Kim and Mauborgne's expectation clarity, and it is the part leaders tend to rush. People want to know what this means for their role, their workload, their targets, their next six months. If you do not know yet, say so and give them a date by when you will (for example, "I do not have the answer on team structure yet, I will come back to you by the 15th").
Give people room to react, and keep listening after the meeting. Someone will be angry, someone will be quiet, and someone will ask the question you were dreading. Let that happen in the room rather than pushing it into the corridor. In the weeks after, check in individually. Possibly the most useful question you can ask is "What would make this easier for you to work with?" because it gives you something concrete to take back up.
Know where your line is. Most decisions you disagree with are judgment calls where reasonable people differ, and for those, disagree and commit is the right approach. A small number are different, such as decisions that you believe are unethical, unsafe, or that you could not defend to your team in good conscience. Those call for a different conversation, with your manager, with HR, or with yourself about whether this is still the right place for you. It helps to know in advance which kind of decision you are dealing with.
A Few Questions to Take With You
If you are facing one of these conversations right now, I would not expect yourself to feel comfortable with it. Discomfort is a fairly reasonable response to being asked to stand behind something you argued against. What helps is being clear with yourself before you walk into the room.
So before your next team meeting, you might ask yourself:
Have I made my case to the people who decided, clearly enough that they would be able to repeat it back?
Can I explain their reasoning in a way they would recognize as fair?
What does my team most need to know about what changes for them, and when?
Is this a decision I can commit to, or is it one where I need to have a different conversation?
And when this is behind us, what do I want my team to remember about how I handled it?
A conversation like this is rarely going to feel good, for my client or for most leaders I work with in her position, but it can be handled in a way you are comfortable standing behind afterwards. That usually means being honest that you had a different view, explaining the decision as fairly as you can, and then giving your team the clarity they need to get on with their work. None of it requires you to perform an enthusiasm you do not feel, and in my experience teams tend to trust a leader more when they can see that the support is genuine even where the agreement is not.
Hi! I'm Merve. 👋 I help leaders build high performing teams, amplify their business impact, and advance their careers.
Here are five ways you can connect with me:
Book a 1:1 Coaching Session: Tailored to your individual goals, I offer in-depth guidance, a focused strategy, and results-oriented accountability to help you navigate your professional and personal challenges, including difficult conversations like delivering a decision you disagree with.
Join Signature Leadership Programs: Designed for corporate leaders and business owners at all stages of the leadership journey, these programs blend 1:1 coaching with group workshops and training, equipping you to grow your career, earnings, and business success.
Subscribe to My FREE Monthly Newsletter: Stay updated with the latest in leadership and business with insights and musings delivered directly to your inbox.
Access FREE Worksheets for Leaders: Visit my website to access and download worksheets and workbooks that provide practical exercises for enhancing self-awareness, self-reflection, and fostering positive change in your leadership and team dynamics.
Follow me on LinkedIn: Connect with me on LinkedIn for daily updates, thought-provoking articles, and a community of like-minded professionals committed to continuous growth and leadership excellence. Join the conversation and stay inspired on your leadership journey.
