Fluent Start speaking

Workplace situation · Meetings

Disagreeing in a meeting

Push back on an idea without making it personal, and stay calm when someone pushes back on yours.

Case study: Ritu's silent no

In a design review, a Munich architect proposed moving the whole order service to event streaming in one quarter. Ritu, a senior developer in Pune, knew the team had no streaming experience and a hard client deadline in eight weeks. She said nothing, then complained on the team chat afterward. The plan was approved. Three weeks later the team was firefighting. In the next review, her manager showed her a different way: "I like the direction. My concern is the timeline. Could we pilot it on one service first?" The architect agreed in two minutes, because the pushback came with a reason and a smaller step.

Takeaway: Silence in the meeting is agreement. Disagree with the plan, not the person, and bring an option.

Many of us avoid contradicting a senior person in public, or we say 'yes, yes' and mean no. Global colleagues read silence as agreement and value respectful, specific disagreement, especially in reviews.

Pushing back (you are Senior developer)

Goal: Get your concern on the table, with a reason and an alternative, while keeping the relationship warm.

Step by step

  1. Find the common ground. Agree with the goal before you question the plan.
  2. Name one concern. Be specific: risk, time, cost or data.
  3. Offer an option. A smaller step, a pilot, or a different order.
  4. Invite their view. Ask a real question and listen to the answer.

Say this, not that

I agree we need to scale the order service. My concern is the timeline.No, this will not work.Agreeing on the goal makes the disagreement feel safe.
Can I offer a different view?With due respect, you are wrong.'With due respect' often sounds like the opposite to global ears.
We've got eight weeks to the client deadline, and nobody on the team has run Kafka in production.Facts make the pushback about the plan, not the person.
What if we piloted it on one service first and decided after that?
Am I missing something about why it has to be this quarter?Why are you doing like this?A curious question keeps the door open.

Model conversation

Markus
So the proposal is to move the whole order service to event streaming this quarter. Any objections?
You
Can I offer a different view, Markus? I agree we need to scale the order service. My concern is the timeline.
Markus
Go on.
You
We have eight weeks to the client deadline, and nobody on the team has run Kafka in production yet.
Markus
That's true, but if we wait, we'll be rebuilding under even more pressure.
You
Fair point. What if we pilot it on the notifications service first, and decide on the rest by the end of next month?
Markus
That's a reasonable middle path. Can you write up the pilot scope?
You
Sure. I'll share a one pager by Wednesday.

Rehearse this side out loud

Being challenged (you are Presenter)

Goal: Hear the challenge fully, answer the real concern, and keep your credibility without over defending.

Step by step

  1. Pause and thank. Take a breath. Thank them for raising it.
  2. Check the concern. Restate it so you answer the right question.
  3. Answer briefly. One or two facts. Admit what you don't know.
  4. Agree a next step. Offer to check, test or follow up with a date.

Say this, not that

Good question. Thanks for raising it.No no, that is not correct.A calm first line shows confidence, not weakness.
Just to make sure I understand, your worry is the regression time, right?Restating buys you a few seconds and avoids answering the wrong thing.
You're right that we haven't tested the payment flow on Android yet.Actually it is not my fault, the requirements came late.Owning a gap is more credible than explaining it away.
I don't have that number with me. I'll check and send it by end of day.I think it should be fine only.A guess under pressure can come back to bite you.
Let's take that offline so I can show you the details, if that's okay.

Model conversation

You
So with these changes, we're ready to release on the twelfth.
Priya
Sorry, I have to challenge that. We haven't run the full regression on Android.
You
Good point, Priya, thanks for raising it. Just to check, is your concern the Android payment flow specifically?
Priya
Yes. Last time that flow broke in production.
You
You're right, we haven't covered it yet. It's about four hours of testing.
Priya
So the twelfth is at risk?
You
It's tight but doable. Could your team run it on Monday? If anything fails, I'll flag a new date by Tuesday.
Priya
Monday works. Thanks for not brushing it off.

Rehearse this side out loud

Practice it out loud

Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.

Practice both sides

Related situations