One of my clients, a brilliant French manager, came to me frustrated after a meeting with her British colleagues.
“I presented my proposal,” she told me. “And they said it was ‘quite interesting.’ So I thought they liked it. But then nothing happened. No follow-up or action. What went wrong?”
I had to tell her the truth: “Quite interesting” in British English often means “I disagree, but I’m being polite about it.”
You could tell by her face that she’d completely misread the room.
This happens quite frequently in international business. Non-native English speakers prepare excellent presentations, deliver them clearly, and then wonder why their ideas don’t get traction. The problem isn’t normally the English but the culture gap disguised as language.
British business communication operates on a very specific set of unwritten rules. And if you don’t know those rules, you can say all the right words and still completely miss what’s actually being communicated.
So let me decode this for you.
“That’s interesting” doesn’t mean they agree
Let’s start with the most dangerous phrase in British business English: “That’s interesting.”
In many cultures, if someone says your idea is interesting, that’s positive. It means they’re engaged. They’re curious and that they want to know more.
In British English, “that’s interesting” often means: “I’ve heard what you said, and I’m acknowledging it, but I’m not convinced.”
It’s a neutral holding statement. Not agreement nor enthusiasm. Just… acknowledgement.
And the tricky part it that the tone barely changes whether they genuinely find it interesting or they’re politely disagreeing. You have to read the context.
If “that’s interesting” is followed by questions, discussion, or requests for more information, they might actually be interested.
If “that’s interesting” is followed by “let’s park that for now” or “we should probably move on,” they’re not interested at all.
The same goes for “quite interesting.” That “quite” is often a softener. It actually reduces the enthusiasm rather than increasing it.
Compare: “That’s interesting!” (positive) “That’s quite interesting.” (neutral to negative)
I know, It makes no logical sense, but this is how it works.
“I hear what you’re saying” usually means “I disagree”
This one catches people out constantly.
You present your case, you make your argument. And someone responds with: “I hear what you’re saying.”
You think: Great! They understand me.
But what they actually mean is that they understand your position, but don’t agree with it, and that they are about to explain why.
“I hear what you’re saying” is a polite transition into disagreement. It’s the British way of saying “I respectfully disagree” without using those words.
So when you hear “I hear what you’re saying,” don’t relax. Brace yourself. The pushback is coming.
If you want to know whether someone actually agrees with you, listen for phrases like:
- “I think you’re right.”
- “That makes sense.”
- “I’m aligned with that.”
- “Let’s move forward with this.”
Those are agreements. “I hear what you’re saying” is not.
The softener trap: “perhaps,” “possibly,” “might”
British English uses a lot of softening language. “Perhaps we could consider…” “It might be worth looking at…” “Possibly we should think about…”
For non-native speakers, this can be confusing because in many languages, using this much hedging language makes you sound uncertain or weak.
In British business culture, it’s just politeness. It’s a way of making suggestions without sounding aggressive or domineering.
But here’s where you need to be careful: there’s a difference between using softeners as cultural politeness and using them because you genuinely lack confidence.
When a senior British leader says “Perhaps we should reconsider this approach,” that’s not a gentle suggestion. That’s a directive. They want you to reconsider. The “perhaps” is just cultural wrapping.
But when you, as a non-native speaker, say “Perhaps maybe we could possibly think about…” you sound like you don’t believe in your own idea.
So here’s the rule: use softeners when you’re disagreeing or making suggestions that affect other people’s work. Don’t use them when you’re presenting your own expertise or recommendations.
Compare: “I think we should change the budget allocation.” (confident, clear) “Perhaps we might want to possibly consider changing the budget allocation.” (sounds unsure)
The first one positions you as someone who knows what they’re talking about. The second one sounds like you’re apologising for having an opinion.
When to be direct and when to soften
This is the question I get asked most: “How do I know when to be direct and when to use softer language?”
Here’s my framework:
Be direct when:
- You’re presenting facts or data
- You’re sharing your professional opinion or recommendation
- You’re explaining a process or procedure
- You’re answering a direct question
Use softer language when:
- You’re disagreeing with someone
- You’re suggesting changes to someone else’s work
- You’re raising a concern or problem
- You’re asking someone to do something
Examples:
Direct: “The data shows a 15% decline in Q3.” Soft: “It might be worth looking at why we saw that decline.”
Direct: “I recommend we postpone the launch.” Soft: “Perhaps we could consider a short delay to address these issues.”
The key is this: be direct about what you know. Be softer about what you’re asking others to do or change.
How to disagree without sounding aggressive
This is where many non-native speakers struggle. In some cultures, direct disagreement is normal and expected. In British business culture, it needs to be wrapped in politeness.
But here’s the thing: you can disagree strongly and still be polite. You just need the right phrases.
Don’t say: “That’s wrong.” “I don’t agree.” “That won’t work.”
Do say: “I see it slightly differently.” “I have some concerns about that approach.” “I’m not sure that addresses the main issue.”
Notice how these phrases disagree without directly contradicting the other person? That’s the skill.
And then, crucially, you explain why you disagree:
“I see it slightly differently because the data suggests…” “I have some concerns about that approach, particularly around timing…” “I’m not sure that addresses the main issue, which from my perspective is…”
You’re still making your point and pushing back. You’re just doing it in a way that doesn’t put the other person on the defensive.
Reading the room: tone matters more than words
Here’s something that makes British communication even more complex: tone often carries more meaning than the actual words.
“That’s a great idea” said enthusiastically, means they like it. “That’s a great idea” said flatly means they don’t.
The same sentence but with completely different meanings.
This is why video calls and face-to-face meetings are so much easier than email when you’re dealing with British colleagues. You can see their face. You can hear their tone. You can pick up the cues that tell you whether they actually mean what they’re saying.
On email, it’s harder. Which is why I always tell my clients: if you’re not sure how someone has received your proposal or idea, pick up the phone. Ask directly. “I wanted to check: are you on board with this approach, or do you have concerns?”
Direct questions get clearer answers.
Why “sorry” doesn’t always mean apology
British people say “sorry” constantly. Sorry when someone bumps into them. Sorry when they need to interrupt. Sorry when they’re about to disagree.
For non-native speakers, this is baffling. Why are you apologising when you haven’t done anything wrong?
The answer: “sorry” in British English is often just a politeness marker. It softens what comes next.
“Sorry, could I just add something here?” (not apologising, just politely interrupting) “Sorry, I’m not sure I follow.” (not apologising, asking for clarification) “Sorry, can I stop you there for a moment?” (not apologising, redirecting the conversation)
You don’t need to copy this habit but you do need to understand it.
When a British colleague says “sorry” before disagreeing with you, they’re not apologising for disagreeing. They’re just being British.
What you can do about all of this
I know this feels like a minefield. How are you supposed to prepare a presentation when the words people use don’t actually mean what they say?
Here’s my advice:
1. Focus on the response, not just the words
If you present an idea and people respond with questions, discussion, and follow-up, that’s positive. Even if they used phrases like “interesting” or “I hear what you’re saying.”
If you present an idea and people respond with silence, subject changes, or vague acknowledgments, that’s not positive. Even if they said “great” or “thanks for sharing.”
Watch what happens after the meeting. That tells you more than what’s said during it.
2. Ask direct follow-up questions
If you’re not sure whether someone agrees with your proposal, ask: “Does this approach work for you?” “Are you comfortable moving forward with this?” “Do you see any issues with this plan?”
Direct questions tend to get clearer answers, even in British business culture.
3. Don’t apologise for your expertise
Use softer language when appropriate, but don’t undermine your own credibility.
If you’re presenting your professional recommendation, own it. “I recommend we…” is better than “Maybe we could possibly consider…”
4. Learn to hear the subtext
This takes time. But the more you work with British colleagues, the better you’ll get at hearing what’s actually being said beneath the polite surface.
Pay attention to patterns. Notice how people respond when they genuinely agree versus when they’re just being polite. You’ll start to recognise the difference.
It’s not about becoming British
Let me be clear: I’m not suggesting you adopt British communication style completely.
You should communicate in a way that feels authentic to you. If you’re naturally more direct, don’t lose that. It’s valuable.
But understanding these cultural patterns helps you navigate meetings more effectively. It helps you read responses accurately. And it helps you avoid the frustration of thinking you had agreement when you actually didn’t.
My French client? Once she understood these patterns, she started asking more direct follow-up questions. She stopped assuming “interesting” meant agreement. And she started getting much clearer responses from her British colleagues.
Her ideas didn’t change. Her English didn’t change. But her ability to read the room and respond accordingly? That changed everything.
That’s what cultural communication skills do. They help you navigate the unspoken rules so your excellent ideas actually get heard and acted on.
And that’s what matters.
