Because support isn’t something you get after a decision. It’s something you design into how it’s made.
Most leaders treat support as something that happens after a decision.
The decision is made. The announcement is crafted. The communication goes out. And then — through the right tone, the right framing, the right messaging — people are persuaded to support it.
That model is backward.
Support isn’t manufactured after the fact. It’s built into the process — through how the decision is made, who is involved, what information people have when they hear about it, and how clearly the decision is connected to the reality of the people it affects.
When the process is right, the communication almost takes care of itself. When the process is wrong, no communication will fully compensate.
Why decisions don’t get the support leaders expect
Most decisions that fail to gain support don’t fail because they’re wrong.
They fail because of how they arrived.
People received a decision that felt like it was made about them rather than with any understanding of their reality. They heard the rationale after the decision was final rather than as part of the process that shaped it. They experienced the announcement as managed — designed to minimize resistance rather than genuinely communicate. And they had no way to know whether the concerns they had were ones the decision-makers had considered.
All of these experiences produce the same outcome: skepticism. Not necessarily about the decision itself, but about the process that produced it. And skepticism about process is more corrosive than disagreement with direction — because it doesn’t just affect this decision. It affects every subsequent one.
When people trust the process — when they believe decisions are being made thoughtfully, with genuine consideration of their reality, and communicated honestly — they support decisions they don’t fully agree with. When they don’t trust the process, they resist decisions they might otherwise have accepted.
The goal isn’t unanimous agreement. It’s sufficient trust in the process that disagreement doesn’t produce disengagement.
The five things that actually produce support
1. Involving people at the right level before the decision is final
Involvement doesn’t mean giving everyone a vote. It means ensuring that the people most affected by a decision have had a genuine opportunity to contribute their perspective to the thinking that shapes it — before the decision is final.
That distinction matters enormously. Consultation that happens after a decision is made — where people are informed of a direction and asked for their thoughts about implementation — is not the same as consultation that happens during decision-making. The first is process management. The second is genuine input.
People can distinguish between the two. Immediately. And the experience of being consulted after the fact — of having their input solicited in a process that wasn’t going to change regardless of what they said — produces more resentment than not being consulted at all. Because it adds the experience of having their time wasted to the experience of not having been genuinely heard.
Real involvement — even limited, even at a single representative level — before a decision is final changes the organizational experience of that decision. Not because the input necessarily changes the outcome, but because the process of being genuinely heard changes how the outcome is received. (For how to build genuine alignment during this process, read The Difference Between Alignment and Agreement.)
2. Being honest about the constraints
One of the most consistent generators of unsupported decisions is the gap between how much latitude people think they have and how much they actually have.
When a leader invites input on a decision that is actually significantly constrained — by budget, by regulatory requirements, by strategic imperatives that aren’t fully disclosed — and doesn’t disclose those constraints, people contribute input in good faith and experience disappointment when their contributions don’t change the outcome. Not because the decision was wrong. Because the process felt dishonest.
Disclosing constraints isn’t weakness. It’s respect. Telling people “we’re making this decision within these parameters, and here’s where there’s genuine room for input” is more respectful than inviting unlimited input into a constrained process without being honest about the constraints. People can engage more productively with a real process than with a false one.
When constraints are named honestly, input becomes more useful — focused on the genuine decisions rather than the predetermined ones. And when the decision is made, the people who contributed understand why it looked the way it did.
3. Communicating the rationale before the decision
Most decision communications are structured the wrong way.
They announce the decision first — what has been decided — and then explain the rationale. This structure puts people in a defensive position before they’ve heard the reasoning. They’ve already received the outcome. Now they’re evaluating whether the justification is sufficient.
Structuring it the other way — beginning with the problem being solved, the criteria being used to evaluate options, and the trade-offs being considered — puts people in a different position. They’re receiving the reasoning before they know the conclusion. They can evaluate the logic rather than defensively processing the outcome.
This isn’t a manipulation. It’s an accurate reflection of how good decisions are actually made — by identifying a problem, evaluating options, making trade-offs, and arriving at a conclusion. Communicating in that sequence gives people access to the actual thinking rather than just the result of it. And decisions that people understand the thinking behind are decisions they’re significantly more likely to support — even when they would have preferred a different outcome.
4. Naming what was considered and why it was rejected
Support often breaks down not because people disagree with the chosen direction but because they don’t know whether their preferred alternative was considered.
When a decision is announced without acknowledging the alternatives that were evaluated, people who had a different preference don’t know whether their view was considered and found wanting or simply not considered at all. Both feel like being dismissed — but one is at least an honest dismissal, and the other suggests the process was incomplete.
Naming the alternatives that were evaluated and the reasons they were not chosen does something specific. It tells people who had a different preference: we thought about what you would have suggested, and here’s why we went a different direction. That acknowledgment — even when the conclusion is not what they wanted — produces more support than simply announcing a direction without reference to alternatives.
It also makes the rationale more credible. A decision that acknowledges and addresses the obvious counterarguments is more convincing than one that ignores them — because it signals that the decision-makers have genuinely wrestled with the question rather than simply reached a comfortable conclusion.
5. Making the personal connection explicit
Most decision communications explain what has been decided and why it makes sense for the organization. Very few explain what it means for the specific person receiving the communication.
But people don’t process decisions at the organizational level. They process them at the personal level — what does this mean for my work, my role, my team, my day-to-day experience. Until that question is answered, everything else is abstract.
When decision communications explicitly address the personal level — when they answer not just “what did we decide and why” but “what does this mean for you specifically” — they remove the most common source of resistance to supported decisions.
Not resistance to the direction. Resistance to uncertainty about personal implications. The decision might be entirely reasonable. But if people leave the communication not knowing what it means for them, they’re going to fill that gap — and the gap fills faster with anxiety than with anything else. (For how to build that personal connection into every message, read How to Write a Change Message People Actually Read.)
What support actually looks like — and what it doesn’t
Support is frequently confused with agreement and enthusiasm. It’s neither.
Agreement is “I would have made the same decision.” Most decisions in complex organizations will not produce agreement. People have different information, different priorities, and different perspectives. Expecting agreement is expecting something that organizations can’t reliably produce.
Enthusiasm is “I’m excited about this direction.” Some decisions are genuinely exciting. Many are not — they’re pragmatic, difficult, or disruptive in ways that warrant acknowledgment rather than celebration. Performing enthusiasm in the face of decisions that don’t warrant it produces the wrong tone, which reads as tone-deafness and undermines the credibility of the communication.
Support is something more modest and more durable than either. It’s “I understand why this decision was made, I believe the process was legitimate, and I’m willing to work within it even if it wasn’t my preferred outcome.”
That’s achievable. It doesn’t require everyone to love the direction. It requires them to trust the process enough to follow it.
The decisions that will never get full support — and how to handle them
Some decisions will never be universally supported. Decisions that eliminate roles. Decisions that significantly disrupt established ways of working. Decisions that involve trade-offs where some people benefit and others don’t.
For these decisions, the goal isn’t universal support. It’s adequate support — enough for the decision to be executed effectively, enough for the people who are most affected to feel respected even when they’re disappointed.
Adequate support for difficult decisions comes from three things: honest acknowledgment of what the decision costs the people most affected by it, clear explanation of why those costs are being accepted — what the organization is gaining that justifies them — and genuine care for the people who bear the heaviest burden of the decision.
The last one is the most important and the most frequently absent. Organizations that make difficult decisions without genuine care for the people most affected produce the bitterness that outlasts the decision itself. Organizations that make difficult decisions with genuine care — that acknowledge the impact honestly, provide real support for those most affected, and treat difficult news with the dignity it warrants — produce a different response.
Not happiness about the decision. Respect for how it was handled.
And respect, even in the hardest moments, is what makes the relationship between leaders and organizations resilient rather than brittle. (For how to communicate difficult decisions with genuine care, read How to Communicate Bad News Without Losing Trust.)
What this looks like in practice
I worked with a leadership team preparing to announce a significant operational consolidation — the kind of decision that would affect roles, locations, and reporting structures for a large portion of the organization.
The initial communication approach was standard: announce the decision, explain the business rationale, acknowledge the impact briefly, and provide information about next steps and support resources.
When we worked through the five elements, several gaps became clear. The rationale was being communicated after the decision rather than as the framing for it. The alternatives that had been evaluated — including options that would have been preferred by the most affected groups — weren’t being mentioned. And the communication addressed the organizational impact but not the personal one — what this meant for different roles in different locations wasn’t being translated.
We rebuilt the communication structure. The problem being solved came first — the honest account of what the current structure was costing the organization and why maintaining it was no longer viable. The alternatives that had been considered came next — including the acknowledgment that a less disruptive option had been evaluated and the specific reasons it was found insufficient. Then the decision. Then the personal implications by audience group. Then the support available.
The response to the announcement was not positive — because the decision itself was genuinely difficult. But the feedback from managers cascading the communication was consistent: employees were angry about the decision and they felt the communication was honest. That separation — frustration with the outcome, respect for the process — is the best outcome available from a genuinely difficult decision.
It’s also the outcome that makes recovery possible.
Final thought
Support for decisions isn’t manufactured by communication.
It’s built into the process — through genuine involvement before the decision is final, honest disclosure of constraints, rationale communicated before conclusion, acknowledgment of alternatives considered, and personal connection made explicit.
When that process is right, communication expresses a decision that people are prepared to support.
When it isn’t, no communication will produce the support that the process failed to build.
The leaders who consistently make decisions people support are not the ones who are most persuasive. They’re the ones who design the process well enough that persuasion is rarely required.
FAQs: Making decisions people will support
Usually because of how the decision arrived rather than what was decided. People received a decision that felt made about them rather than with genuine understanding of their reality. They heard rationale after the fact rather than as part of the process. They experienced the communication as managed rather than honest. And they had no way to know whether their concerns had been considered. These process failures produce skepticism that affects not just the specific decision but every subsequent one.
Agreement is “I would have made the same decision.” Support is “I understand why this decision was made, I believe the process was legitimate, and I’m willing to work within it even if it wasn’t my preferred outcome.” Agreement is unreliable in complex organizations because people have different information and perspectives. Support is achievable when the process is honest and the communication is clear. Leaders who aim for agreement consistently disappointed; leaders who aim for support consistently surprised by how much they receive.
Before the decision is final — at a level that reflects the actual degree of input available. Consultation after a decision is made is process management rather than genuine involvement, and people can distinguish between the two immediately. Even limited, representative involvement before a decision is final changes how the outcome is received — not because the input necessarily changes the conclusion but because the experience of being genuinely heard changes how the conclusion is processed.
Because support often breaks down not because people disagree with the chosen direction but because they don’t know whether their preferred alternative was considered. Naming what was evaluated and why it was rejected tells people whose preference was different: we thought about what you would have suggested. That acknowledgment — even when the conclusion isn’t what they wanted — produces more support than announcing a direction without reference to alternatives, because it signals that the process was genuinely thorough rather than simply comfortable.
By aiming for adequate support rather than universal support — enough for the decision to be executed effectively, enough for the people most affected to feel respected even when they’re disappointed. Three things produce adequate support for genuinely difficult decisions: honest acknowledgment of what the decision costs the people most affected, clear explanation of why those costs are being accepted, and genuine care for the people who bear the heaviest burden. Not happiness about the decision — respect for how it was handled.
Announcing the decision before explaining the rationale. This puts people in a defensive position before they’ve heard the reasoning. Structuring the communication the other way — beginning with the problem being solved, the criteria used, and the trade-offs considered — gives people access to the actual thinking rather than just the result. Decisions that people understand the thinking behind are significantly more likely to be supported, even when the outcome isn’t what they would have chosen.
The Clarity Framework™ structures decision communication around the principles that produce support rather than just awareness. The diagnose principle identifies where the gap between the decision and the organizational experience of it is widest. The define principle builds the narrative that frames the problem before the conclusion. The deliver principle addresses the personal connection — what the decision means for specific people — that most decision communications skip. And the measure principle tests whether the decision has been genuinely understood rather than just formally announced.
Ana Magana is a change management and communications strategist based in Calgary, Alberta. She helps organizations make decisions that land — through communication designed to build support, not just announce direction.
Making a difficult decision and not sure how to communicate it? Work with Ana →
Related reading: The Difference Between Alignment and Agreement → Why Clarity Matters More Than Consensus → How to Communicate Bad News Without Losing Trust →