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 — company and team gatherings follow different schedules. Todoist currently describes two organization gatherings per year; this does not guarantee individual attendance or establish a universal cadence. (Source)
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.]
Make room to repair misunderstandings. [Inference — application guidance.] Retreats may help colleagues discuss problems and rebuild shared context. The company examples do not establish that in-person time is the fastest trust-repair mechanism or that a gathering reliably resets trust.
Remote relationships need room to develop. [Inference — application guidance.] Written conversation, social calls and in-person time can each support relationships. The cases do not establish that informal connection is impossible online.
Doist historically published a 20/30/50 agenda: 20% work, 30% planned social activity and 50% rest/free time. Treat it as a company example rather than a current mandatory agenda. Todoist’s current About page confirms twice-yearly organization gatherings. (Historical agenda, current company page)
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.]
[Inference — As a distributed team grows, one annual company-wide retreat provides less relationship depth per pair. Larger companies may need team- or division-level gatherings between company-wide events; the evidence reviewed here does not establish a universal headcount threshold.]
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, 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. Current guidance emphasizes division and team meetups, typically five to seven days, with three to four weeks of expected annual travel. It does not confirm a 2026 Grand Meetup or an exact number of trips per employee. (Source)
Todoist (formerly Doist) — Two Organization Gatherings Per Year. Todoist’s current About page describes two organization gatherings annually. This is a company cadence, not a guarantee of individual attendance; historical team-retreat and agenda descriptions should retain their dates. (Source)
GitLab — Summit and Coffee Chats. GitLab documents company gatherings under the Summit name and a separate coffee-chat program. Its event history records a March 2024 Las Vegas Summit; the public pages do not establish a current annual cadence. (Event history, coffee chats)
Research Context
A June 2026 working paper reports a randomized trial of 248 customer-service employees in Türkiye. One coordinated office day per month increased calls handled per hour by 7.8% at the end of the intervention and reduced attrition by roughly one-third. Participants were volunteers living within about 45 minutes of the office. This supports testing occasional local gatherings; it does not establish the return on international retreats, compulsory travel or a particular agenda. The paper has not been presented here as peer-reviewed evidence. (Study)
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. Set an agenda for the purpose. [Inference — application guidance.] Doist’s historical 20/30/50 example can inform the discussion, but choose the balance of work, social activity and rest around the people attending. No optimal percentage is established here.
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. Choose the scale of gathering. [Inference — application guidance.] Company-wide and team-level meetings can serve different purposes. Evaluate which relationships or coordination needs require in-person time; both formats are not proven necessary for every company.
5. Budget explicitly for in-person time. Make retreats a named budget line, not an afterthought. Set the amount from the gathering’s purpose, travel footprint, and frequency rather than copying a stale per-person benchmark.
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.
Cutting relationship investment without considering alternatives. [Inference — application guidance.] Compare the purpose, cost and accessibility of international retreats, local gatherings and online contact. The evidence does not establish that protecting travel spend is always the right financial choice.
Ignoring barriers to attendance. [Inference — application guidance.] Account for travel, care, health and accessibility needs, and provide meaningful ways to participate. The evidence here does not establish that introverts or new hires are less likely to attend, or justify universal compulsory travel.
An agenda that crowds out its purpose. [Inference — application guidance.] If connection is the goal, reserve time for conversation and rest. A fixed 20% work ceiling is a company example, not an empirically established rule.
Related Frameworks
- Sync vs Async Decision Matrix — choose a communication mode for the work
- The 20–30 Person Fracture Point — a working hypothesis about coordination needs during growth
Sources
- Our Rituals — 37signals Employee Handbook: https://basecamp.com/handbook/our-rituals
- How We Work — Automattic: https://automattic.com/how-we-work/
- Doist How We Work: https://doist.com/how-we-work
- Doist Careers — company-wide and team retreats: https://doist.com/careers
- GitLab’s Guide to All-Remote: https://handbook.gitlab.com/handbook/company/culture/all-remote/guide
Todoist current company/retreat policy: https://www.todoist.com/about-us
GitLab Summit history: https://handbook.gitlab.com/handbook/company/culture/summit/previous/
Aksoy et al. — One Office Day a Month (June 2026 working paper): https://hoover-s3-website.s3.us-west-2.amazonaws.com/s3fs-public/research/docs/26114-Aksoy%20et%20al.pdf
Inferences
- In-person time may strengthen trust and shared context, but relationships can also develop through written conversation and social calls. Evaluate the combination that works for the team.
- The purpose and accessibility of a gathering should drive its agenda and cost. Company examples and a local office-day trial do not establish a universal retreat format.
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.