How to disagree well at work

Disagreeing at work carries a cost that disagreeing with a friend does not, and pretending otherwise is bad advice. There is a way to do it that keeps the cost small.

Most of it is about timing and framing, not courage.

What is actually happening

A disagreement in a meeting is heard by everybody present, which turns a technical point into a social event. The person you are disagreeing with is managing how it looks as well as whether you are right.

That is why the same objection lands completely differently in a meeting and in a message an hour earlier.

Why it happens

Hierarchy is real and pretending it is not does not remove it.
Meetings reward whoever is quickest, not whoever is most careful.
Objections often arrive fully formed and sound like a verdict rather than a contribution.

What it looks like

Your manager proposes an approach you think will not work.

You say nothing in the meeting.
You say something to a colleague afterwards.
The work starts.
Three weeks later the problem you saw arrives.
Somebody asks why nobody raised it.

What to do instead

1. Raise it before the room

A message beforehand costs nobody anything publicly and is far more likely to change the outcome. This single habit does more than everything else here.

2. Disagree with the thing, name the shared aim

"We both want this shipped by March — I think this route risks that" is a different conversation from "that won't work".

3. Bring the alternative

An objection without an option is a complaint. Even a poor alternative changes the conversation from stop to choose.

4. Be explicit about your confidence

"I'm fairly sure" or "this is a hunch" tells people how much weight to give it. Without that, every objection sounds like the same level of certainty.

5. Disagree and commit, out loud

"I still think it's the wrong call, and I'll make it work." Said plainly, this earns more than being right does.

Try this

Next time you disagree in a meeting, do not say it there. Send it beforehand next time.
When you do object, name the shared goal in the first sentence.
Say how confident you are.
Offer one alternative, even a rough one.
If the decision goes the other way, say you are behind it and mean it.

What it sounds like

In the meeting, cold

You: I don't think that'll work.

Them: Why not?

You: It just seems risky.

Them: Let's go with it and see.

A vague objection in public is the easiest thing in the world to overrule, and it costs some credit with nothing bought.

Beforehand, specific

You: Before tomorrow — I think the March date is at risk with this approach, because of the vendor dependency.

Them: Hm. What would you do?

You: Start the integration first and the UI after. Less parallel work, but the risk is front-loaded.

Them: Bring that up tomorrow, I'd rather the team heard it.

The same objection, one day earlier, ended with being asked to make the case publicly. That is the outcome the meeting version cannot produce.

Why this is hard to actually do

In some workplaces this is genuinely punished. If so, the useful question is about the workplace rather than the technique.

Raising it early requires noticing early, which means paying attention to agendas you would rather skim.

Disagreeing and committing feels like losing twice. It is the single most respected thing on this list.

What it costs to leave it

Problems you saw coming arrive anyway, and you carry knowing about them.
Staying quiet reads as agreement, and repeated agreement reads as having no view.
The cost of never disagreeing is usually paid slowly, in being consulted less.

Practise it

Reading about conversations is not the same as having one. Splivex puts you on video with somebody who disagrees with you, for twenty minutes, about one question. There is no score and no winner — the only question afterwards is whether either of you changed your mind.

Practise on Splivex →