Raising a Concern
How to object without sounding negative. The four registers, softening with modals, "valid concern" replies, the about/with line, standup vs client-call variants, the я переживаю trap, two dialogues, and a quiz.
When you need this
Something in the plan is wrong and you have to say so — to a lead, a client, or a room that has already half-decided. English has a dedicated move for this, and it is not disagreement. You put a concern on the table: an item, not an emotion, that the room can pick up and answer.
Get this wrong in either direction and you pay for it. Too blunt ("this is a problem") and you're the difficult one; too soft ("maybe it's fine, I don't know") and nobody registers that you objected at all.
- You can see a risk the room hasn't priced in — coupling, scope, a deadline that assumes nothing goes wrong.
- You disagree with a decision but don't own it.
- You need the objection on the record without making it personal.
- You're reviewing someone's work and something needs to change before it ships.
- A client's requirements have moved and the estimate hasn't.
Register ladder
The same move at four levels of formality. Pick the rung, not the phrase.
Casual
Friends, teammates you know well, Slack banter.
- "Wait — what happens when two people hit this at once?"
- "Hmm, this bit worries me."
- "Not sure about this one, honestly."
Fine with your own team, in Slack, mid-thread. Too loose for a client — it reads as thinking aloud, not as an objection.
Neutral
The default at work — standups, most Slack, most email.
- "I have a concern about the timeline."
- "One thing I'm not sure about: we'd be duplicating state across two services."
- "Can I flag something before we move on?"
The default at work. Use this rung unless you have a reason not to.
Professional
Clients, other teams, anyone senior, anything on the record.
- "Before we commit, I'd like to raise a concern about the migration path."
- "My main concern is that this couples us to a third-party API we don't control."
- "I want to voice one concern about the estimate — can I walk through it?"
Clients, other teams, anyone senior, anything written down. Note the pattern: raise / voice + concern + about.
Formal
Contracts, complaints, first contact, legal and HR.
- "We wish to express our concern regarding the proposed delivery date."
- "Our primary concern is the absence of a rollback plan."
- "We would like to place on record a concern about the change in scope."
Contracts, complaints, anything a lawyer might read. Rare in speech — if you say this in a standup you'll sound like you're threatening to sue.
Channel variants
The register holds; the length changes. A call gets a sentence, an email gets a paragraph.
Call
- "Can I raise a concern before we move on?"
- "Sorry — one concern on that, quickly."
- "Can I push back gently on that?"
Say the concern in one sentence, then stop. On a call, the trap is explaining for ninety seconds and losing the room before you reach the point.
Standup
- "No concerns from my side."
- "One concern: the migration script hasn't been tested against prod-sized data."
- "Nothing blocking, but I want to flag a concern for later."
Standup wants the headline only. If it needs discussion, say so and take it offline.
Slack
- "flagging a concern on this — we'd be duplicating state across two services 🧵"
- "one concern before I approve: no error handling on the retry path"
- "not blocking, just a concern: this assumes the webhook always fires"
Lowercase and short is normal. Put the detail in a thread so the channel stays readable.
- "Before we finalise scope, I have a couple of concerns I'd like to walk through."
- "One concern: the current estimate assumes the API contract is stable. If that changes, the timeline moves."
- "Happy to be talked out of this, but I wanted it on the record."
Email is the one channel where you name the concern and propose the fix — the reader can't ask a follow-up question in the moment.
In person
- "Got a minute? I have a concern about Friday."
- "Can I think out loud at you for a second?"
Face to face you can be softer, because tone carries the seriousness that written English has to spell out.
The reply side
Half of any situation is what you say back.
- "That's a valid concern."
- "That's a fair concern — let me address it."
- "Good point. I hadn't thought about the retry path."
- "I share that concern, actually."
- "Let me try to allay that: we already have a fallback if the webhook doesn't fire."
- "Fair — but the risk is bounded, because it only affects the admin path."
- "You're right. Let's not ship it until that's handled."
- "I hear the concern, but I think the risk is manageable."
- "I take the point, though I'd weigh it differently — shipping late costs us more here."
- "That's a real risk, but I don't think it should block this release."
- "Can we note that concern and come back to it after the demo?"
- "Let's log it — I don't want to lose it, but it's not this sprint."
Traps for Ukrainian and Russian speakers
- ❌ "I worry that the deadline is too tight."
- ✅ "I'm concerned that the deadline is too tight."
- A direct translation of я переживаю / я беспокоюсь. I worry reports a feeling and sounds personal; I'm concerned states a position. In a meeting you always want the second.
- ❌ "I have a concern to you."
- ✅ "I have a concern about the estimate." / "I'd like to raise a concern with you."
- The concern is about the thing and raised with the person. Never to.
- ❌ "This is a problem."
- ✅ "I have a concern about this."
- Naming a problem assigns blame and invites defence. Naming a concern invites an answer — same information, opposite reaction.
- ❌ "It doesn't concern me."
- ✅ "That's outside my scope." / "That doesn't apply to me."
- Sounds like not my problem, don't ask me — cold, sometimes rude. Not a neutral way to say a topic is unrelated to you.
- Don't apologise for objecting. "Sorry, maybe this is stupid, but…" throws away the authority you need for the objection to land. "Can I raise a concern?" is already polite.
- One concern per turn. Stacking three at once means the room answers the easiest and forgets the other two — lead with the one that would change the decision.
Mini dialogues
Two short exchanges — read them aloud once each.
- Lead: So we're saying the migration lands Thursday?
- You: Can I flag a concern before we commit to that?
- Lead: Go ahead.
- You: My concern is that Thursday assumes the script runs clean on prod-sized data, and we've only tested on a sample.
- Lead: That's fair. How long to test against a real snapshot?
- You: Half a day. I'd rather spend it now than roll back on Friday.
- Lead: Agreed — let's say Monday and do it properly.
- Client: And we'd want the dashboard in the same two weeks, obviously.
- You: Before we finalise that, I have a concern I'd like to walk through.
- Client: Sure.
- You: My concern is that the dashboard wasn't in the estimate we agreed — it roughly doubles the front-end work.
- Client: Hmm. We do need it, though.
- You: Understood. If cost is a concern, we can phase it — core flows in two weeks, dashboard the week after.
- Client: That works. Let's do it that way.
Don't say this
- ❌ "I don't like this approach." — personal and unanswerable — nobody can address your taste.
- ❌ "That's wrong." — blunt to the point of hostile; leaves the other person nowhere to go but defence.
- ❌ "Sorry, this is probably a stupid question, but…" — pre-discounts your own objection, so the room discounts it too.
- ❌ "I worry so much about this deadline." — emotional register; sounds like anxiety rather than analysis.
- ❌ "Whatever, it's your call." — passive-aggressive withdrawal — it reads as a threat to say "I told you so" later.
- ❌ "I have a concern to the timeline." — wrong preposition; concerns are about things.
Practice
Choose the better option for each prompt.
1.Neutral register, in a standup: "I ___ a concern about the timeline."
2.Professional register: "I'd like to ___ a concern about the migration path."
3.Concerns are always ___ something, never to it.
4.Accepting someone else's objection: "That's a ___ concern."
5.Reassuring them: "Let me try to ___ that concern — we have a fallback."
6.The register you want in a meeting: "I'm ___ that the deadline is too tight."