How to Give Critical Feedback in English at Work
ESL English learning: Master pushback and conflict vocabulary for code reviews, design critiques, and technical debates without sounding aggressive.
Pronunciation Guide: Conflict Vocabulary
These terms are frequently mispronounced by non-native speakers. Pay attention to stress patterns—English stress can completely change how professional you sound.
dispute /dɪˈspjuːt/
di-SPYOOT
Stressing first syllable: DIS-pute
contention /kənˈtenʃən/
con-TEN-shun
Pronouncing as 'con-TENSION'
dissent /dɪˈsent/
di-SENT
Confusing with 'descent' /dɪˈsent/
altercation /ˌɔːltərˈkeɪʃən/
al-ter-KAY-shun
Stressing wrong syllable: AL-ter-cation
squabble /ˈskwɒbəl/
SKWOB-ul
Pronouncing 'qu' as /kw/ separately: s-KWA-ble
Why Conflict Vocabulary Matters in Tech
Technical work is full of disagreement—and that's healthy. Whether you're reviewing code, debating architecture in an RFC, or giving feedback in a 1:1, you need vocabulary that's direct enough to be clear but calibrated enough to maintain working relationships.
Many ESL engineers default to either overly soft language ('maybe this could possibly be better?') or accidentally harsh phrasing ('this is wrong'). Neither serves you well. This article gives you the precise vocabulary to navigate pushback, dissent, and contentious debates like a native speaker.
The Goldilocks Zone of Feedback
In tech culture, good feedback is specific, actionable, and respectful. The vocabulary you choose signals whether you're collaborating or attacking. Master these words to hit the right register every time.
Core Conflict and Pushback Vocabulary
These terms range from mild disagreement to serious opposition. Knowing when to use each helps you calibrate your message precisely.
| Term | Definition | Tech Workplace Example |
|---|---|---|
| dispute (n./v.) | A formal disagreement or to argue against something | There's an ongoing dispute about whether to use REST or GraphQL for the new API. |
| contention (n.) | A point of disagreement; also competition for a resource | The main contention in this RFC is around database schema migration strategy. |
| dissent (n./v.) | To disagree, especially with a majority view | Two senior engineers dissented from the team's decision to adopt microservices. |
| squabble (n./v.) | A petty argument over minor details | Let's not squabble over variable naming conventions—pick a style guide and move on. |
| altercation (n.) | A heated verbal argument | The retrospective turned into an altercation when blame was assigned unfairly. |
| wrangle (v./n.) | To argue noisily or wrestle with a problem | We wrangled over the deployment strategy for two sprints before reaching consensus. |
- Dispute and contention are neutral/formal — safe for RFCs and design docs
- Squabble implies the argument is petty — use carefully to avoid dismissing others
- Altercation signals things got too heated — usually describes a problem, not a goal
- Dissent is professional and valued in tech — expressing dissent shows independent thinking
Scenario: Giving Critical Feedback in a Code Review
Code reviews require you to point out problems without making the author defensive. The goal is to dispute the code, not attack the coder. Here's how to use conflict vocabulary professionally.
| ❌ Too Aggressive | ✅ Professional Pushback |
|---|---|
| This is wrong. | I'd dispute this approach—the edge case on line 47 could cause a null pointer exception. |
| Why did you do it this way? | I have some contention with this pattern. Could we discuss the tradeoffs? |
| This doesn't make sense. | I'm having trouble following the logic here. Can you walk me through your reasoning? |
| You should have used a different algorithm. | There's an alternative algorithm that might reduce time complexity. Worth considering? |
The 'I' Statement Technique
Frame pushback as your perspective: 'I have contention with...' or 'I'd dispute...' This sounds collaborative rather than accusatory. It invites discussion instead of triggering defensiveness.
Scenario: Responding to Combative Feedback in a Meeting
Sometimes you're on the receiving end of harsh feedback. Maybe a stakeholder is frustrated, or a colleague is being unnecessarily aggressive. Here's vocabulary to de-escalate while still holding your ground.
| Situation | De-escalation Phrase | Why It Works |
|---|---|---|
| Someone attacks your work publicly | I hear your dissent. Can you help me understand the specific concern? | Validates their right to disagree while requesting specifics |
| A discussion becomes an altercation | Let's table this for now and revisit when we have more data. | Creates space without dismissing the issue |
| Petty squabbling over details | This feels like we're squabbling over implementation details. What's the core disagreement? | Names the behavior neutrally and refocuses |
| Someone dismisses your technical opinion | I'd like to respectfully dissent. Here's my reasoning... | Asserts your position professionally |
- Never match aggression with aggression — you lose credibility
- Use 'I hear...' to acknowledge without agreeing
- Ask clarifying questions to shift from emotion to logic
- Naming the dynamic ('this feels like squabbling') can reset the conversation
Scenario: Describing a Contentious Debate in a Team Update
When reporting on technical discussions to leadership or other teams, you need neutral vocabulary that conveys the substance without drama. Here's how to describe conflict professionally.
| ❌ Too Dramatic / Informal | ✅ Professional Summary |
|---|---|
| The team had a big fight about the architecture. | There was significant contention around the proposed architecture. |
| People were arguing for hours. | The team engaged in extended debate before reaching consensus. |
| Some people wouldn't agree with anything. | Several engineers expressed dissent regarding the timeline. |
| It got pretty heated in the meeting. | The discussion was vigorous, with strong opinions on both sides. |
Register Matters
In Slack, you might say 'we wrangled over this for a while.' In a status email to leadership, write 'there was contention that has now been resolved.' Match your vocabulary to your audience.
Grammar Patterns for Professional Pushback
The grammar structures you use can soften or sharpen your pushback. Here are patterns that sound professional in tech contexts.
| Pattern | Example | Effect |
|---|---|---|
| I'd + verb | I'd dispute that assumption. | Conditional softens the statement |
| There's + noun + around | There's some contention around this approach. | Depersonalizes the conflict |
| Could we + verb | Could we revisit the tradeoffs here? | Invites collaboration |
| I'm inclined to + verb | I'm inclined to dissent on this point. | Shows thoughtful disagreement |
| The concern is that... | The concern is that this won't scale. | Focuses on the issue, not the person |
Avoid Absolute Language
Words like 'always,' 'never,' and 'obviously' escalate conflict. Replace 'This will never work' with 'I have concerns about whether this will work.' The vocabulary of certainty often triggers defensive responses.
Practice Exercises
Test your understanding of conflict vocabulary in tech workplace contexts.
Multiple choice
Choose the best answer.
Which word best describes a petty argument over minor code style preferences?
Multiple choice
Choose the best answer.
In a design document, which phrase sounds most professional for describing disagreement?
Complete the sentence
Type the missing word or phrase.
Complete this professional response to aggressive feedback: 'I hear your ______. Can you help me understand the specific concern?'
Multiple choice
Choose the best answer.
Which grammar pattern best softens critical feedback in a code review?