How to Raise Concerns and Push Back in English at Work
ESL English learning: Master vocabulary and phrases for raising concerns, pushing back on decisions, and escalating issues professionally in tech workplaces.
Why Raising Concerns Professionally Matters in Tech
Every tech professional needs to push back sometimes — on unrealistic deadlines, questionable technical decisions, or process problems. But in English, the difference between 'raising a concern' and 'complaining' often comes down to a few key word choices.
Native speakers intuitively adjust their register (formality level) based on context: a Slack message to a teammate sounds different from an escalation email to leadership. For ESL speakers, mastering this register shift is crucial for being heard without damaging relationships.
This article covers the vocabulary, phrases, and cultural patterns you need to voice concerns effectively in standups, design reviews, 1:1s, and written communication.
Core Vocabulary for Raising Concerns
English has many verbs for expressing dissatisfaction, ranging from mild to strong. In tech workplaces, choosing the right verb signals whether you're flagging a small issue or escalating a serious problem.
| Term | Strength | Tech Workplace Usage |
|---|---|---|
| raise a concern | mild | The standard professional phrase. 'I'd like to raise a concern about our testing coverage.' |
| push back (on) | moderate | To resist or question a decision. 'We pushed back on the Q3 deadline.' |
| object (to) | moderate-strong | Formal disagreement. 'I object to deploying without load testing.' |
| flag (something) | mild | Bring attention to a potential issue. 'I want to flag a risk in this approach.' |
| escalate | strong | Move an issue to higher authority. 'If this isn't resolved by Friday, I'll need to escalate.' |
| take exception to | strong/formal | Express strong disagreement. 'I take exception to that characterization of our team's work.' |
Grammar Note: 'Object to' + Gerund
The verb 'object to' is followed by a noun or -ing form, never a base verb. Say 'I object to being asked to cut corners' — not 'I object to be asked.' This is a common mistake that sounds unnatural to native speakers.
Slack vs. Email: Adjusting Your Register
The same concern requires different language depending on the channel. A casual Slack message to your team lead uses different vocabulary than a formal escalation email to a VP. Here's how the same message transforms across registers.
| Informal (Slack/DM) | Formal (Email/Doc) |
|---|---|
| Hey, I'm a bit worried about this timeline. | I have concerns about the feasibility of the proposed timeline. |
| This doesn't feel right to me. | I'd like to raise an objection to this approach. |
| Can we talk about this? Something's off. | I believe this warrants further discussion before we proceed. |
| I'm not sure this is gonna work. | I have reservations about the viability of this solution. |
| We really need to loop in [manager] on this. | I recommend escalating this to [manager] for visibility. |
Culture Tip: 'Soft No' in American Tech Culture
In many American tech companies, direct 'no' statements are avoided. Instead, people say 'I have some concerns' or 'I'm not sure this is the right approach' — which often means 'I disagree.' Learning to read (and use) these soft signals is essential for effective communication.
Scenario 1: Raising a Concern in a Team Meeting
Imagine you're in a design review and the proposed architecture has a scalability problem you've spotted. You need to raise this concern without sounding like you're attacking the author's work.
The key is to frame your concern as a question or observation, not an accusation. Use hedging language to soften the impact while still being clear about the issue.
- ❌ 'This design won't scale. It's going to fail in production.' (Too direct, sounds like an attack)
- ✅ 'I'm wondering if we've considered how this handles 10x the current load? I have some concerns about scalability.'
- ❌ 'You didn't think about edge cases.' (Accusatory 'you' statement)
- ✅ 'One thing I'd like to flag — have we covered the edge case where the user session expires mid-transaction?'
- ❌ 'This is wrong.' (Blunt, relationship-damaging)
- ✅ 'I might be missing something, but I'm seeing a potential issue with the caching strategy here.'
Phrase Bank: Hedging Your Concerns
Use these openers to soften technical pushback: 'I might be missing context, but...', 'Have we considered...?', 'I want to flag a potential risk...', 'My concern is...', 'I'm wondering if...', 'Could you help me understand...?'
Scenario 2: Pushing Back on an Unrealistic Deadline
Your PM has just committed the team to a two-week deadline that you know is impossible without cutting corners. How do you push back without sounding negative or uncooperative?
The most effective strategy is to reframe the conversation around trade-offs rather than simply saying 'no.' This shows you're solution-oriented while being honest about constraints.
| Heard at Work (Problematic) | Better English |
|---|---|
| That's impossible. | To hit that date, we'd need to descope features X and Y. |
| We can't do that. | I have concerns about the timeline. Can we discuss trade-offs? |
| The deadline is unrealistic. | Based on our velocity, a realistic estimate is [date]. What can we adjust? |
| You're asking for too much. | I want to make sure we're aligned on what's achievable given our current capacity. |
Notice how the 'better' versions avoid accusatory 'you' statements and focus on facts (velocity, capacity) rather than emotions. They also invite collaboration by asking questions or offering alternatives.
Scenario 3: Escalating a Blocker in Slack Without Sounding Aggressive
You've been waiting three days for another team to unblock your PR, and you need to escalate. But you don't want to sound aggressive or create tension. Here's a template that works.
- Step 1: State the fact neutrally. 'The PR for [feature] has been waiting for review since Monday.'
- Step 2: Explain the impact. 'This is blocking our release, which is scheduled for Thursday.'
- Step 3: Make a clear ask. 'Could someone take a look today, or should I escalate to [manager]?'
- Step 4: Keep the tone collaborative. End with 'Happy to discuss if there are concerns about the changes.'
Full example: 'Hey team 👋 The PR for the auth refactor (#2847) has been pending review since Monday. This is blocking our Thursday release. Could someone take a look today? Happy to jump on a call if that helps. If this isn't possible, I may need to escalate to [manager] for visibility. Thanks!'
This message is firm but not aggressive. It states facts, explains impact, and offers collaboration before mentioning escalation.
Pronunciation Guide: Tricky Terms
Several key terms in this vocabulary set have pronunciation challenges for ESL speakers. Pay attention to stress patterns and vowel sounds.
escalate /ˈeskəleɪt/
ES-kuh-late (stress on first syllable)
Saying 'es-ka-LATE' with stress on the last syllable
object (verb) /əbˈdʒekt/
ob-JECT (stress on second syllable for verb)
Saying 'OB-ject' (noun stress) when using the verb
feasibility /ˌfiːzəˈbɪləti/
fee-zuh-BIL-uh-tee
Saying 'fee-ZAY-bility' with wrong vowel sound
concern /kənˈsɜːrn/
kun-SURN (stress on second syllable)
Pronouncing 'con' like 'cone' instead of schwa
viable /ˈvaɪəbl/
VY-uh-bul (two syllables, not three)
Saying 'vi-AY-bull' as three syllables
Practice Exercises
Multiple choice
Choose the best answer.
You need to tell your PM that a two-week deadline is not achievable. Which response is most professional?
Multiple choice
Choose the best answer.
Complete the sentence: 'I _____ to being asked to deploy without proper testing.'
Multiple choice
Choose the best answer.
Which phrase would be most appropriate for a formal escalation email to a VP?
Multiple choice
Choose the best answer.
In American tech culture, when a colleague says 'I have some concerns about this approach,' what do they typically mean?