How to Run a Remote Team Offsite

We flew twenty-six people to Lisbon and spent the first morning watching slides. A product roadmap deck. A finance update. A recap of the last two quarters that half the room had already read in the weekly update. People had crossed nine timezones and lost a night of sleep to sit in a hotel conference room and look at a screen, which is the one thing every single one of them can do perfectly well from their own desk. By the coffee break I wanted the four hours back.

The offsite got good later, and I'll get to why. But that first morning is the mistake almost every distributed team makes when they finally get everyone in one place. They fill the scarcest, most expensive time they'll buy all year with exactly the work that didn't need the room.

The one thing you shouldn't make async

Nearly everything else on this blog argues the same direction: take the meeting, make it a doc; take the sync, make it async; stop spending your thin overlap hours on things a written update would do better. The offsite is the exception that proves the rule. It's the one time you should deliberately spend a fortune to force everyone into the same room at the same hour, because there are a handful of things that async genuinely cannot do, and those things quietly decide whether the other fifty weeks of async actually work.

Trust is the big one. A distributed team runs on it. Every time you disagree-and-commit on a decision you weren't in the room for, every time you give a teammate the benefit of the doubt on a terse Slack message at the end of their day, you're drawing down a balance. That balance gets built fastest in person, over a dinner that runs long, on a walk where the conversation drifts off the agenda. You can top it up a little through the screen. You can't open the account there.

The failure mode of a team that never meets isn't dramatic. It's thin. Everyone is polite and professional and slightly transactional, and the relationships hold fine right up until the first real conflict, at which point there's no reservoir to draw on and a design disagreement curdles into a grudge. I've watched a fully remote team that had never once been in a room together nearly fall apart over a reorg, not because the reorg was bad, but because nobody had enough stored goodwill to assume good intent. This is the deeper version of the problem behind fighting isolation on a remote team. The daily async connection keeps people from feeling alone. The offsite is what makes them a team that can survive an argument.

Cut anything that could have been a recording

Here's the test I use for an offsite agenda now, and it's ruthless: if a session could be a document or a recording, it doesn't belong on the schedule. It goes out before the trip, so people arrive already caught up.

The roadmap deck? Send it a week early and ask everyone to read it. The quarterly financials? A doc. The demo of the thing your team shipped? Record it and let people watch on the plane. All of that is information transfer, and information transfer is precisely what async is good at. Burning in-person hours on it is like flying to another continent to read a book someone could have mailed you.

What survives the cut is everything that needs bandwidth a screen can't carry. The strategic argument where reasonable people disagree and you need to read the room, see who's holding back, and let the tension actually surface. This is the setting where the hard decisions that stall out in async finally get made, because you can push on an objection in real time and watch the person's face when you land on the answer. Whiteboarding a problem nobody has framed cleanly yet. The messy, high-context conversations that would take forty Slack messages and still end in a misunderstanding. When someone proposes a session, ask what it needs a room for. If the answer is "nothing, really," you just saved everyone a session.

Protect the unstructured time on purpose

The instinct, once you've spent sixty thousand dollars flying everyone somewhere, is to fill every waking hour so the money isn't "wasted." Resist it. A back-to-back agenda from 9am to 9pm is how you send twenty-six exhausted people home having learned nothing about each other.

The best thing that happened in Lisbon happened in a gap. We had a free afternoon, and eight people ended up wandering the city in a loose group, and two engineers who'd been low-grade sniping at each other in code review for months spent three hours talking about everything except work. They came back friends. Nothing on the official agenda did as much for the team as that unplanned walk. That's not a coincidence you can schedule, but it's one you can make room for by refusing to book every hour.

So leave real gaps. Long meals with no agenda. An afternoon off. Evenings that aren't a mandatory group activity, because the forced-fun dinner where everyone performs enthusiasm is its own quiet failure, the in-person cousin of the virtual happy hour nobody wants to attend. The connection you're paying for happens in the space between the sessions, not in the sessions. Plan the scaffolding and then get out of the way.

Be fair about who pays the travel tax

An offsite has a cost that never shows up in the budget line, and it always lands on the same people. If your team is centered in North America with a few folks in Sydney and Bangalore, and you hold every offsite in Austin, the same two or three people eat a twenty-hour flight and a wrecked week of sleep every single time, while everyone else drives in from the suburbs. That's the travel version of always parking the awkward meeting slot on the same far-timezone person, and it breeds the same slow resentment.

Rotate the location. Do one in Europe, one in Asia-Pacific, one somewhere central, so the burden moves around instead of parking permanently on your most distant colleagues. Build in a recovery day on either end, on the company's clock, so nobody is expected to be sharp after a red-eye and a customs line. And write down every arrival and departure time in each traveler's own timezone when you send the logistics, because the person flying furthest is exactly the one a misread "check-in at 4pm" hurts most.

Send the outcomes home in writing

Someone will miss the offsite. A new baby, a visa that didn't clear, a health thing. When the trip is over, the decisions and the plans and the shared context need to survive for the people who weren't there, and honestly for the people who were and won't remember the specifics in a month.

So write it down like you would any decision made off-screen. The strategy you aligned on, the arguments that got you there, the concrete commitments and who owns them. Not a photo dump and a vibe, but a real document a person who stayed home could read and actually understand what changed. The offsite is where the decisions get made in the room. The write-up is what keeps them from evaporating the moment everyone lands back in their own timezone.

Keep Every Offsite Time Straight Before Anyone Boards

Booking flights, a group dinner, and a recovery day across a team scattered over nine timezones is where a misread hour turns into a missed connection. Timely converts every time mention in Slack to each person's own clock automatically, so when the logistics thread says "wheels up at 11am" or "dinner at 8," the person flying in from Sydney reads the right number without doing the math.

Add Timely to Slack — Free · See how it works