How do you disagree politely in English at work?
Three steps: acknowledge their view, say what worries you, then offer another way. I see the appeal, but I'd rather not. My concern is that if something goes wrong, every order is affected. I'd suggest starting with five percent of traffic. The reason and the alternative matter as much as the polite words, because they give people something to answer. In a multinational team, a flat You're wrong or I don't agree can come across as too blunt.
What do you say at each step?
One or two phrases per step are enough. These come from the Technical design review scene, the Meetings unit and other work scenes in Before You Speak.
| Say this | What it does |
|---|---|
| 01 AcknowledgeShow you heard them before you say no | |
| I see your point, but … | The everyday version |
| That's a fair point, but … | Gives them credit first |
| I see the appeal, but … | Admits their idea has real advantages |
| That's true on a normal day, but … | Agrees with part of it, then shows where it stops being true |
| 02 Say what worries youYour concern and the reason, not just no | |
| My concern is that … | Makes it about the risk, not the person |
| I'm not sure that'll work, because … | Doubt, with a reason attached |
| I don't think 30% is realistic yet. | Politer than “It's impossible” |
| I'd rather not. | Politer than “No” or “I don't agree” |
| 03 Offer another wayGive them something to say yes to | |
| I'd suggest starting with five percent of traffic. | A clear alternative |
| Have we considered doing it in two phases? | Your idea as a question |
| How about a middle ground? | Moves two sides toward a deal |
| Here's what I can do: … | After saying no, says what you can do |
| 04 Close itSay what happens now | |
| On balance, it's worth it. | Brings the trade-off to a conclusion |
| Two things from you: … | Says what you need, and how many |
| Can we try that from Monday? | “Try” is easier to agree to than “change” |
How direct does each phrase sound?
Roughly from the softest to the most direct. The order is our own judgement, from the notes in the Meetings unit.
| Phrase | How it sounds |
|---|---|
| I see it a bit differently. | Soft: a different view, no verdict on theirs |
| I'm not sure that's the best option. | Polite doubt |
| That's a fair point, but … | Gives credit, then disagrees |
| I see your point, but … | Shows you understood, then disagrees |
| I'm not sure that'll work, because … | Doubt, with your reason |
| I'd rather not. | A clear no, still polite |
| I disagree. | Very direct: use it rarely in meetings |
| You're wrong. | Can sound too blunt in a multinational team |
What does polite disagreement sound like?
Example: a design review on a Thursday morning. You lead the checkout team and you've just presented a plan to split checkout into its own service. Olivier, the chief architect, and Marta, the engineering director, are asking questions. Marta has two ideas you don't agree with.
My question is simpler. Why a separate service at all? Couldn't we just scale the old system?
We looked at that. Scaling the old system is cheaper in the short term, but every checkout change still waits for the full release. The new service costs more to run, but we can release and scale it on its own. We think it's worth it.
Acknowledge · Trade-offFair enough. For us, speed matters more than a few extra servers.
One more thing. Why not switch everyone over in one go? One weekend, and it's done.
I see the appeal, but I'd rather not. My concern is that if something goes wrong, every order is affected. I'd suggest starting with five percent of traffic and going up step by step. We can switch back in minutes.
Acknowledge · Concern · AlternativeI'm with you on that. A slow rollout beats a bad weekend.
Fine, you've convinced me. So what do you need from us?
Two things. First, your sign-off on the step-by-step rollout. Second, someone from the infrastructure team on call during the load test. I'll send a summary today and set up a follow-up after the test.
Next stepSource: the Technical design review scene in Before You Speak; the lines are as in the scene, and you can read and hear all of it. The people and the project are made up. It ends well here; in a real meeting you may not win the point, but people will know what you think and why.
How do you say the same thing more naturally?
Clear is a short sentence that gets you understood, Natural is what a colleague would actually say, and Compact packs in more while still sounding spoken. If you're nervous, the clear version is enough.
A director wants to switch everyone over at once
- ClearI understand, it is faster. But if there is a problem, all orders have a problem. I suggest we start with five percent, then more. We can go back quickly.
- NaturalI see the appeal, but I'd rather not. My concern is that if something goes wrong, every order is affected. I'd suggest starting with five percent of traffic and going up step by step. We can switch back in minutes.
- CompactI see the appeal, but I'd rather not do it in one go. My concern is the risk: if something breaks, every single order is hit. What I'd suggest is five percent first, then step by step up to a hundred. With a feature flag, we can switch back in minutes.
A senior engineer says it has never been a problem
- ClearMost days, yes. Payments timed out for over 20 minutes on Black Friday. I suggest three retries at most. Wait one, two, then four seconds.
- NaturalThat's true on a normal day. But on Black Friday last month, the payment API timed out for over 20 minutes. I'd suggest three retries at most, waiting one, two, then four seconds.
- CompactThat's true on a normal day, but at peak it's a different story. On Black Friday the payment API timed out for over 20 minutes. I'd suggest capping it at three retries, waiting one, two, then four seconds.
Your manager wants a target you don't think is possible
- ClearI think 30% is too high for now. I suggest 24%. The new carrier needs more time.
- NaturalI don't think 30% is realistic yet. I'd suggest 24%, because the new carrier needs more time.
- CompactHonestly, 30% is a stretch until the new carrier's proven itself. I'd rather commit to 24% and actually hit it.
All three versions are the lines the scenes prepare: Technical design review, Video code review and Mid-year 1:1.
What do you say when they push back?
The first reply is often not the end of it. These pairs are from Before You Speak scenes.
| They say | You can say |
|---|---|
| “Honestly, that's too slow.” | I see your point, but it's over 400 terabytes. If the copy fails halfway, we won't have an easy way to roll back. |
| “Is this a real risk, or more of a what-if?” | That's true on a normal day. But on Black Friday last month, the payment API timed out for over 20 minutes. |
| “Couldn't you squeeze it in first thing tomorrow?” | I'd really like to help, but if I do the slides tomorrow morning, the client report might slip. |
| “I need both.” | Sure. The payment fix is about 6 days, and the full coupon feature is about 9. We only have 8 days of capacity. |
| “What can I give marketing?” | How about this: we build a basic coupon version this sprint, minimum-spend discounts only. It's about 2 days. |
| Two people want opposite things | How about a middle ground? We start with half, ten thousand units, then look at the data in week two and top up if we need to. |
| They're right | That's a fair point, it's a real limitation. I actually put it on the last slide. |
Which slips make disagreement sound rude?
From the notes and slip warnings in the Before You Speak scenes and units. None of these is wrong English. They're just stronger than most people mean.
| Easy to say | Better | Why |
|---|---|---|
| ✗ You're wrong. | ✓ I see your point, but … | Acknowledge first, then soften. It isn't about being vague: you can still say exactly what you think. |
| ✗ I don't agree with you. | ✓ That's a fair point, but … | The disagreement is still there, without making it about them. |
| ✗ No way. | ✓ I'm not sure that's the best option. | Doubt leaves room to talk. |
| ✗ It's impossible. | ✓ I don't think 30% is realistic yet. | “Yet” also tells them what would need to change. |
| ✗ That won't work. | ✓ I'm not sure that'll work, because … | Say why, not just no. |
| ✗ You are both wrong. | ✓ How about a middle ground? | Moves the talk from who's right to what to do. |
| ✗ You should … | ✓ Why don't you … / I'd suggest … | Softer than “you should”, and still clear. |
| ✗ I want … | ✓ I'd need … | “I'd need” sounds like a condition for the plan, not a personal demand. |
| ✗ Can we discuss about it? | ✓ Can we discuss it? | “Discuss” takes its object directly, with no “about”. |
How do these phrases sound in different accents?
Press a button to hear the same phrase in a US, UK, Australian or Indian accent. Tone carries a lot of the politeness here.
| Phrase | Meaning | Listen: US / UK / AU / IN |
|---|---|---|
| I see your point, but it's a big risk. | polite disagreement | |
| That's a fair point. | you're right about that | |
| I'm not sure that's right. | polite doubt | |
| I see it a bit differently. | I have another view | |
| That makes sense. | I agree with your reasoning | |
| Just to confirm, you're coming on Saturday at 8? | checking what was agreed |
The voices are AI-generated, for practice only.
How do you practise disagreeing?
In each of these, someone pushes for something and you have to say no without closing the door:
- Technical design review: trade-offs and a polite no: with a French architect and a Polish director. Practise it
- Video code review: raising a problem: with a senior engineer who says it has never been an issue. Practise it
- Sprint planning: payments before coupons: persuading a product manager with numbers. Practise it
- Quarterly budget meeting: keeping your budget: using data to win part of it back. Practise it
- Open-plan office: saying no to an extra task: and offering something else instead. Practise it
The scene pages are in Chinese with the full English script alongside, and every line has a recording. You can read and listen without signing up. All characters, lines and voices are AI-generated, for practice only.
Polite wording is harder to find when someone is pushing back in real time. In Before You Speak (开口前 kaikouqian), two AI colleagues with real accents talk and you can cut in at any time; when it's your turn, they stop and wait for you. Afterwards you get at most two corrections, they go into your review book, and in review a colleague says the original line again and you answer. You can also write your own situation in Chinese (what it's about, who it's with, what you want to say, the facts only you know) and get a practice scene in two or three minutes.
Free sign-up, no card. The free plan has two live AI conversation rounds and three scripted sessions a week; your own scenes come with a 7-day free trial, and nothing is charged when it ends. For people living outside mainland China, Hong Kong and Macau. The app explains in Chinese; Chrome on a computer works best.
Which guides go with this one?
- Speaking up in meetings: How to get in when nobody leaves a gap, ask about what you missed, buy time and confirm the next step.
- Politely interrupting: Which phrase fits which moment, how strong each one sounds, and how to move a side topic out of the meeting.
- Rehearsing a difficult talk with your boss: A delay, a raise, a target you can't hit: what to write down, what to say, and how to rehearse against pushback.
- All guides
How was this page written?
- Author
- The maker of Before You Speak, a Chinese engineer working in English in Abu Dhabi.
- Sources
- These practice scenes in Before You Speak: Technical design review, Video code review, Mid-year 1:1, Sprint planning, Open-plan office and Cross-team meeting, plus its Meetings unit and “jump in and disagree” practice pack. The names and the projects are made up.
- Use of AI
- The characters, lines and audio in the scenes are AI-generated. The explanations on this page were drafted with AI and put together by the author. The ranking of how direct each phrase sounds is our own judgement.
- Updates
- First published 2026-11-01. Found a mistake or want to add something? Write to hello@kaikouqian.com.