The Week That Makes the Other Fifty-One Work

The irony of being a remote work advocate: the thing that makes async work best might be the occasional, intentional synchronous.

Me, Aatu, and Tommi just spent a week with our dev team in Mangaluru. Three Finns flying to India to sit in the same room as people we talk to every day through screens and messages. It sounds like a contradiction to everything I've written about async communication.

It isn't. It's the other half of the story.

The Async Case Still Stands

I've written before about why we moved toward async-first communication. About how it creates space for different thinking styles. How it rewards clarity over speed. How it lets people contribute on their own terms instead of competing for air time.

I still believe all of that. Async is our operating model, and it works.

But operating models don't build relationships. People do. And people need more than text on a screen to fully trust each other.

What Async Can't Do

When you work async-first with people you've never shared a room with, you're collaborating through a keyhole. You see enough to get the work done. You know they're competent. You know they deliver. But you're working on what researchers call "swift trust." Trust based on categories and credentials, not lived experience.

Swift trust is fragile. It gets you through the task, but it doesn't survive the first real misunderstanding. A misread message. A missed deadline. A decision that feels wrong from the other side. Without deeper knowledge of who someone is, small friction becomes big friction fast.

The transition from swift trust to knowledge-based trust, the kind built on actually knowing how someone thinks, what motivates them, what's going on in their life, takes longer in virtual teams. The casual signals that build that trust don't travel well through Slack.

You can't replicate the moment when you're eating lunch together and someone mentions a frustration they'd never type into a message. You can't replace the trust that builds when you see someone's face light up explaining something they care about.

The Connection Decay Problem

Atlassian has the most rigorous data I've found on this. Their Team Anywhere Lab studied over 1,600 team gatherings and found something specific: in-person time boosted team connection scores by an average of 27%.

But here's the part that matters more: that connection decayed back to baseline after approximately four months.

This reframes the question. It's not "should distributed teams meet in person?" Most people already agree on that. It's "how often do we need to refill the trust reservoir?"

The Atlassian data suggests roughly three times a year. And critically, they found that regular office attendance didn't predict team connection. It was the intentional, purposeful gathering that mattered. Not proximity. Not frequency. Intentionality.

Presence, Not Agenda

We played cricket. Three Finns trying to learn the game from teammates who grew up with it. There were comparisons to pesäpallo, the Finnish version, which led to the kind of conversation you can't schedule: explaining your culture through sport, laughing at each other's technique, finding the overlap between two things that seem completely different.

We took a ferry across the river to Mangaluru beach. Walked barefoot in the shoreline waters at sunset. No agenda. No retro. No whiteboard.

These are the moments that async can't produce. Not because the format is wrong, but because trust isn't built through work output alone. It's built through shared experience.

Martin Fowler puts it well: "The most valued component of an in-person meeting isn't scheduled work. It's casual interactions over coffee and meals." He recommends distributed teams meet for one week every two to three months.

Basecamp has operated on this principle for over twenty years. Their twice-yearly meetups are primarily social events with some work mixed in. Not the other way around. Jason Fried calls them social events, and after two decades of successful remote-first operation, it's hard to argue with the approach.

The Economics

There's a common objection: flying people across the world is expensive.

It is. But the math works differently than most people expect.

Matt Mullenweg, CEO of Automattic, the company behind WordPress.com with over 2,000 employees across 97 countries, spends roughly $3.3 million annually on their Grand Meetup. That's comparable to what maintaining a physical office would cost.

His framing is worth sitting with: the Grand Meetup is "the one week a year that makes the other fifty-one work."

You're not adding a cost on top of remote work. You're redirecting what you'd spend on permanent office space into concentrated investment in the moments that actually build trust. No daily commute. No half-empty office on Fridays. Instead, a few weeks a year where everyone is fully present and fully intentional about being together.

Automattic's internal data showed that relationships formed during meetups were demonstrably closer than pre-meeting baselines. Mullenweg says it plainly: "It's so much easier to hear the nuance in someone's chat messages if you've hung out with them."

That's exactly what we experienced.

Back to Async, But Different

Here's what changes when you come back. The messages land differently. You hear the person's voice in your head when you read their words. You give the benefit of the doubt more easily. You have context for the human behind the screen name.

The async channel carries more signal because you know who's sending. A terse message from someone you've shared a meal with reads as efficient. The same message from a stranger reads as cold.

This connects back to something I noticed in our async experiments: async rewards clarity over speed, but clarity is easier when you know the person behind the words. The week in Mangaluru didn't replace our async workflow. It made it work better.

There is trust. And trust travels well through text.

What I'm Still Figuring Out

This is an ongoing experiment, not a solved framework.

I'm still working out the right cadence for our team. The Atlassian data says roughly every four months. Basecamp does twice a year.

I'm thinking about what happens as the team grows. Unstructured time works beautifully with a small group. Does it scale? Or does it need more structure to stay intentional?

And I'm thinking about the team members who couldn't be there. How do you bring back the trust and connection for people who missed the week? Is there a way to extend the experience, or do you just plan the next one sooner?

The Pattern

The evidence and the experience point in the same direction: async-first is the operating model, periodic in-person time is the trust infrastructure.

The in-person time isn't for doing the daily work. It's for building the relational foundation that makes the daily work possible. It's for turning keyhole collaboration into full-picture understanding.

You don't need to be in the same room every day. But you need dedicated time, not for workshops with packed agendas, but for presence. For cricket matches and ferry rides and meals on banana leaves. For the kind of shared experience that no amount of well-written Slack messages can replace.

The irony of being an async advocate: the thing I'll keep advocating for most might be the occasional, intentional week of being together.

---

What's working for your distributed team? How do you build trust across distance? I'd be curious to hear what you're finding.