Listen to this article
Read by Coach Nigel Casey · 5 min read audio
You're a project manager. Your team member delivered a report. It's technically correct. It's also bland, undersold the results, and made your team look unprepared in front of the client. You have to tell them this isn't good enough.
The problem is that you're saying it in English, your second language. And the last time you were direct, they got defensive. The time before that, you hedged so much they didn't understand the problem at all.
Most textbooks will tell you to use the "feedback sandwich." Positive comment, criticism, positive comment again. In theory, it works. In practice, native English speakers have heard this technique so many times that they hear it coming from a mile away. The positive opener signals "bad news incoming." They stop listening.
Here's what actually works: be direct about what's wrong, then show you're still invested in them improving.
The structure that actually works
Wrong version:
"The report was quite good, but the analysis section needed more depth, and the recommendations could have been clearer. Still, I think you have potential."
What they hear: "This is bad, and you're not very good at this."
Right version:
"I need you to rewrite the analysis section. It's too general. It doesn't show the client why our numbers matter. Once you've done that, send it to me and we'll tighten the recommendations together."
The difference: I've told them exactly what's wrong (too general). I've told them exactly what to do (rewrite it). I've signalled that I'm invested in the result (we'll work on it together). No ambiguity. No buried criticism. No false praise.
Three phrases that soften without hiding the problem
"I need you to..."
This is direct. It's also warm. It shows you're making a request, not handing down judgment.
"I need you to cut this by half. It's repetitive."
Not: "Perhaps it could be a bit more concise?" (They won't know how much, and the softness signals uncertainty.)
"The issue is..."
This separates the problem from the person. It's not "You made a mistake." It's "The issue is clarity."
"The issue is the client can't see themselves in this proposal. Add two client examples."
Not: "You didn't put enough examples in." (Sounds like an accusation.)
"Here's what I need to see next time..."
This is future-focused. It moves past the current failure and into what success looks like.
"Here's what I need to see next time: your three strongest data points upfront, then the analysis. Not the other way round."
Not: "Next time, maybe try putting the data points first?" (The "maybe" makes you sound uncertain. They won't prioritise it.)
The dangerous phrase you're probably using
You've likely heard this one: "You could have..." or "You might have considered..."
"You could have included more data analysis."
This sounds polite. But it's actually passive-aggressive. It means "You didn't, and you should have known better." Native speakers hear this as criticism wrapped in false politeness. It makes them defensive.
If there's something they should have done, say so clearly.
"Add more data analysis. The client needs it to understand your conclusion."
What comes after the feedback
This is where most non-native speakers lose it. They deliver the feedback correctly, then immediately soften again. They apologise. They add unnecessary reassurance. They undo the clarity they just created.
You: "I need you to rewrite this section. It's not clear enough."
Them: "OK, I understand."
You: "But, I mean, you did some good work. I just think maybe if you added a bit more... and don't worry, I'm sure you'll get it right next time."
Now they're confused. Was it a real problem, or not?
After you've given the feedback, pause. Let them respond. If they push back or ask for clarification, explain. If they accept it, you're done. Don't fill the silence with reassurance. That erases the message.
The one exception: when they're new or junior
If someone is genuinely early in their career, you can add one sentence of guidance.
"I need you to add a recommendations section. Show the client what we think they should do. I know you haven't done this before. Let me show you an example."
You're still direct. You're still clear about what's wrong. You're just adding one small gesture of support.
How to practise this
The next time you have to give feedback, write down:
- 1.What specifically is wrong?
- 2.What exactly do you want them to change?
- 3.Will you work with them on it, or are they handling it alone?
Then say it. Short sentences. Specific words. No hedging.
If you have a difficult feedback conversation coming up this week, record yourself saying it. Play it back. Do you sound uncertain? Do you apologise? Do you soften at the end? Those are the habits that are costing you clarity.
Better yet, bring the conversation to Thursday's Fluency Clinic. I'll help you rehearse the exact words until they feel natural.
Language Analysis
Select a category above to highlight those words in the text.
Learning Materials
📖 Key Vocabulary
blandadjective · B1
dull or uninteresting, lacking flavour or excitement
“The presentation was technically correct but the language was bland and failed to engage the audience.”
hedgingnoun · B2
using cautious, uncertain language to avoid making a direct statement
“His hedging about the project timeline made it unclear whether he actually supported the proposal.”
feedback sandwichnoun phrase · B2
a technique for delivering criticism by placing negative feedback between positive comments
“Many managers use the feedback sandwich, but employees often see through it immediately.”
to softenverb · B1
to make something less harsh, severe, or direct
“She tried to soften the bad news with kind words, but the message was still clear.”
ambiguitynoun · B2
uncertainty or lack of clarity in meaning
“The ambiguity in his instructions left the team confused about what they should actually do.”
passive-aggressiveadjective · B2
expressing anger indirectly through subtle, often polite criticism
“When she said 'You could have done better,' it felt passive-aggressive rather than constructive.”
to undoverb · B1
to reverse or cancel something that was previously done
“His constant apologies undid all the clarity he had established in the feedback.”
defensiveadjective · B1
reacting in a way that shows you are hurt or angry about criticism
“When given direct feedback, some team members become defensive instead of listening.”
to clarifyverb · B1
to make something clearer or easier to understand
“If they push back on the feedback, clarify exactly what you mean.”
gesturenoun · B1
an action showing kindness, goodwill, or support
“Adding one sentence of guidance is a small gesture of support for a junior team member.”
to prioritiseverb · B1
to treat something as more important than other things
“When feedback feels uncertain, team members don't prioritise making the changes.”
rehearseverb · B1
to practise something, especially words or a performance
“If you have a difficult feedback conversation coming up, rehearse the exact phrases.”
⚙️ Grammar Notes
Direct imperatives without hedging
Using direct commands (imperatives) creates clarity. Avoid softening words like 'perhaps,' 'maybe,' or 'could' when the feedback is important. In professional English, directness signals confidence and is actually more respectful than false politeness.
→“Add more data analysis. The client needs it to understand your conclusion.”
Common mistake: Using 'You could have included more data analysis' instead of 'Add more data analysis.' The conditional weakens the message and can sound passive-aggressive.
Separating person from problem: 'The issue is...' vs 'You are...'
Starting criticism with 'The issue is' creates psychological distance between the person and the problem, making feedback less personal and more constructive. This is particularly important for non-native speakers who want to avoid sounding harsh.
→“The issue is clarity. / The issue is the client can't see themselves in this proposal.”
Common mistake: Saying 'You didn't include enough examples' which makes it sound like a personal failure rather than a fixable problem.
Future-focused statements: 'Here's what I need to see next time...'
Framing feedback as forward-looking expectations rather than dwelling on past mistakes psychologically moves the conversation toward solutions. This structure shows investment in the person's improvement and is more motivating than past-focused criticism.
→“Here's what I need to see next time: your three strongest data points upfront, then the analysis.”
Common mistake: Focusing entirely on what went wrong without explaining what success looks like, leaving the recipient uncertain about how to improve.
Collaborative language: 'We'll work on this together' vs solo task assignment
Including yourself in the solution signals investment and support. The word 'we' in this context means the manager and employee as a team, not the royal 'we.' It softens the feedback while maintaining clarity about the problem.
→“Once you've done that, send it to me and we'll tighten the recommendations together.”
Common mistake: Assigning the entire task to the employee alone, which can feel punitive rather than collaborative, especially for junior staff.
💬 Comprehension Questions
- 1.Why does the feedback sandwich fail with native English speakers?
- 2.What specific phrase does the post recommend instead of 'You could have included more data analysis'?
- 3.What are the three things you should know before giving feedback, according to the post?
- 4.Why does the post suggest NOT adding reassurance immediately after delivering feedback?
- 5.If you were managing a junior employee who delivered unclear work, how would you modify the feedback approach compared to managing a senior colleague?