Swift Trust: How New International Teams Build Trust Without a Shared History

Your new international team just kicked off. Everyone’s warm, generous, quick to give the others the benefit of the doubt when a message lands badly or a deadline slips. Three months later, that warmth has gone. People are double-checking each other’s work. Messages that used to be casual have suddenly become formal. Meetings that used to run loose now feel guarded. Nobody can point to the exact day it happened; the warmth just drained away quietly in the background while everyone was getting on with their work. If that sounds familiar, you haven’t imagined it — and it’s not a sign your team was never gelling. There’s a name for what happened, and it’s been studied for decades. Once you understand the mechanism behind it, you can catch it happening in real time, instead of noticing three months in that something’s off. Twenty minutes or thereabouts, one real problem, and what you can actually do about it. Today: why the trust in your new international team is more fragile than it feels, and what to do before it quietly drains away. Let’s go.

Here’s the pattern I see constantly with new international teams. The first few weeks feel easy, almost deceptively easy. People assume good intent, they fill in the gaps generously, and if someone’s message is short, nobody reads into it — they take it at face value and move on. If a deadline slips, nobody’s first thought is ‘this person is unreliable.’ There’s a kind of default charity running underneath everything. And then, somewhere around month two or three, it changes. Not with a big blow-up — usually there isn’t a single moment you can point to. Messages get a bit more formal. People start CC-ing others on things they never used to. Work that used to be taken on faith starts getting double-checked before it goes out the door.

If you’re a leader watching this happen, it’s genuinely confusing. Nothing went wrong, exactly. There was no incident, no conflict you can highlight. But there’s a shift in the atmosphere, in the way people work together. And most leaders read this as, ‘well, the honeymoon phase has ended’ — as if it’s an inevitable part of teams settling in, or proof the team never really gelled. You might even start wondering if you hired the wrong mix of people, or if this group just doesn’t have the chemistry.

Let me make it concrete, because it’s easy to nod along in the abstract and not recognise it in your own team. Take a product team: a couple of engineers in Munich, a designer in Osaka, a project manager in São Paulo. Week one, everyone’s in the group chat constantly — quick replies, plenty of exclamation points, a generous read of every message. By week eight, the Munich engineers have started sending longer, more formal status updates, because a couple of times a short update got followed by an anxious check-in from the project manager in Osaka asking if everything was okay. The Osaka designer, meanwhile, has started saying less in meetings, because two rounds of blunt, direct feedback from Munich landed harder than intended. Nobody has done anything wrong. Nobody’s a bad actor. But within six weeks the whole team is communicating more cautiously than it did on day one — and everyone assumes that’s just what happens as a team settles in. It isn’t. That’s swift trust, quietly converting into distance.

So I want to push back on the ‘this is just what happens’ framing, because none of it is inevitable. This is a well-documented, well-understood pattern with an actual name: swift trust. It’s not mysterious, it’s not bad luck, and it’s been out there for many years. Once you understand how the mechanism works, you can see it happening in real time in your own team — which means, critically, you can do something about it while it’s happening, instead of noticing the damage after the fact.

So why does this happen? Here’s the mechanism, and it’s worth understanding properly, because it changes what you do about it. Conventional wisdom says trust is built slowly — we all know that trust takes a long time to build and a single second to break. It’s built through repeated positive experiences over time, until you reach the point where you think, ‘I trust this person, they’ve got my back, they do what they say, the quality of their work is good.’ That slow-built trust is brilliant, and it’s the real thing. But it assumes you have time, and that you’re working with people you’ll get to know gradually. International, dispersed teams usually don’t have that luxury. They get assembled fast and are expected to perform immediately — sometimes within days of being put together.

So instead, something else kicks in. Team members extend what researchers call swift trust — a provisional, almost role-based trust, given automatically because you’ve been placed on the same team. You assume your new colleague is competent and well-intentioned, not because you’ve verified it, but because the organisation, in its wisdom, has put them there with you. It’s trust based on credit — extended in advance of any actual evidence. And to be clear, this isn’t a flaw. Swift trust is genuinely useful. It’s why newly formed international teams can move fast in the first few weeks, while a team without it might spend that same time cautiously circling each other, waiting to see who’s reliable before committing to anything. So swift trust is a real asset. The problem isn’t that it exists — the problem is what happens to it next.

And here’s the part that matters most. Like any credit — and we all know how credit works: you borrow something, and at some point it has to be paid back — swift trust has to be repaid. If it isn’t, it gets pulled back quietly, without anyone making a noise about it. In a co-located office, that repayment happens constantly and almost invisibly: a shared coffee, reading someone’s body language in a meeting, all the small social cues that quietly confirm ‘yes, this person is who I thought they were; yes, they get things done when they say they will, and the quality is really good.’ Face-to-face contact in particular has been shown, again and again, to matter enormously for sustaining trust, because it carries exactly the kind of information a Slack message, a WhatsApp or an email just can’t.

