Distributed Teams Don't Have a Team Building Problem — They Have a Format Problem

The conversation about distributed team events usually starts in the wrong place. People Ops leaders frame it as a scheduling challenge: how do we find the least-bad live window? What's implicit in that search is the assumption that synchronous team building is the real thing and async is what you do when scheduling fails. OECD's 2024 analysis of global workforce patterns found that distributed teams across three or more time zones share just 2.5 hours of overlap in standard business hours. Most teams use that overlap for operational work. Asking them to also fit a 75-minute team event into it means either crowding out the work or crowding out the event, and when it's the latter, participation drops, and the People Ops lead is left explaining to Finance why a well-designed event landed below 60%.

Across 50+ countries and five years of distributed-team programs, we've designed and run more than 1,500 virtual team events for 300+ companies. The companies that have moved to async team building (specifically the Marathon format, with daily content drops and a shared leaderboard across 1-5 days) report not just equivalent participation to their synchronous events, but often higher. The people who've opted out of mandatory live events often complete all three episodes of a Marathon voluntarily. That's not a scheduling optimization. It's a format that changes who can realistically participate, not just when.

How do you run team-building events for a distributed team without the same region drawing the short straw on time zones every quarter?

Why the Same Window Never Quite Works

The time-zone overlap problem for distributed teams isn't just about inconvenience — it's about systematic underrepresentation. When 9am EST is your event window, it's 2pm in Warsaw (comfortable), 3pm in Nairobi (fine), and 10pm in Singapore (consistently punitive). Move the window earlier and you've transferred the inconvenience to your US West Coast team. Rotate quarterly and you've turned team building into a quarterly signal about whose region the company cares about most this cycle.

We worked with a software company last year (roughly 500 employees, with substantial teams in Central Europe, Southeast Asia, and the US East Coast) whose company anniversary event had historically been a synchronous Big Game. Their European team participated at 78%. Their Southeast Asian team participated at 41%. When we mapped the participation data against time zones, the pattern was clear: the Southeast Asian team was consistently underrepresented in every live culture event the company ran, not because of disengagement, but because the format required them to join at 9pm local time. They weren't disengaged. They were at a structural disadvantage.

For their next anniversary, we ran a 3-day Marathon. Each daily episode unlocked at 9am in each team's local time — not the same clock, but the same moment in each team's working day. Southeast Asian participation reached 76%. European participation stayed flat at 77%. US East Coast came in at 79%. The format was the wall, and switching formats removed it.

This pattern isn't an edge case. When we ran Coca-Cola HBC's LearnFest 2021 closing event for 6,000 employees across 28 countries, the design constraint that shaped the entire format wasn't the audience size. It was the requirement that participants could engage as their local calendars allowed. A format demanding simultaneous presence across 28 countries at 6,000 people is a format that guarantees some meaningful part of your workforce has an experience different from everyone else's. Async design and synchronous design aren't the same product aimed at different schedules; they're different formats built for different operational realities.

For distributed teams where the goal is consistent, equitable participation across all regions, games with strong narrative momentum perform especially well in async format. Bureau of Magical Affairs, which we've run for international onboarding cohorts spread across a month, works because the four-case-file structure gives players a concrete reason to return for each episode. Last Temple Mystery, whose four-floor expedition arc maps naturally onto Marathon's daily cadence, keeps teams invested across days because each episode reveals what the next floor requires.

The Format Decision That Usually Makes Itself

In practice, the choice between Big Game and Marathon for distributed teams resolves quickly once you map the team's actual time zone spread and answer one honest question about your culture: will people show up to a mandatory live event without resentment?

Big Game is a single synchronous event, 60-90 minutes, everyone on the same call, hosted by a HeySparko Game Host. The energy of Big Game is its product. Shared leaderboard shifts visible to everyone at the same moment, the host setting the pace through a live room, teams reacting to the same plot twist simultaneously. For groups where all participants are within a 6-hour time zone spread, Big Game is the right format. The shared moment is what you're buying. That product requires everyone present for it.

The moment your spread exceeds 8 hours, the math changes. We've watched teams try to cover US-plus-APAC distribution by running two separate Big Game sessions. That solves the coverage problem but creates a different one: the two cohorts have genuinely different events. The host's live improvisations in Session 1 don't replicate exactly in Session 2. The leaderboard energy from the first session doesn't carry to the second. You end up with two events wearing the name of one.

Marathon is built for exactly the situation where a shared window isn't viable. Players engage on their own schedule (typically 30-45 minutes per day) while a shared leaderboard updates continuously. The competitive pull of a visible leaderboard does the motivational work that a mandatory calendar block would otherwise need to do. For Apocalypse, run as a 4-stage async adventure with daily stage releases, a Singapore engineer and a Warsaw product manager can both be advancing their team's score in the same episode, with neither needing to coordinate a shared time window. The race is on the leaderboard, and that race is live for everyone regardless of when they play.

There's also a cultural argument for Marathon that goes beyond scheduling. We see it in completion rates: in our data across 500+ events, 65-78% of participants who start Episode 1 of a Marathon complete all three episodes. For opt-in events (no mandatory participation required) this rate holds. People don't finish because they have to. They finish because the story has momentum and their team's position on the leaderboard is recoverable. Mandatory synchronous events often achieve lower real engagement than opt-in async ones, because obligation and genuine participation aren't the same thing.

That said, occasion-driven events (a company anniversary, a holiday party, a milestone celebration) often warrant Big Game even for distributed teams, provided the time zone spread allows it. Wintervald Hotel Mystery in Big Game format produces a live-deduction experience where the Game Host roleplays suspects while teams ask questions in breakout rooms; the real-time interview dynamic is more immersive when everyone's present simultaneously. For a specific occasion with a manageable time zone window, that live energy is worth the coordination cost. For quarterly engagement programs designed to cover a globally distributed workforce? Marathon, consistently.

