Collaboration starts with understanding how we talk to each other

When I moved from France to Canada, I kept accidentally offending people in meetings.

In France, direct feedback is respect. You push back, you debate, you argue your point. That’s how you show someone you take them seriously. In Canada, that same directness reads as aggressive. Feedback is softer, more considered, wrapped in qualifiers. Same intent, completely different delivery.

I had to relearn how to communicate with people who weren’t wrong, just different. Most communication breakdowns in teams aren’t about bad intentions. They’re about invisible assumptions.

The gaps nobody talks about

Every team has them. Some people want the conclusion first, then the reasoning. Others need the context before they can evaluate anything. Some think out loud and arrive at their position by talking through it. Others process privately and come back with a fully formed opinion, and feel steamrolled if they’re pushed for a reaction in real time.

In meetings, the loudest voices naturally dominate. That’s not always who has the best ideas. An engineer who needs a moment to collect their thoughts before speaking is often the one who sees the flaw nobody else caught, but they leave without saying it because the conversation moved on.

Cultural and linguistic differences add another layer. A phrase that reads as casual irony to one person sounds like genuine criticism to another. Technical jargon that’s obvious to someone who’s been writing APIs for ten years is genuinely opaque to someone newer to back-end work. None of these are failures. They’re just the reality of building things with humans who aren’t identical.

These gaps don’t resolve themselves. They either get addressed intentionally or they fester into recurring friction that nobody knows how to name.

Three things that actually help

Retrospectives that go beyond tickets. The standup-and-sprint-review cadence is good for tracking work. It’s not good for surfacing the question “are we actually communicating well?” A retro that only covers what was shipped and what was blocked misses half the team’s experience. I’ve found that simply asking “was there a moment this sprint where you felt unheard or unclear?” opens conversations that wouldn’t happen otherwise.

Anonymous pulse checks. Not everyone is comfortable raising a concern in a group, especially when that concern is about the group’s dynamics. A short, anonymous survey run every few weeks can surface isolation, frustration, or communication friction before it becomes disengagement. Keep it short: five questions, not twenty. The goal is early signal, not comprehensive data.

Team READMEs. This one takes more effort but has the highest lasting impact. Each team member writes a short document about how they work: how they like to receive feedback, how they prefer to be approached when something’s wrong, what they need to feel included in a discussion, when they do their best thinking.

READMEs make the invisible visible. Instead of spending months accidentally learning that someone hates being put on the spot in meetings, or that another person needs to hear “good job” occasionally to stay motivated, you start with a baseline of understanding. It reduces the time people spend guessing and the friction that comes from getting it wrong.

The manager’s job in all of this is not to make everyone communicate the same way. It’s to create enough structure that different styles can coexist, to make sure the quiet person gets heard, to catch the pattern where feedback from one person consistently lands wrong on another, and to normalize the conversation about how we work together, not just what we’re working on.

Collaboration on a diverse team doesn’t happen automatically. It happens because someone made it their job to pay attention.