Skip to content
FluentSession

How to disagree politely in English at work

Phrases for disagreeing politely in English at work: partial agreement, questions instead of objections, disagreeing with your manager, and pushing back in writing.

2 min read

To disagree politely in English, start with what you agree with, then add your concern with "but" or "although". "I don't agree" is grammatically correct, but in many English-speaking workplaces it sounds more confrontational than the speaker intends, especially from a non-native speaker whose tone is already harder to read.

This matters most for people from cultures where direct disagreement is normal and even a sign of respect, as it often is in Polish, Dutch or German teams. The words translate. The effect does not.

Why directness lands differently

Linguists explain this with politeness theory: in conversation people protect each other's "face", their sense of being competent and respected (Politeness theory, Wikipedia). A direct "That's wrong" threatens the other person's face. Softened disagreement lets them change their mind without losing it.

British English in particular uses a lot of understatement. "I'm not sure that's the best approach" often means "I think this is a bad idea". If you answer that sentence as if it were a mild doubt, you may miss a strong objection.

Partial agreement

The most reliable pattern: agree with part of the idea, then disagree with another part.

I see your point, but I'm worried about the timeline.Acknowledges, then names a specific concern. That makes sense in general. Where I'm less sure is the cost.Moves the disagreement to one detail. I agree with the goal. I'd just approach it differently.Same destination, different route.

Questions instead of objections

A question lets the other person find the problem themselves, which is easier to accept.

How would this work if the client changes the scope?Raises a risk as a question. Have we considered doing it in two phases?Proposes an alternative without rejecting the original. What happens if the API is down?A technical objection framed as a scenario.

Disagreeing with your manager

The stakes are higher, so make it about the shared goal and offer a way forward.

Can I share a different view on this?Asks permission. Almost always answered with yes. I want to make sure we hit the deadline, and I'm worried this plan puts it at risk.Shared goal first, then the concern. If we go ahead, could we at least add a week for testing?Accepting the decision, with a condition.

Disagreeing in writing

Written disagreement looks harsher than spoken, because there is no tone of voice. Add one more softener than you would use out loud.

Too direct in writingBetter
This won't work.I'm not sure this will work for the larger accounts.
You forgot the tests.Could we add tests before merging?
No, we can't do that.I don't think we can do that by Friday. Could we aim for Tuesday?
Why is this so late?Is there anything blocking this? Happy to help.

For code reviews specifically, see English for code reviews.

When to be direct anyway

Softening has limits. When something is unsafe, illegal or about to break production, say it clearly: "We need to stop this release. The payment tests are failing." Clarity beats politeness when the cost of being misunderstood is high.

Practise before the meeting

Disagreeing is hard to rehearse alone, because you need someone to disagree with. A voice tutor can play that role. In FluentSession you describe the tutor yourself, for example "a confident product manager who wants to ship on Friday no matter what", and practise holding your position politely.