How to Disagree with Senior Stakeholders Without Damaging Trust

Disagreeing with a senior stakeholder can feel uncomfortable.

Especially if you are someone who naturally avoids conflict.

If you are anything like me, your first instinct may be to keep the peace, find common ground and avoid saying anything that could create tension. You might think, Is this really worth challenging? Maybe I should just let it go.

And sometimes, letting something go is the right decision.

But leadership requires something more.

There will be moments when you genuinely disagree with a decision, a proposed approach or an assumption being made by someone more senior than you. You may see a risk they have not considered. You may have data that challenges the preferred direction. Or you may simply believe there is a better way of achieving the same outcome.

The easy option is to stay quiet.

The leadership option is to speak up — without turning the disagreement into a battle.

This is something I have been working on for a while. I have had to learn that disagreement does not automatically mean conflict, and that challenging an idea does not mean challenging the person.

You can disagree with someone senior to you while still protecting the relationship and maintaining trust.

In fact, healthy disagreement can strengthen trust.

The goal is not to become the person who challenges everything. Nor is it to win every argument.

The goal is to become someone senior stakeholders can trust to tell them what they need to hear, even when it is uncomfortable.

Here are five principles that have helped me.

1. Align Your Disagreement to the North Star

Before you bring a contradicting suggestion to the table, pause and ask yourself:

What are we actually trying to achieve?

Does your position align with the business strategy?

Does it support the organisation’s goals?

Does it align with the company’s values?

Does it ultimately help the project, team or organisation achieve its intended outcome?

This matters because disagreement becomes much easier to receive when the other person can see that you are not challenging them — you are trying to protect the shared objective.

Start the conversation from the why.

If you and the senior stakeholder agree on the destination, the conversation becomes about finding the best route to get there.

For example, instead of saying:

“I don’t think we should do it this way.”

You could say:

“I agree that our priority is to deliver this within the current programme. I have some concerns about whether this approach gives us the best chance of achieving that, and I’d like to share what I’m seeing.”

The difference is subtle.

You are not starting with opposition.

You are starting with alignment.

And then you create space for the disagreement.

This is particularly important for technical professionals because we can sometimes become so focused on the technical correctness of our position that we forget the broader business objective.

Being right technically is not the same as being effective as a leader.

2. Bring Data, Not Just Opinion

If you are going to challenge a senior stakeholder, make it easy for them to understand why you hold a different view.

Your opinion may be valuable.

But evidence makes the conversation much stronger.

Look at what has happened in similar situations before.

What were the outcomes?

What does the current data tell you?

Have you tested your proposed approach?

Can you simulate the likely outcomes?

Are there examples from previous projects, teams or organisations that support your concern?

The more senior the stakeholder, the less useful it is to simply say:

“I don’t think this will work.”

Instead, show them what you are seeing.

For example:

“We tried a similar approach on the previous project, and the additional approval cycle added approximately three weeks to the programme. Based on the current sequence, I think we could see a similar impact here.”

Now the conversation is no longer simply about whether they should trust your opinion.

You have given them something they can evaluate.

And then you can have a much better conversation about the assumptions behind the decision.

This is where your technical background becomes an advantage.

You already know how to analyse information, test assumptions and look for evidence. The leadership skill is learning how to bring that thinking into a conversation without turning it into a technical data dump.

Senior stakeholders rarely need every detail you have.

They need to understand the issue, the evidence, the potential impact and what you recommend doing next.

3. Start with the MVP

Sometimes your disagreement is about a significant decision.

That can make the conversation feel like an all-or-nothing proposition.

It doesn’t have to be.

If possible, look for a way to test your alternative on a smaller scale.

Start with the minimum viable option.

Could you pilot the approach?

Could you test it on one part of the project?

Could you run a simulation?

Could you collect another round of data before committing fully?

This is particularly useful when you believe strongly in your proposed approach but don’t yet have enough evidence to prove it.

Rather than asking someone senior to make a major change based entirely on your judgement, you can say:

“Would you be open to us testing this on this section first? It would give us some evidence before we roll it out more widely.”

That changes the conversation.

You are no longer asking them to choose between your idea and their idea.

You are suggesting an experiment.

And experiments are much easier to have conversations about.

They also give you something valuable: more evidence.

There is another benefit.

Starting small reduces the perceived risk of being wrong.

