One of the most expensive assumptions leaders make is believing that good ideas should be enough.
On paper, the logic feels difficult to argue with. If a recommendation is commercially sound, strategically aligned and supported by evidence, people should support it. Organisations are full of intelligent professionals making rational decisions. Strong ideas should naturally gain traction.
Yet anyone who has spent time inside a large organisation knows reality rarely works that way.
Every experienced leader has lived through some version of the same story. A project that seemed certain to gain approval suddenly stalls. A well researched recommendation encounters unexpected resistance. A sensible initiative becomes trapped in endless discussions despite its obvious value. From the perspective of the person leading the work, the situation often feels irrational.
The recommendation makes sense.
The business case is strong.
The benefits are clear.
So why isn't anybody buying in?
Over the years, I've discovered that most leaders answer this question incorrectly. They assume resistance is caused by disagreement with the idea itself. As a result, they respond by producing more analysis, gathering additional data or strengthening the recommendation. The harder they push, the more resistance they often encounter.
The issue is that stakeholder support is rarely created through logic alone.
Several years ago, I worked with a senior leader responsible for a significant operational transformation programme. The initiative had the support of the executive sponsor, the projected benefits were substantial and the implementation plan had been carefully developed. From a project perspective, everything appeared to be in place.
Yet progress was painfully slow.
Meetings generated more questions than answers. Stakeholders appeared supportive in public but hesitant in private. Decisions that should have taken days were taking weeks. Frustration across the programme continued to grow.
Eventually, we stepped back and looked beyond the project itself.
What became obvious almost immediately was that the challenge had very little to do with the quality of the recommendation. The challenge was that different stakeholders were evaluating the proposal through completely different lenses.
Operations leaders were concerned about disruption.
Finance leaders were focused on risk.
Commercial teams worried about customer impact.
Several senior stakeholders were privately questioning whether the organisation had the capacity to deliver the programme successfully.
The recommendation had not failed.
The stakeholder landscape had simply never been fully understood.
This experience reinforced something I have observed repeatedly throughout my career. Most leaders think stakeholder management is about communicating more effectively. In reality, effective stakeholder management begins with understanding before communication ever takes place.
The leaders who consistently gain support for important initiatives spend remarkably little time trying to convince people.
Instead, they spend time trying to understand them.
They understand what different stakeholders care about. They understand where concerns are likely to emerge. They understand how previous experiences influence current perceptions. Most importantly, they recognise that stakeholders are rarely evaluating a recommendation from the same perspective as the person presenting it.
This sounds obvious.
In practice, it changes everything.
I remember working with an executive who consistently gained support for complex initiatives despite operating in an environment filled with competing priorities and strong personalities. Watching him work was fascinating because he rarely tried to persuade anyone. In fact, he often spoke less than everybody else.
What he did exceptionally well was ask questions.
Before presenting a recommendation, he would spend time understanding how different stakeholders viewed the issue. He wanted to understand what success looked like from their perspective. He wanted to know what concerns they had. He wanted to identify potential objections before they appeared in formal discussions.
By the time a recommendation reached an executive meeting, very little of the influencing work remained.
Most of it had already happened.
This is where many leaders misunderstand influence.
They assume influence happens during the meeting.
In reality, influence is often established before the meeting begins.
The presentation may be where the decision is formally made, but stakeholder confidence is usually built through dozens of smaller interactions that occur long beforehand. Informal conversations, relationship building, credibility and trust frequently play a greater role than anything that appears on a presentation slide.
Trust, in particular, is often underestimated.
When stakeholders trust a leader's judgement, they become more willing to support recommendations despite uncertainty. When trust is absent, even strong ideas face resistance. This explains why two leaders can present remarkably similar recommendations and receive completely different responses.
The difference is rarely the recommendation.
The difference is confidence.
Stakeholders are constantly asking themselves questions that never appear on meeting agendas. Do I trust this person's judgement? Have they considered the risks? Do they understand the implications? Can they deliver what they are promising?
The answers to those questions influence support far more than most leaders realise.
This is also why stakeholder management becomes increasingly important as careers progress. Early in a career, success is often driven by expertise and individual contribution. As leaders move into more senior positions, their ability to create outcomes becomes increasingly dependent on people they cannot directly control.
Projects require cross functional support.
Strategic initiatives require executive alignment.
Change programmes require broad organisational buy in.
Authority alone becomes insufficient.
Influence becomes essential.
The leaders who thrive in these environments understand that stakeholder management is not a process. It is a leadership capability. It requires curiosity, empathy, communication and trust. It requires understanding how different people experience the same situation. It requires patience when alignment takes longer than expected. Most importantly, it requires recognising that support is something that must be earned rather than assumed.
Perhaps the most important lesson is that stakeholder resistance is not always a sign that people disagree with your idea. Sometimes resistance is simply a signal that people need more confidence before they are willing to support it.
Leaders who understand this tend to approach influence differently.
Instead of asking, "How do I get people to agree with me?"
They begin asking, "What would need to happen for people to feel confident supporting this?"
The quality of the conversation changes immediately.
And more often than not, so does the outcome.
Many leadership challenges that appear to be communication problems are actually stakeholder alignment problems. Developing stronger stakeholder management, executive communication and influencing skills can help leaders build trust, create alignment and gain support for important initiatives long before formal decisions need to be made.