Fluent Start speaking

Workplace situation · Conflict and escalation

Conflict with a teammate

Raise a problem with a teammate directly and kindly, or respond well when one is raised about you.

Case study: The demo that wasn't his

Shreya, a developer in Bengaluru, built the caching layer that made the team's demo fast. In the sprint review, her teammate Tom from Melbourne presented it as "what I put together". She said nothing, complained to two friends, and stopped helping him with reviews. The tension lasted a quarter. On another team, Rahul had a teammate who kept missing handoffs at the end of the Indian day. He asked for a 15 minute call, described two specific handoffs, explained the impact on his morning, and asked what was getting in the way. It turned out the teammate had a school run at that hour. They moved the handoff 30 minutes, and it was fixed.

Takeaway: Talk to the person, not about them. Specific facts, the impact, and a curious question fix most conflicts.

Many of us avoid direct conflict with peers and go to the manager or stay silent. In global teams, a direct, private, respectful conversation with the person is expected first, and it's seen as a sign of trust.

Raising the issue (you are Developer)

Goal: Raise the problem directly and kindly, so Tom understands the impact and you agree what changes.

Step by step

  1. Go private and early. A short 1:1, soon after it happens, not in a group.
  2. Describe, don't accuse. What happened, specifically, without labels.
  3. Share the impact. How it affected you or the work.
  4. Ask, then agree. Ask for their view, then agree what you'll both do next time.

Say this, not that

Hey Tom, do you have fifteen minutes? There's something I'd like to talk about, just between us.Why do you always do this?"Always" turns a fix into a fight.
In the sprint review, the caching layer was presented as something you put together.A specific fact is hard to argue with.
I built most of that, so it felt like my work wasn't visible to the team.You stole my work.Impact on you invites empathy. Accusations invite defense.
I might be missing something. How did you see it?A curious question keeps it a conversation.
Next time, could we present it together, or could you mention who built which part?

Model conversation

You
Hey Tom, do you have fifteen minutes? There's something I'd like to talk about, just between us.
Tom
Sure, what's up?
You
In the sprint review, the caching layer was presented as something you put together. I built most of that, so it felt like my work wasn't visible.
Tom
Oh. I didn't mean it like that. I was just summarizing for the team.
You
That's fair, and I might be missing something. How did you see it?
Tom
Honestly, I was nervous and said "I" without thinking. I'm sorry, you did the hard part.
You
Thanks, I appreciate that. Next time, could we present it together, or mention who built what?
Tom
Absolutely. And I'll mention your work in the next update to the stakeholders.

Rehearse this side out loud

Responding to it (you are Developer)

Goal: Listen without defending, understand the impact, and agree a change that rebuilds trust.

Step by step

  1. Thank them. Raising it directly took courage.
  2. Listen fully. Let them finish. Don't jump in with your side.
  3. Ask to understand. Ask for an example or the impact, to really get it.
  4. Own your part. Even if there's more to the story, own what you did.
  5. Agree a change. One specific thing you'll do differently.

Say this, not that

Thanks for telling me directly, Sanne. I'd rather hear it from you.That's not true at all.Defending first makes them regret raising it.
Can you give me an example, so I understand it properly?Asking for detail shows you're taking it seriously.
That makes sense. I can see how that left your team stuck in the morning.Name the impact back to them.
You're right. I've been rushing the handoff notes, and that's on me.Everyone is busy, I also have many things.Own your part before sharing any context.
From tomorrow, I'll post the handoff by five my time, with the build number and known issues.

Model conversation

Sanne
Hi, I wanted to raise something. Three times this sprint, the handoff notes were missing, and my testers lost the morning.
You
Thanks for telling me directly, Sanne. I'd rather hear it from you. Can you give me an example?
Sanne
On Tuesday, the build had a known login bug, and we spent three hours finding it ourselves.
You
That makes sense. I can see how that left your team stuck.
Sanne
It's frustrating, because we start right when you finish.
You
You're right. I've been rushing the handoff at the end of my day, and that's on me.
Sanne
Thanks for saying that.
You
From tomorrow, I'll post the handoff by five my time, with the build number and known issues. Can we check in next Friday?

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