Giving Feedback in English: Positive and Constructive
CEFR B1-B2 • Business English • SBI structure, hedging, and the wording that makes feedback actually land
Feedback is a vocabulary problem first
You can have the right read on someone's work and still deliver feedback that backfires — because the English phrasing did not land. Native speakers reach for a small, repeatable set of patterns. Non-native managers often translate from their first language and either come across too soft (the message gets lost) or too direct (the person gets defensive). This guide gives you the 30 phrasings that work for positive feedback, constructive feedback, and the hardest case — feedback to your boss.
The SBI structure: Situation, Behavior, Impact
Almost every effective feedback line in English follows this 3-part shape. Memorize it.
| Letter | Means | Example |
|---|---|---|
| S Situation | When and where it happened | "In yesterday's design review..." |
| B Behavior | What specifically you observed | "...you presented three options without recommending one..." |
| I Impact | The effect it had | "...the team left without alignment, and we pushed the decision another week." |
Why SBI works: it makes feedback factual and specific. "You are bad at meetings" feels like an attack. "In yesterday's design review, you presented three options without recommending one — the team left without alignment" is observable and actionable.
Positive feedback that actually motivates
Generic praise ("great job!") is forgettable. Specific praise ("the way you reframed the budget question saved us 30 minutes") is what people remember a year later.
"I want to call out the way you handled the customer escalation last week — specifically, the move to bring in legal early. That saved us from a much bigger problem."
"Call out" = highlight. SBI structure throughout. Names the specific behavior.
"I noticed in yesterday's meeting that you pulled Marina into the conversation when she had been quiet — and her input changed the direction. That kind of move is exactly what I want to see more of."
"I noticed" = observational. "Exactly what I want to see more of" = explicit ask for repetition.
"The Q3 deck you put together was the strongest I have seen from anyone on the team this year. Specifically, the way you anticipated the CFO's questions and addressed them in the appendix — that is senior-level work."
Compares to peer benchmark + names the specific senior behavior.
"I have been meaning to thank you for the runbook you wrote after the May incident. I have used it three times since — it is the kind of artifact that pays off long after you wrote it."
Delayed thank-you with concrete usage. Stronger than immediate "great work."
"One thing you do really well is breaking complex topics into clear bullet points. The migration plan you sent yesterday is a good example."
Names the strength + ties to a recent specific example.
Constructive feedback that does not bruise
The hardest English to write. Here is the script:
"I want to share something I noticed, and I want to be direct because I think it is fixable: in the last two design reviews, you committed to a position before the team had finished sharing concerns. I think two engineers stopped raising issues."
Permission opener + reason for directness + SBI. The full pattern.
"One thing I want to flag is the response time on customer escalations — they have been averaging 36 hours, and the SLA is 24."
"Flag" = "raise gently." Numbers make it factual, not personal.
"Can I share an observation? In the last three weeks, you have been responding to Slack messages at 11 PM. I want to flag that because it sets a norm for the team I do not think we want."
"Can I share an observation?" = explicit consent for feedback. Polite reset.
Asking permission first (the most-skipped move)
Especially with peers, asking before delivering feedback dramatically improves how it lands.
"Mind if I share some feedback on the doc?"
The simplest permission ask. Native speakers use it constantly.
"Are you open to a piece of constructive feedback on the talk?"
"Are you open to" = give them an out. Stronger than "can I tell you..."
"I have some thoughts on how the meeting went — happy to share if you want them."
"Happy to share if you want them" = optional, no pressure.
Giving feedback to your boss (the hardest case)
This requires more hedging, but the structure is the same. The phrase "from where I sit" does a lot of work.
"From where I sit on the team, the all-hands meetings have been running long — the last three were over an hour. I worry it is signaling that punctuality is not a real value, especially for the new hires."
"From where I sit" + "I worry it is signaling" = upward feedback formula.
"Can I share an observation about something I would do differently? The way the reorg was announced — without a written summary — meant my team had three days of speculation before the details came out. What I would have valued was a one-pager at the announcement."
"What I would have valued" = polite version of "what should have happened."
Feedback patterns by audience
| Audience | Hedge level | Recommended opener |
|---|---|---|
| Direct report (close working relationship) | Light hedging | "I want to share something I noticed..." |
| Direct report (new or distant) | Medium hedging | "Can I share an observation? In yesterday's..." |
| Peer | Medium-heavy hedging | "Mind if I share some feedback on the X?" |
| Boss (close relationship) | Heavy hedging | "From where I sit, I worry that..." |
| Boss (formal relationship) | Maximum hedging | "Could I share an observation when you have a few minutes?" |
Receiving feedback gracefully
Equally important and often missed by non-native speakers. The standard responses:
"Thanks for that — let me sit with it for a day before I respond properly."
"Sit with it" = process before reacting. Shows maturity.
"That is hard to hear, and I want to take it seriously. Can you give me a specific example of when you saw it?"
Acknowledges difficulty + asks for specificity. Strongest receiver pattern.
"I appreciate you sharing that. A few questions to make sure I understand..."
Acknowledge + ask to clarify. Standard professional response.
Mistakes to avoid
- "You always" or "You never" — absolutes invite defense. Use "in the last two meetings" instead.
- "Don't take this personally" — guarantees they will. Skip the disclaimer and just deliver SBI.
- "Honestly..." as an opener — implies you usually are not honest. Just state the observation.
- "No offense, but..." — same problem as "with all due respect." Offense is coming.
- Sandwiching feedback (good-bad-good) — readers learn to skip the good and brace for the bad. Just deliver the feedback directly.
Practice: Test yourself
Tap each question to reveal the answer.