The Problem

Your English is excellent. Your grammar is secure. Your vocabulary is rich. So why do people sometimes look blank when you speak?

Learning intention: Understand the three layers of communication breakdown and learn why, at C2 level, the issue is almost never vocabulary or grammar.

The Three Layers

Communication can break down in three ways. Most advanced speakers focus on the first two. You need to master the third.

Layer 1: Vocabulary Problem

Your listener doesn't know the word.

Example: "The orthogonal approach..." (listener doesn't know "orthogonal")

Fix: Simple. Define it or use a simpler word.

Layer 2: Grammar Problem

The sentence structure is unclear. The listener can't parse it.

Example: "The dashboard, which we designed to show, is what we implemented because the stakeholders requested it."

Fix: Break it into shorter sentences. Simplify clause structure.

Layer 3: Pragmatics Problem

Your listener hears the words and understands the grammar—but doesn't get your intent.

Example: "The model isn't capturing seasonal variation."
(Does this mean: It's a known limitation? We need to fix it? It's acceptable? You're frustrated?)

Fix: Make your intent explicit. Signal your message. Check understanding.

Why pragmatics matters at C2

At lower levels, listeners are forgiving. They expect some struggle. They listen actively, guess meaning from context, ask for clarification.

At C2, people expect fluent, natural speech. When you sound fluent but they don't understand you, they don't think "English problem." They think:

This lesson teaches you the language to prevent that moment. It's about making your thinking visible.

Your task now

🎙 Speak: Think of a time someone didn't understand you—even though you spoke grammatically correct English. What was the breakdown? Was it vocabulary, grammar, or something else? Speak for 2–3 minutes.

The Language

Learning intention: Master 16 expressions that make your meaning explicit and keep your listener with you.

1. Checking Understanding

These expressions invite your listener to tell you if you're being clear. They turn a one-way broadcast into a dialogue.

"Does that make sense so far?"
When: After explaining a concept, before moving on.
Context: "So we're using a Bayesian approach because it handles uncertainty better. Does that make sense so far?"
"Just to check we're on the same page..."
When: Before diving into detail or a recommendation.
Context: "Just to check we're on the same page—you're saying the dashboard needs to update in real time, right?"
"Shall I put that another way?"
When: You notice confusion or want to rephrase proactively.
Context: "The variance is explained by the interaction term. Shall I put that another way?"
"I want to make sure I'm being clear..."
When: Before restating something important or complex.
Context: "I want to make sure I'm being clear: this doesn't mean we're changing direction. We're refining the approach."
🎙 Speak: Take one of these checking expressions. Create a scenario where you'd use it (e.g., in a meeting, presenting findings, explaining a process). Speak naturally, using the expression. Aim for 45–60 seconds.

2. Reformulating

These expressions signal that you're about to say the same thing in a simpler, clearer way. They prevent misunderstanding before it happens.

"What I'm really getting at is..."
When: You want to cut through complexity to the core point.
Context: "The algorithm optimizes across multiple variables, but what I'm really getting at is: this approach costs less."
"To put it more simply..."
When: You've said something technical and need to translate it.
Context: "We're reducing dimensionality through PCA. To put it more simply, we're making the data easier to visualize."
"In other words..."
When: You need a synonym or restatement for clarity.
Context: "The model exhibits overfitting behavior. In other words, it's memorizing the training data instead of learning patterns."
"The key point here is..."
When: You're filtering out noise and highlighting what matters.
Context: "We tested seventeen variations. The key point here is only three showed statistical significance."
🎙 Speak: Pick a complex idea from your field or experience. Explain it once in technical language. Then use "To put it more simply..." and reformulate it for a general audience. Aim for 1–2 minutes total.

3. Signposting

These expressions guide your listener through your argument. They create a map so people know where you're going.

"Before I go into detail, the big picture is..."
When: You're about to explain something complex; give the frame first.
Context: "Before I go into detail, the big picture is: we can meet the deadline but we'll need to compromise on one feature."
"There are three things to consider here..."
When: You're organizing a multi-part answer or recommendation.
Context: "There are three things to consider here: cost, timeline, and technical feasibility. Let me walk you through each."
"The reason I mention this is..."
When: You're explaining why a detail matters; signaling relevance.
Context: "The client's previous vendor failed to integrate with their legacy system. The reason I mention this is: we need to plan for compatibility."
"Let me come back to that in a moment..."
When: Someone raises a question, but you want to address it later in your explanation.
Context: "You're asking about ROI—let me come back to that in a moment. First, I need to explain how the system works."
🎙 Speak: Imagine you're presenting a recommendation to a stakeholder. Structure your answer using at least two signposting expressions. Speak for 2–3 minutes.

4. Managing Implicature

These expressions make implicit meaning explicit. They prevent the listener from reading between the lines and getting it wrong.

"I don't mean to suggest that..."
When: Your words could be misinterpreted as criticism or a bigger claim than intended.
Context: "The original approach didn't capture all variables. I don't mean to suggest that it was wrong—it was fit for purpose at the time."
"Just to be clear, I'm not saying..."
When: You want to preempt a misunderstanding you sense coming.
Context: "We need to redo this analysis. Just to be clear, I'm not saying the team made a mistake—there's new data."
"What I mean by that is..."
When: You've said something that might sound abstract; you ground it.
Context: "The system needs to be more robust. What I mean by that is: it should handle edge cases without manual intervention."
"When I say X, I mean specifically..."
When: A term you've used could have multiple interpretations; you narrow it.
Context: "When I say 'scalable,' I mean specifically: it can handle a 10x increase in data volume without redesign."
🎙 Speak: Think of a statement that could be misunderstood or sound critical. Use "I don't mean to suggest that..." or "Just to be clear, I'm not saying..." to clarify your intent. Speak for 45–60 seconds.

The Say/Hear Gap

Learning intention: See how the same words can create confusion—and how target language fixes it.

Scenario 1: The Model Problem

What the speaker says:
"The model doesn't capture seasonal variation."

What could the listener hear?

How target language fixes it ▼

Better version:

"The model doesn't capture seasonal variation. What I mean by that is: we're aware of this limitation, and it's acceptable for this use case because the client's data is mostly static. Just to be clear, I'm not saying the model is broken—the key point here is it meets the business requirements."

What changed: You went from a statement (ambiguous) to a mini-explanation (clear). The listener knows your intent.

Scenario 2: The Timeline Pressure

What the speaker says:
"We'll need to cut features to hit the deadline."

What could the listener hear?

How target language fixes it ▼

Better version:

Before I go into detail, the big picture is: we have three options. Let me come back to the financial impact in a moment, but first—there are three things to consider: timeline, scope, and resource availability. To put it more simply, cutting features is the lowest-risk way to maintain quality while hitting the date."

What changed: You gave context, signaled structure, and explained trade-offs. The listener understands the reasoning, not just the outcome.

Scenario 3: The Methodology Question

What the speaker says:
"We're using a Bayesian approach rather than frequentist methods."

What could the listener hear?

How target language fixes it ▼

Better version:

"We're using a Bayesian approach rather than frequentist methods. Shall I put that another way? Instead of asking 'What's the probability of this result if the null hypothesis is true?', we ask 'Given the data we have, what's the probability of this theory being true?' The reason I mention this is: it handles uncertainty better when you have small sample sizes. Does that make sense so far?"

What changed: You translated jargon, explained why you chose it, and checked understanding. The listener feels included, not left behind.

Scenario 4: The Feedback Moment

What the speaker says:
"The dashboard needs to be redesigned."

What could the listener hear?

How target language fixes it ▼

Better version:

"The dashboard needs to be redesigned. I don't mean to suggest the current version is broken. What I'm really getting at is: user testing revealed three pain points. The reason I mention this is: they're fixable, and fixing them will make adoption much faster. Shall I walk you through them?"

What changed: You softened the blow, clarified the intent (improvement, not criticism), and invited dialogue. The listener hears collaboration, not judgment.

🎙 Speak: Choose one of these four scenarios. Imagine you're the speaker. Use at least three target language expressions to deliver the message clearly and with appropriate tone. Speak naturally; aim for 1–2 minutes.

Practise

Learning intention: Use target language in real-time to reformulate complex ideas and maintain dialogue.

Question Volleyball

A stakeholder throws you a question. You use target language to answer clearly. Here are five common scenarios.

Question 1: "Why didn't you use the simpler model?"

Model answer (expressions highlighted) ▼

"What I'm really getting at is there's a trade-off between simplicity and accuracy. The key point here is: the simpler model would be 15% less accurate. When I say 'less accurate,' I mean specifically: it would misclassify more edge cases, which directly impacts your bottom line. To put it more simply, we chose the complex model because the cost of errors is higher than the cost of complexity. Does that make sense?"

🎙 Speak: Now answer the same question in your own way. Use at least two expressions from the lesson.

Question 2: "How confident are you in these findings?"

Model answer (expressions highlighted) ▼

"Before I go into detail, the big picture is: I'm very confident, but with one caveat. There are two things to consider: first, the statistical confidence—we're at 95%, which is industry standard. Second, the data quality. The reason I mention this is: we had some missing values. I don't mean to suggest that compromises the findings—we handled them through imputation. Just to be clear, I'm saying the results are robust but not bulletproof. Shall I explain the imputation method?"

🎙 Speak: Answer this question with at least three target expressions. Be specific about your confidence level and any limitations.

Question 3: "This is different from what we expected. What went wrong?"

Model answer (expressions highlighted) ▼

"I want to make sure I'm being clear: nothing went wrong. What I mean by that is: our hypothesis was based on incomplete information. The reason I mention this is: it's actually valuable—it tells us something about the system we didn't know. To put it more simply, the data revealed an interaction we didn't expect, but now we can model it. Just to be clear, I'm not saying the original analysis was flawed—the key point here is we have better information now. Does that make sense?"

🎙 Speak: Reframe a "failure" or unexpected result as a learning. Use at least three expressions. Sound collaborative, not defensive.

Question 4: "Can you give us a quick summary?"

Model answer (expressions highlighted) ▼

"Before I go into the headlines, the big picture is: we can do this, but it'll cost more than the original estimate. There are three reasons: integration complexity, timeline, and risk mitigation. Let me come back to cost in a moment, but first—when I say 'complexity,' I mean specifically: the legacy system and the new platform don't speak the same language; we need a middleware layer. The key point here is: it's manageable, and the cost is justified. Does that land for everyone?"

🎙 Speak: Give a 90-second summary of a complex project or analysis. Structure it using signposting language. Make it clear for a non-technical audience.

Question 5: "Should we change direction?"

Model answer (expressions highlighted) ▼

"I don't mean to suggest our current direction is wrong. What I'm really getting at is: there's a faster path forward that we didn't see initially. There are two things to weigh: switching costs versus future gains. The reason I mention this is: the calculation changes depending on your timeline. To put it more simply, if you need results in 6 months, we should shift. If you can wait 9, the current path is fine. Just to be clear, I'm not saying either choice is wrong—the key point here is understanding the trade-off. Shall I model both scenarios?"

🎙 Speak: Propose a change without sounding like you're criticizing the original choice. Use at least three expressions. Present it as a nuanced decision, not a yes/no.

Reformulation Challenge

Your task:

You're about to explain something complex to an audience with mixed technical knowledge. First, explain it in technical language (1 minute). Then, use "To put it more simply..." and "What I'm really getting at is..." to reformulate it for a general audience (1 minute).

Topics to choose from:

🎙 Speak: Choose a topic. Deliver both versions. Show how your target language makes the second version accessible without losing precision.

Real Scenarios

Learning intention: Apply target language in realistic consulting and professional contexts.

Scenario A: Presenting Data to Non-Technical Stakeholders

The Setup:
You've analyzed three years of data on system performance and user behavior. You've found something unexpected: the most expensive feature is actually the least used. You need to recommend action. You have 5 minutes with the decision-makers.
💡
Your opening line
How do you grab attention and set the frame? Use "Before I go into detail, the big picture is..."
🎯
Structure your argument
How many points will you cover? Use "There are X things to consider..." or "Let me come back to that in a moment..."
⚠️
Preempt misunderstanding
What might they hear that you don't intend? Use "I don't mean to suggest..." or "Just to be clear, I'm not saying..."
✓
Check understanding
How will you know they're with you? Use "Does that make sense so far?" or "Shall I put that another way?"
🎙 Speak: Deliver your 5-minute presentation. Use at least four target language expressions. Be clear, structured, and persuasive. Sound like someone who understands both the data and the business.

Scenario B: Explaining a Failed Recommendation

The Setup:
Three months ago, you recommended an approach. New information has emerged. The approach is no longer viable. You need to explain why to the same stakeholders and propose an alternative. This is delicate: you don't want to sound like you made a mistake, but you also don't want to sound defensive.
🛡️
Acknowledge without apologizing
How do you own the situation without seeming incompetent? Use "I don't mean to suggest the original analysis was wrong..."
📊
Explain what changed
New data? New constraints? Use "The reason I mention this is..." and "What I mean by that is..."
🔄
Present the new path
How is this better? Use "To put it more simply..." or "The key point here is..."
🤝
Invite dialogue
Make them feel part of the decision. Use "Shall I walk you through the new approach?" or "Does that make sense?"
🎙 Speak: Deliver this message. Aim for 3–4 minutes. You want to sound confident, collaborative, and self-aware—not defensive or apologetic. Use at least five expressions.

Scenario C: Giving Feedback on Someone's Work

The Setup:
A colleague has delivered an analysis. It's technically sound, but it's missing context. It answers the question they were asked, but not the question the business actually needs answered. You need to give feedback that is honest but not demoralizing.
👍
Start with what's good
What did they do well? Be specific and genuine.
🎯
Explain the gap (not blame)
Use "I don't mean to suggest..." or "Just to be clear, I'm not saying the analysis is wrong..."
🔍
Show what's missing and why it matters
Use "The reason I mention this is..." and "What I mean by that is..."
🚀
Offer the path forward
Make it collaborative, not corrective. "Shall we add X?" not "You need to add X."
🎙 Speak: Deliver feedback on a piece of work. Make it honest and constructive. Your tone should be supportive, not critical. Use at least four expressions. Aim for 2–3 minutes.

Scenario D: Handling a Difficult Question in a Meeting

The Setup:
You're presenting your work. Someone asks a question that reveals a flaw in your thinking, or a gap you hadn't considered. You have two options: admit you don't know, or think on your feet. You choose to think on your feet. You need to sound competent while staying honest.
⏱️
Buy time thoughtfully
Don't say "Um." Say: "That's a great question. Let me think through that..."
🗣️
Reframe the question
Use "Just to check we're on the same page..." to clarify what they're really asking.
🤔
Give a thoughtful partial answer
Use "What I'm really getting at is..." to distill your thinking. Admit what you don't know.
📋
Close the loop
Promise follow-up. "Let me come back to that with a full analysis."
🎙 Speak: Imagine you're in a meeting and someone asks you a challenging question. Think on your feet and respond. Use at least three expressions. Sound thoughtful and honest, not flustered.

The Invisible Layer

Learning intention: Understand the cultural and cognitive dimensions of why people don't understand you—even when your English is perfect.

High-Context vs. Low-Context Communication

Some cultures communicate "high-context": much meaning is implicit, assumed, unspoken. You're expected to read between the lines. Others are "low-context": meaning is explicit and literal.

High-Context

Listeners expect you to:

  • Assume shared background
  • Use indirectness (it's polite)
  • Let silence speak
  • Trust inference

Example: "The timeline is tight." (means: we might not make it)

Low-Context

Listeners expect you to:

  • Say things explicitly
  • Use directness (it's clear)
  • Fill silence with words
  • State assumptions

Example: "We have a 40% risk of missing the deadline." (explicit, measurable)

The problem for excellent English speakers:

You might be a high-context communicator speaking to low-context listeners (or vice versa). Your English is flawless—but your communication style doesn't match their expectation.

High-context speaker + low-context audience: You sound vague, evasive, or like you're hiding something.

Low-context speaker + high-context audience: You sound blunt, harsh, or insensitive.

Solution: Make your implicit meaning explicit. Use the target language from this lesson. It bridges the gap.

🎙 Speak: Think about your own communication style. Are you more high-context or low-context? Describe a time when that style caused misunderstanding. How would you adjust using target language? Speak for 2 minutes.

The Role of Directness

Many advanced English speakers believe that directness = clarity. Not always true.

Direct statement:
"That approach won't work. We need to pivot immediately."

What happens:

Same meaning, more explicit:
"I don't mean to suggest the current approach is flawed. What I'm really getting at is: new information has emerged that changes the calculation. The reason I mention this is: we have a window to adapt without losing momentum. To put it more simply, pivoting now costs less than pivoting in two weeks. Does that make sense?"

What happens:

The insight:

Making your implicit meaning explicit isn't less direct. It's more clear. Directness is a style. Clarity is a goal. At C2 level, your job is to achieve clarity—whatever style that requires.

🎙 Speak: Take a direct statement you might make in your work. Rephrase it using at least three target expressions. Show how the second version is clearer, even though it's longer. Speak for 1–2 minutes.

Cognitive Load and Comprehension

Your listener is doing cognitive work. They're listening to you in a second language. They're taking in new information. They might be processing competing agendas.

When you use target language strategically, you reduce their cognitive load:

"Before I go into detail, the big picture is..."

Creates a frame → listener knows where you're going → easier to follow detail

"There are three things to consider..."

Signals structure → listener can anticipate what comes next → easier to track

"In other words..."

Gives a second chance to understand → catches people who got lost → reduces anxiety

"Does that make sense so far?"

Checks understanding → gives listener permission to ask → opens dialogue

The takeaway:

Your target language isn't just about avoiding misunderstanding. It's about managing how much cognitive work your listener has to do. You're being kind and clear—which is also strategic.

🎙 Speak: Imagine you're explaining something complex to someone who's new to your field. How would you structure your explanation to reduce cognitive load? Use at least three expressions. Show how you'd make it easier to follow. Speak for 2 minutes.

When Silence Is the Problem

After you speak, there's silence. What does it mean?

What you think:

"They understood. We're good."

What might be true:

  • They didn't understand but are embarrassed to ask
  • They understood the words but not the implication
  • They understood but disagree
  • They understood but don't know how to respond
  • You genuinely got through. (Sometimes.)

Target language fixes this. Expressions like "Does that make sense?" and "Shall I put that another way?" are invitations. They say: You're allowed to not understand. We can fix this together.

🎙 Speak: Explain why checking understanding ("Does that make sense?") is actually a sign of strength, not weakness. How does it change the dynamic in a meeting or conversation? Speak for 1–2 minutes.

Recall & Reflect

Learning intention: Consolidate what you've learned. Retrieve the language. Reflect on how you'll use it.

Review: Name the Expressions

Without looking back, can you recall three expressions from each category? Write them or speak them aloud.

Checking Understanding

Name three expressions:

🎙 Speak: Give three checking expressions. Say them aloud. Then use each one in a short sentence.

Reformulating

Name three expressions:

🎙 Speak: Give three reformulating expressions. Say them aloud. Then use each one to simplify something complex from your field.

Signposting

Name three expressions:

🎙 Speak: Give three signposting expressions. Say them aloud. Then use them to structure a 1-minute explanation of anything.

Managing Implicature

Name three expressions:

🎙 Speak: Give three implicature expressions. Say them aloud. Then use them to deliver a potentially sensitive message (feedback, bad news, change of direction).

Reflection Questions

Think deeply about these. Speak your answers.

Question 1: Where do you most struggle to be understood?

Is it in presentations? One-on-one conversations? With certain audiences? When explaining technical ideas? When delivering difficult feedback?

🎙 Speak: Identify one specific context where people sometimes don't understand you, even though your English is good. Describe the situation. What do you think the real breakdown is—vocabulary, grammar, or pragmatics? Speak for 1–2 minutes.

Question 2: Which expressions from this lesson will you use first?

Pick one or two that feel natural to you. Plan where you'll try them.

🎙 Speak: Choose two expressions from the lesson that you'll start using in your next meeting or conversation. Why did you choose those two? How will they help? Where will you try them? Speak for 1 minute.

Question 3: What's the difference between sounding fluent and being clear?

This lesson has been about that gap. What did you learn?

🎙 Speak: Reflect on the difference between fluency (correct grammar, good accent, natural pacing) and clarity (people actually understand your intent). Are they the same thing? Why or why not? How does target language bridge the gap? Speak for 1–2 minutes.

Question 4: How does checking understanding change power dynamics?

Does it make you look weaker? Or stronger?

🎙 Speak: Does asking "Does that make sense so far?" make you sound uncertain or in control? Speak honestly. How do you think your listeners experience that question? Speak for 1 minute.

"I Can..." Statements

Complete these. Speak them aloud. Believe them.

🎙 Speak: Complete these sentences out loud. Be specific and confident:

Final Reflection

The deeper work

This lesson has been about pragmatics—the gap between what you say and what people hear. But it's also been about something bigger: awareness.

Good communicators don't just know how to speak. They know how their words land. They're curious about their listener. They adjust. They check. They care about being understood, not just about being right.

That's not about English. That's about respect.

🎙 Speak: You've learned 16 expressions that make meaning explicit. But the real skill isn't the expressions—it's the mindset behind them. What mindset do these expressions represent? How does using them change how you think about communication? Speak for 2–3 minutes. Be reflective. This is for you, not for assessment.