Matching the Game to Your Distributed Team's Culture

Not all distributed teams are the same culture, and the game choice matters more than most event organizers expect. The most consistent completion-rate predictor in our data across distributed events isn't the format alone — it's whether the game's premise and puzzle logic actually resonate with how that team solves problems. The wrong game in the right format still produces a mid-event cliff where Day-1 participation doesn't carry through to Day-3 completion.

Engineering and tech teams in high-urgency environments respond well to Apocalypse. The four-stage vaccine-race structure (Research Center, Street, Power Station, Laboratory) rewards coordination under pressure, which is something engineering teams recognize from their real work. We've watched 30-person distributed engineering squads self-organize into specialists by Stage 2, with the APAC half running a parallel analysis track while the European half works infrastructure, synthesizing in the final stage. The game surfaces the team's natural coordination patterns in a way that deduction-based formats don't, and it does it without requiring anyone to be funny on camera.

For distributed teams at more formal enterprise cultures (legal, finance, consulting practices, regulated industries), Wintervald Hotel Mystery tends to land better. The deduction mechanic rewards careful thinking over speed; the Agatha Christie aesthetic doesn't require any specific cultural context to work (we've run it across 12+ countries with consistent comfort feedback). In Marathon format, the daily-stage reveals work especially well for deliberate team cultures, where players get to discuss suspects and theories in Slack across days rather than in a single compressed session, which often produces richer cross-team conversation than the live format does.

Teams with a whimsical, workplace-comedy lean (the kind of org that has an active meme channel and a CEO who shows up to all-hands in costume) often get the strongest return from Bureau of Magical Affairs for year-round events, from Under the Big Top for summer or mid-year culture moments, or from Adventure Through the Ages when the team prefers exploratory narrative variety to urgent coordination — its hop across historical eras gives each Marathon day a distinct setting to discuss in Slack between episodes. The vintage circus mystery runs in async beautifully for Slack-native distributed teams; the investigation debate over "who took the headliner" tends to spill into team channels between episodes, and that spillover is exactly the cross-team social contact that distributed teams are trying to generate.

For year-end events at distributed teams, Stolen Hours occupies a specific niche: the genre-bending premise (Santa's clock hands scattered across postapocalypse, cyberpunk, steampunk, and biopunk worlds) is December-specific enough to feel intentional without being narrowly Christmas. In a 5-day Marathon over a holiday week, the four genre shifts surface different player strengths and keep the leaderboard competitive across all five days. Different players lead in different worlds. The team in APAC that was middling in Stage 1 pulls ahead in Stage 4. The event people reference in January tends to be the one with a close leaderboard on Day 4 and a dramatic final-stage reversal.

One operational note that shows up repeatedly in post-event debriefs for distributed teams: the customization add-ons (NPC, Logo, and Story tiers) amplify the connection value of a Marathon more than they do in a Big Game, because each player encounters the branded elements repeatedly across days. The Singapore team member who joins at 3pm local on Day 2 has the same branded experience as the Warsaw team member who joined at 9am. Brand recall multiplies across the event duration. For distributed teams running annual engagement programs, it's worth considering whether that multiplier justifies the add-on investment.

What the Engagement Data Actually Shows

The research on async engagement for distributed teams has moved beyond anecdotal. Three findings come up across independent sources, and they all point in the same direction.

Microsoft's 2024 Work Trend Index, which surveyed 31,000+ workers across 31 countries, found that 57% of distributed workers prefer asynchronous engagement options over live ones. That's not a minority preference — it's a majority. When you default to synchronous events for a distributed team, you're running a format that more than half your team would not have chosen if given the option.

Deloitte's 2023 Human Capital Trends report found that 46% of employees felt less connected to their colleagues compared to before the pandemic — a persistent gap that scheduled Zoom socials have not meaningfully closed. The structural reason is that casual social contact for distributed teams doesn't accumulate the way it does for co-located teams. Structured game events with coordination mechanics, shared stakes, and cross-team composition generate the equivalent of "weak-tie" connection that office hallways used to produce: the colleague in a different function you've never worked with directly, but now recognize from a shared leaderboard experience. Anog et al.'s 2023 systematic review of 60+ studies, published via SSRN, found that structured team-building activities increase both satisfaction and retention impact — with effects amplified when activities integrate into a broader development strategy rather than run as isolated one-offs. That's the academic argument for Marathon-as-program rather than Marathon-as-event.

Microsoft's 2025 Work Trend Index (Breaking Down the Infinite Workday), based on a 31,000-knowledge-worker survey combined with Microsoft 365 telemetry, found that 30% of meetings now span multiple time zones — an 8-point absolute increase since 2021. That shift makes the team-level engagement gap structurally more visible than it used to be: a third of every team's working calendar now crosses regional boundaries, which means a synchronous-only engagement program is quietly compounding the same coverage gaps every quarter. The analytics that Marathon produces — participation rate by day, completion rate by team, NPS pulse by cohort — give HR leaders the team-level breakdown that exposes which managers are running genuinely engaged teams and which aren't. A company-average participation rate of 74% can conceal a team in one region that participated at 40% because their manager sent a "this is optional" message on Day 1.

In our own data, the completion-rate pattern holds up across event types and team sizes. 65-78% of Marathon participants who engage with Episode 1 complete all three episodes. For async events run on an opt-in basis (no mandatory participation) that figure stays in the same range. The leaderboard creates pull; the narrative creates curiosity; the combination produces completion rates that mandatory live events rarely match, because the mechanics are aligned with how distributed teams actually want to engage.

Frequently asked questions