What It Is
A retreat is a scheduled in-person gathering for a remote team. Unlike an office — where people are co-located daily — retreats are time-limited, intentionally designed events with a specific purpose: build the relationships and trust that sustain distributed culture for the months between gatherings.
The best remote-company retreats share several characteristics:
- Scheduled in advance, with enough lead time for international travel
- Loosely structured — intentionally so; the agenda serves relationship-building, not deliverables
- Periodic — most companies do 2–4x per year at various scales (company-wide + team)
- Designed for connection, not productivity — the work gets done async; the in-person time is for the human infrastructure that makes async work possible
Why It Works
Async communication is sustainable only when there is enough relationship capital. A message from a colleague you have never met is interpreted differently than a message from someone you have spent time with. The ambiguities of text communication — tone, intent, frustration — are resolved much more generously when you have context for the person. Retreats build that context. [Inference — central argument; consistent with what Doist (20/30/50) and Automattic (3–4 weeks travel/year) actually invest in but not measured cross-company.]
Distributed teams accumulate trust debt. Every misunderstanding, missed deadline, and communication breakdown erodes trust slightly. Without repair mechanisms, that debt accumulates. In-person time is the fastest trust repair mechanism available. Retreats are the scheduled opportunity to reset the trust level. [Inference — practitioner framing; the “trust debt” metaphor is not a measured construct.]
Organic relationship-building does not happen async. Colocated teams build informal relationships through proximity: lunch conversations, hallway chats, impromptu whiteboard sessions. These create the “social overhead” that makes work collaboration easier. Distributed teams have no equivalent unless they design one. Retreats are the designed equivalent.
Doist spends ~$350,000 per year on retreats for a team of roughly 90–100. That is well over $3,000 per person per year. For a bootstrapped company that runs no-meetings-by-default, this is their largest discretionary cultural investment. The investment signals that they understand what the retreats are actually buying: the relationship capital that makes the async operating system sustainable. (Source)
Where It Fails
Retreats designed as compressed work sessions produce exhaustion, not connection. The most common failure mode: a 3-day offsite with 8-hour days of workshops, presentations, and strategic planning sessions. Participants come home more tired and no better connected. [Inference — practitioner observation; consistent with Doist’s published rationale for the 20/30/50 split.]
Retreats that happen once per year are insufficient for large distributed teams. Annual company retreats work for teams of 10–30. For teams of 100+, annual is not enough. You cannot build and maintain meaningful relationships at the company-wide level with a single annual gathering.
Retreats without small-group time miss the point. A company-wide keynote session does not build relationships. Small dinners, pair activities, and unstructured free time do. Retreats that are structured entirely as group presentations give people group information; they do not give people each other.
Retreats without clear design are wasted budget. Flying 50 people to a hotel and leaving the agenda loose without intentional structure produces expensive but unproductive time. Loosely structured is not the same as undesigned. The best retreats have a clear purpose, a light structure, and built-in space for organic connection.
Best Examples
37signals / Basecamp — Twice-Yearly, 1 Week, Different City Each Time. Two company-wide gatherings per year, one week each. Different city every time. The structure is intentionally loose: some scheduled talks (All Hands on Monday, lightning talks), team huddle sessions, manager 1:1s, and abundant unstructured exploration time. The emphasis is on connection and strategy — not status updates or deliverable reviews. (Source)
Automattic — Division and Team Meetups, 3–4 Weeks of Travel Per Year. Post-pandemic: company-wide Grand Meetup paused; replaced with division and team meetups. Individual teams meet for 5–7 days in locations worldwide. Total employee travel: 3–4 weeks per year. The next Grand Meetup planned for 2026. The travel budget signals seriousness about in-person investment. (Source)
Doist — Company Retreat + Team Retreat, 20/30/50 Rule. Two gatherings per year: one company-wide, one team-level. The 20/30/50 framework governs every retreat:
- 50% rest and relaxation / free time
- 30% planned social and entertainment activities
- 20% dedicated work sessions The explicit rationale: “in-person time at Doist is primarily for relationship-building, not for replicating office productivity.” (Source)
GitLab — GitLab Contribute (Annual) + Coffee Chat Infrastructure. Annual company gathering called “Contribute.” Plus structured coffee chat program for year-round informal connection. The two-level approach — big annual event for company-level connection, coffee chats for individual relationships — addresses the limitation that one event per year cannot build the full relationship infrastructure a distributed company needs. (Source)
Implementation Guide
1. Schedule retreats before the year starts. The single most common failure: the retreat gets scheduled “eventually” and then gets displaced by Q3 planning. Put dates on the calendar in Q1 for the full year, and protect them.
2. Use the 20/30/50 framework. 50% rest and free time. 30% social and activities. 20% work. This sounds extreme until you understand the purpose: the relationship capital built during the 50% rest is what makes the 20% work possible. The work sessions are more productive when preceded by genuine connection.
3. Design for small-group time. Plan for meals in groups of 4–8, not banquet tables of 50. Schedule pair activities. Leave evenings genuinely unstructured so organic conversations happen. The most important conversations at retreats are the ones that happen when nobody planned them.
4. Mix company-wide and team-level gatherings. A company-wide retreat once or twice a year serves company culture. Team retreats serve team coordination and bonding. Both are necessary at scale; they serve different functions.
5. Budget explicitly per person per year. Doist’s roughly $3,500/person is a reasonable reference point for a fully distributed no-meetings company. For companies with more regular sync, budget needs are lower. But make it a budget line, not an afterthought.
6. Brief before, debrief after. The most common waste: people arrive at a retreat without a shared context about what the retreat is for. Send a one-page pre-read. Run a brief kickoff session to set intentions. Do a short retrospective before leaving. These bookends significantly improve retention and follow-through.
Common Mistakes
Treating retreats as performance review season in a nice location. Retreats should not be the occasion for difficult performance conversations, reorganization announcements, or strategic pivots that blindside people. These require prior context and calm conditions — not a hotel conference room where people are already in an unfamiliar social situation.
Skipping retreats when the company is under financial pressure. The retreat budget is the first thing cut when times are hard. This is exactly backwards — when stress is high and trust is low, in-person time is the most efficient trust repair mechanism. Cutting retreats to save money during difficult periods accelerates the culture erosion that the retreats are there to prevent.
Making retreats optional. When retreats are optional, the people who most need the social connection — introverts, new hires, remote employees in less common time zones — are the least likely to attend. Make attendance expected, travel fully covered, and the experience worth showing up for.
Too many work sessions. Work sessions at retreats feel productive in the moment. The actual cost: they crowd out the unstructured time that produces the relationships the company needed the retreat for. Limit work sessions to 20% or less.
Sources
- Our Rituals — 37signals Employee Handbook: https://basecamp.com/handbook/our-rituals
- How We Work — Automattic: https://automattic.com/how-we-work/
- The 20/30/50 Rule for Remote Team Retreats (Doist): https://async.twist.com/20-30-50-rule-remote-team-retreats/
- GitLab’s Guide to All-Remote: https://handbook.gitlab.com/handbook/company/culture/all-remote/guide
Inferences
- The retreat is load-bearing for the async remote model in a way that most companies do not articulate. Async communication works because there is enough relationship trust to bridge the gaps — to give colleagues the benefit of the doubt, to interpret ambiguous messages charitably, to raise problems without fear of overreaction. That trust is built in person. Companies that cut retreats are eating their trust capital. They do not notice the drawdown until something goes wrong.
- The 20/30/50 framework’s most important implication is that “efficiency” at retreats is the wrong goal. Companies that optimize retreats for maximum work output get less of what they actually need. The leisure and social time — the 50% and 30% — is doing the real work of the retreat.
Work with Alex
If your team’s retreats feel like expensive workshops that leave people exhausted instead of connected, or if your distributed team has never done an in-person gathering at all, Alex helps leadership teams design the in-person investment that sustains remote culture.