Dispersed, multicultural teams are often missing exactly that. You’re communicating over email, chat and video — channels that strip out the tone and nuance that reinforce the belief that this person is trustworthy. And culture adds a second layer on top. Someone from a lower-context communication background sends a short, efficient message; to them it’s just efficient, nothing more — it says exactly what it’s meant to, no more, no less. A colleague from a higher-context background reads that same message and thinks, ‘hang on, something’s wrong here — this person must be upset with me.’ Neither of them is misreading the words on the screen. They’re reading the missing context completely differently. And without the chance to check that reading face to face, these small misinterpretations just accumulate, one after another.

Add a language-fluency gap and it sharpens further. Most fluent speakers start, usually unconsciously, reading less fluent colleagues as less capable — there’s research on this, and accents influence how competent we assume people are, too. There’s no real evidence the person is less capable; but because they’re slower, or have to work harder to communicate, it feels like it signals something about competence, even when it doesn’t. Meanwhile, less fluent team members, sensing that gap, become more cautious — they say less than they actually think. Neither reaction has anything to do with real skill, but both quietly drain the trust that was so freely given at the start. So that early goodwill isn’t a milestone you’ve reached and can relax into. It’s a resource with a shelf life. And what decides whether it turns into real, durable trust or just drains away over the next few months is what you, as the leader, do in response.

So what do you actually do? I’ve got four things. Number one: front-load face-to-face contact. If there’s any way to get your team in the same room, even once, even briefly, early in its life, that has to be a priority. That investment does more for long-term trust than months of calls afterwards. It’s not about the agenda of the meeting; it’s about people getting a chance to pick up all the small cues that get stripped out on a screen. If travel is genuinely not possible, then at a minimum, on video, cameras should be on consistently for those first few weeks — audio-only and text-only both underperform, precisely because they carry so little of the information that reinforces trust. Going back to that Munich–Osaka–São Paulo team: even one kick-off week together in person, before the project ramped up, would have given them a far better read on each other than eight weeks of Slack ever could.

Number two: don’t let silence get filled by assumption. This is a big one. When someone goes quiet — replies more slowly, sends a message that reads unusually short — the instinct is to privately decide what it means: they’re annoyed, they’ve checked out, they don’t respect the deadline. Reset that judgement, because in a team with mixed communication styles, the most likely explanation is a difference in norms, not a change in commitment. Ask, rather than infer. A simple ‘hey, just checking in — everything okay on your end?’ does far more to protect trust than any amount of private speculation. That’s exactly the move that would have stopped the Osaka designer quietly disengaging: one direct, low-pressure check-in instead of two more rounds of unintentionally blunt feedback.

Number three: watch the fluency dynamic specifically. If your team has a real spread in language proficiency, pay close attention to who’s gone quiet in meetings. It’s almost never a lack of ideas — it’s much more often someone who’s become cautious about contributing in a second or third language, in real time, in front of more fluent colleagues. Creating space for written input as an alternative, or simply slowing the meeting down and checking in with that person directly, keeps the imbalance from hardening into a trust gap. And number four: name the pattern out loud to the team. Just tell your team what swift trust is, so they know that’s the concept they’re operating inside. Tell them the warmth they’re feeling right now is provisional by design, and that’s completely normal — not a sign that anything’s wrong. People are often already sensing the shift and simply don’t have the language for it. A team that understands this together is far more likely to actively invest in maintaining trust than one left to assume it’ll hold.

So those are the four. And if there’s one thing I’d like you to take from this episode, it’s this: the trust your team has right now was given to you on credit. Your job is to spend the next few months actively repaying it — not just hoping it holds. That’s the whole shift. Stop treating early trust as a milestone you’ve reached, and start treating it as a loan you’re responsible for paying back: through contact, through asking instead of assuming, and through noticing who’s going quiet, and why. And this isn’t just a hunch — it’s a pattern researchers have been documenting in global virtual teams since the late 1990s. I’ll drop a list of those studies in the show notes if you want to go deeper.

Quick recap. Swift trust gets extended fast on international teams, because there’s no time to build it the slow way. It has to be reinforced through real contact, or it decays — and dispersed teams are often missing exactly the cues that would normally do that reinforcing. Four things to actually do: front-load face-to-face time, don’t fill silence with assumptions, watch for the fluency dynamic specifically, and name the pattern to your team directly. And here’s what I’d try this week: think about your team’s first month versus right now. Where has trust actually been reinforced with real contact, and where has it just been assumed? That gap is usually where the problem is hiding.

I’m Brendan Quinn, and this is Cultural Friction. I really look forward to seeing you next time, and I hope you found this episode helpful. If this is a live issue for your team right now, that’s exactly the kind of thing I work through one-to-one with leaders — through advisory, coaching and workshops. You can find out more at brendanthomasquinn.com, and you can also find me on LinkedIn.