How to Give Honest Feedback in English at Work
ESL English learning: Master vocabulary for honest feedback vs sycophancy in code reviews, design debates, and 1:1s at tech companies.
Pronunciation Guide: Tricky Terms
Several of these vocabulary items have unusual pronunciations that can trip up non-native speakers. Pay special attention to stress patterns and vowel sounds.
obsequious /əbˈsiː.kwi.əs/
ob-SEE-kwee-us
Saying 'ob-SEK-wee-us' with wrong vowel in second syllable
sycophant /ˈsɪk.ə.fənt/
SIK-uh-funt
Saying 'sy-KOH-fant' with wrong stress and vowel
ingratiating /ɪnˈɡreɪ.ʃi.eɪ.tɪŋ/
in-GRAY-shee-ay-ting
Skipping syllables: 'in-GRAT-ing'
servile /ˈsɜː.vaɪl/
SUR-vile
Saying 'SER-vil' with short 'i' sound
smarmy /ˈsmɑː.mi/
SMAR-mee
Pronouncing as 'SWARM-ee'
Why Honest Feedback Vocabulary Matters in Tech
In tech workplaces, the pressure to agree with senior colleagues or avoid conflict can lead to sycophantic behaviour—empty praise, fake agreement, and feedback that prioritises harmony over honesty. This creates real problems: bugs ship because nobody questioned the architecture, design flaws persist because juniors felt they couldn't push back, and performance reviews become meaningless when everyone says 'great job' regardless of actual output.
Learning vocabulary to identify and avoid these dynamics helps you communicate with integrity. Whether you're reviewing a pull request, debating an RFC, or giving feedback in a 1:1, you need words that let you be direct without being rude—and that help you recognise when others are being sycophantic rather than genuinely supportive.
Culture Note
In many tech companies, especially those with flat hierarchies, honest disagreement is valued more than polite agreement. Saying 'I have concerns about this approach' to a staff engineer is often more respected than saying 'Looks great!' when you actually see problems.
Key Vocabulary: Words for Flattery and People-Pleasing
These terms help you identify and discuss problematic agreement patterns in your team. Some are useful for self-reflection ('Am I being sycophantic in this review?'), while others help you describe dynamics you observe.
| Term | Part of Speech | Tech Workplace Definition | Example Context |
|---|---|---|---|
| sycophantic | adjective | Flattering someone in power to gain personal advantage | Praising a tech lead's flawed design to stay on their good side |
| obsequious | adjective | Excessively eager to please or obey | Agreeing with every comment in a code review without critical thought |
| smarmy | adjective | Showing insincere charm; overly smooth | Complimenting a hiring manager's 'brilliant questions' during a panel |
| servile | adjective | Submissive in a way that suggests trying to gain favour | Always volunteering for a manager's tasks while ignoring team priorities |
| ingratiating | adjective | Deliberately acting to win someone's approval | Laughing at a director's jokes before the punchline in all-hands |
| toady | noun/verb | A person who flatters to gain advantage; to act this way | The team toady always agrees with whatever the PM suggests |
- Sycophantic behaviour often stems from fear of conflict, not bad intentions—recognising this helps you address it constructively.
- These words have strong negative connotations. Use them carefully in professional settings—usually for self-reflection or trusted conversations, not public criticism.
- The noun forms are: sycophancy, obsequiousness, smarminess, servility, ingratiation.
Scenario 1: Giving Honest Feedback in a Code Review
A senior engineer submits a PR with a complex caching implementation. You notice a potential race condition, but the engineer is well-respected and you're new to the team. The sycophantic response is to approve with 'LGTM, great work!' The honest response requires specific vocabulary and phrasing.
| ❌ Sycophantic (Avoid) | ✅ Honest & Constructive |
|---|---|
| LGTM! Really elegant solution. | I like the approach, but I have a question about line 47—could there be a race condition if two requests hit this cache simultaneously? |
| This is perfect, nothing to add! | The logic is clear. One thought: have we considered what happens when the cache invalidation fails? |
| Brilliant as always! Ship it. | This handles the happy path well. I'd suggest adding a test for the edge case where the upstream service times out. |
| I'm sure you've thought of everything. | I might be missing context, but I'm not sure why we're using a map here instead of a set. Could you clarify? |
Grammar Pattern: Hedging Without Being Weak
Use modal verbs and conditional structures to soften pushback while remaining substantive: 'Could there be...' 'Have we considered...' 'I might be missing context, but...' These hedges show respect without being obsequious.
Scenario 2: Avoiding Sycophancy in a Senior Design Discussion
You're in an RFC review meeting. The principal engineer presents an architecture that you believe has scalability concerns. Other engineers are nodding along. Speaking up feels risky, but staying silent is servile behaviour that could hurt the project long-term.
- Frame concerns as questions: 'How would this handle 10x our current load?' sounds collaborative, not confrontational.
- Separate the idea from the person: 'I have concerns about this approach' not 'I disagree with you.'
- Acknowledge what works first: 'The event-driven model makes sense for our use case. My concern is specifically about the state management piece.'
- Use 'we' language: 'Have we stress-tested this pattern?' includes everyone in the responsibility.
Watch for ingratiating behaviour in yourself and others: excessive agreement ('That's exactly what I was thinking!'), laughing at every comment, or prefacing every point with 'This is probably a stupid question, but...' These patterns signal discomfort with honest disagreement.
Scenario 3: Recognising When Agreement Masks a Problem
In standups and planning meetings, unanimous agreement can be a red flag. When everyone quickly says 'sounds good' to a complex proposal, it may indicate sycophancy, fear of conflict, or simply that people aren't paying attention. Here's vocabulary for surfacing real concerns.
| 🚩 Phrases That Mask Problems | ✅ Phrases That Surface Concerns |
|---|---|
| No concerns from me. | Let me think about this and follow up async if I have questions. |
| Whatever you think is best. | I'd like to understand the tradeoffs before committing. |
| I'm sure it'll work out. | What's our rollback plan if this doesn't perform as expected? |
| The team lead knows best. | Could we timebox this approach and revisit if we see issues? |
Culture Warning
In some team cultures, 'No concerns' is a genuine signal of confidence. In others, it's a polite way to end discussion. Learn your team's norms, but when stakes are high, it's better to slow down and ask clarifying questions than to be obsequiously agreeable.
Register: Slack Messages vs. Formal Documentation
The vocabulary of honest feedback shifts between casual Slack conversations and formal written feedback in performance reviews or design documents.
| Context | Casual (Slack/DM) | Formal (Doc/Review) |
|---|---|---|
| Raising a concern | Hey, quick thought on that PR—are we sure about the caching logic? | I have identified a potential concern with the proposed caching implementation that warrants further discussion. |
| Disagreeing | Hmm, I'm not sure I follow the reasoning here 🤔 | I would like to better understand the rationale behind this architectural decision. |
| Pushing back | This feels risky tbh—can we talk through the failure modes? | Before proceeding, I recommend we conduct a failure mode analysis to assess potential risks. |
| Acknowledging uncertainty | I might be wrong but... | While I may not have full context, my initial assessment suggests... |
Practice Exercises
Multiple choice
Choose the best answer.
A colleague always agrees with the tech lead's suggestions without asking questions, even when the suggestions have obvious problems. Which word best describes this behaviour?
Multiple choice
Choose the best answer.
You're reviewing a PR and notice a potential bug, but the author is a senior engineer. Which response demonstrates honest feedback without being rude?
Complete the sentence
Type the missing word or phrase.
Complete the sentence: His ______ compliments to the hiring manager were obvious to everyone on the panel—he praised every question as 'brilliant' even when they were basic.
Multiple choice
Choose the best answer.
In a design review meeting, everyone quickly says 'sounds good' to a complex architecture proposal. What is the most professional way to slow down the discussion?