And this matters when you are still developing confidence in challenging senior people. You don’t always need to walk into the room with a fully formed solution and absolute certainty.

Sometimes you simply need enough conviction to say:

“I think there may be a better way. Can we test it?”

That is leadership too.

4. It’s Not Just What You Say — It’s How You Say It

You can have the right information and still damage the relationship if you deliver it poorly.

When you disagree, be careful not to make the conversation personal.

Challenge the idea, not the person.

Avoid language that sounds accusatory:

• “You are wrong.”
• “That’s not going to work.”
• “I told you this would happen.”
• “You don’t understand the issue.”

Instead, use collaborative language:

• “I’m seeing a potential risk here.”
• “Can we look at another option?”
• “My concern with this approach is…”
• “What if we considered…”
• “I may be missing something, but this is what the data is showing me.”

There is also something powerful about using “we” language.

“We have a risk here.”

“How can we address this?”

“Could we explore another option?”

“We need to consider the impact on…”

You are reminding everyone that you are on the same team.

And then there is tone.

You do not need to sound apologetic simply because you disagree.

You can be clear, calm and respectful at the same time.

Confidence and respect can coexist.

This is an area I am personally working on. When your natural tendency is to avoid conflict, it can be tempting to soften your message so much that the actual message disappears.

You might say:

“I’m not sure, and maybe I’m overthinking this, but perhaps there could possibly be another way…”

By the time you finish, nobody knows what you are actually proposing.

Being respectful does not require you to make your position invisible.

You can say:

“I have a different view on this, and I’d like to explain why.”

Simple.

Clear.

Respectful.

5. Mind the Timing and the Place

Not every disagreement needs an audience.

Sometimes the best way to protect the relationship is to have the difficult conversation privately.

Imagine challenging a senior stakeholder aggressively in front of a room full of people.

They may feel embarrassed.

They may become defensive.

And once someone feels that they need to defend their position publicly, your carefully prepared argument may never get a fair hearing.

The same conversation held privately can produce a completely different outcome.

This does not mean you should hide important information or avoid raising legitimate concerns in public when the situation requires it.

It means you should think strategically about where and when you challenge.

Ask yourself:

Does this need to be addressed right now, in front of everyone?

Sometimes the answer will be yes.

Sometimes the better approach is to ask for a quick conversation afterwards.

And sometimes, giving someone time to process the information before discussing it further can make all the difference.

Timing is especially important when emotions are already running high.

If someone has just presented a proposal they have spent weeks developing, immediately dismantling it in front of their peers may not be the most productive approach.

You can still raise the concern.

You might simply choose a better moment to do it.

Leadership is not only knowing what to say.

It is knowing when, where and how to say it.

You Can Say Yes to Disagreement

If you tend to avoid conflict, learning to disagree constructively may feel uncomfortable at first.

That’s okay.

You do not need to suddenly become the person who walks into every meeting looking for something to challenge.

Start smaller.

The next time you disagree with a senior stakeholder, pause before automatically saying nothing.

Ask yourself:

1. Are we aligned on the bigger objective?

If not, clarify the objective first.

2. What evidence supports my concern?

Separate what you know from what you assume.

3. Can I test my alternative?

Look for a small experiment rather than an all-or-nothing decision.

4. Am I challenging the idea or the person?

Choose language that keeps the conversation collaborative.

5. Is this the right time and place?

Sometimes the most effective disagreement happens in a one-to-one conversation.

And then speak.

You don’t have to be confrontational.

You don’t have to be the loudest person in the room.

You don’t even have to be completely certain.

You simply need to be willing to contribute your perspective.

Final Thoughts

Disagreeing with a senior stakeholder does not have to damage trust.

Done well, it can actually build your credibility.

You demonstrate that you are willing to think critically, challenge assumptions and protect the interests of the team or organisation rather than simply agreeing with whoever has the most authority in the room.

And that is an important shift for technical professionals moving into leadership.

Your value is no longer only in having the right technical answer.

It is also in being willing to bring a different perspective, communicate it thoughtfully and help others make better decisions.

So if you are someone who naturally avoids conflict, don’t make your goal to become more confrontational.

Make your goal to become more comfortable with constructive disagreement.

Because sometimes leadership means saying:

“I see it differently.”

And then having the courage, clarity and emotional intelligence to explain why.