The manager-engagement gap has been the least-discussed variable in remote work for five years. Engagement scores dip, the response is a company-wide initiative — a new Slack channel, an all-hands event, a quarterly team-building program — and six months later the scores haven't moved much. The events were fine. Participation was fine. But the gap between best-performing and worst-performing manager teams stayed exactly where it was. Remote work doesn't create this problem; it exposes it with unusual clarity.
1,500+ virtual events later — across 300+ companies in 50+ countries since 2020 — the patterns are more consistent than most People Ops leaders expect.
Teams with strong managers have high event attendance, high completion rates in our Marathon format, and high NPS regardless of which game we're running. Teams with checked-out managers have the opposite — even when the event is objectively excellent. The event is not the primary variable. The manager is.
How do you keep remote employees engaged when the biggest variable isn't your event calendar — it's the manager layer sitting between your People Ops initiatives and the employees you're trying to reach?
Stage 1: Diagnose the manager-engagement gap before you plan anything
The instinct is to start with the event. The better instinct is to start with your engagement survey data, segmented by manager.
If your platform (Lattice, Culture Amp, Glint, 15Five) can show you team-by-team engagement scores, pull that view now. The variance within a single company is almost always wider than the company-level average suggests. We've worked with organizations where the average engagement score sits at a respectable 62%, but the by-manager breakdown shows two teams at 85% and four teams below 40%. The company average isn't just masking the problem — it's making the problem invisible.
This matters for event planning because low-engagement teams and high-engagement teams need different things from a shared event. High-engagement teams use events for reinforcement, celebration, and the social memory-making that cements an existing sense of belonging. Low-engagement teams need events to create connection that doesn't yet exist at the team level, which changes the game you choose, the format you use, the facilitation approach, and the post-event follow-up cadence.
The manager pods with below-50% voluntary event attendance are worth a conversation before the next event cycle, not after. The most effective HR Leaders we work with identify those three or four specific managers early and ask a simple question: what does your team need from this that they're not currently getting? The answers are almost never about the event itself.
Responsibility: People Analytics lead or the HRBP for the relevant business unit.
Timing: 4–6 weeks before the next event cycle.
Stage 2: Match the format to your team's actual distribution
The format decision is where most remote engagement programs make their first significant mistake. There are two HeySparko formats, and they're designed for genuinely different situations.
Big Game is a single live 60–90 minute synchronous event, run entirely by a professional HeySparko Game Host, with breakout teams competing on a shared leaderboard. The energy is high — real-time scoring, a narrative unfolding on-screen, the whole company watching the same leaderboard shift at once. It works brilliantly for teams within a 6-hour time zone spread. A 250-person team across three US cities is a clear Big Game candidate.
A 400-person team split across Singapore, Warsaw, and São Paulo has a harder conversation to have. Someone is taking a very early or very late call, and forced participation at an inconvenient hour is the fastest way to generate negative engagement from a positive event. This is not a hypothetical; we've run Big Games for teams spread across 14 hours of working-day difference, and the 5am participants skew the post-event NPS in a predictable direction.
Marathon runs over 1–5 days, with daily content episodes unlocking on a schedule and players engaging on their own time. A shared leaderboard updates throughout, so teams track standings across time zones without needing to be online at the same moment. In our data, the Marathon format reaches approximately 35% more participants than a forced-synchronous equivalent, because it includes the people who genuinely cannot make a single live window. For a US-Europe-APAC team, "everyone plays sometime in the next three days" is a dramatically more inclusive constraint than "everyone plays this Tuesday at 3pm ET." The leaderboard creates pull; no one needs to be pushed.
A concrete diagnostic: count the time zones your participants span, then estimate how many hours of standard business overlap actually exist. OECD's 2024 analysis of global workforce patterns found that teams spread across 3+ time zones share only about 2.5 hours of standard business-hour overlap on any given day. Below 3 hours of shared working time, Marathon is almost always the right call. Above 5–6 hours, Big Game gives you the shared-moment energy that async doesn't replicate.
Responsibility: HR Leader or People Ops Manager, in consultation with the scheduling function for calendar-blocking logistics.
Timing: Format confirmed 3–4 weeks before the event, to allow lead time for any customization.
Stage 3: Choose the game that fits the culture
Game selection is where event planners most often underinvest their attention — and where the difference between a flat event and one that shows up in next month's engagement pulse free-response actually gets made. Start with three diagnostic questions.
Does the team want urgency or deduction? Teams that thrive under time pressure do well with Apocalypse, HeySparko's highest-energy adventure: a four-stage race to develop a vaccine before the last research lab falls. The mechanics surface natural coordinators and delegators by Stage 2 in a way that a quiz night never will. For a calmer audience — legal functions, finance teams, anyone who'd find an outbreak scenario unnecessarily stressful — Wintervald Hotel Mystery delivers the competitive team play in a classical detective format, closer in tone to Knives Out than to an emergency room.
Does whimsy land in this culture, or does the team prefer something more grounded? Bureau of Magical Affairs works brilliantly for teams with warm, self-aware cultures — new hire cohorts especially, since the chaos-plus-bureaucracy premise maps directly onto how it feels to join any company at scale. Mission 8-Bit leans into tech-culture nostalgia: a three-stage product-launch arc (escape the hostile office, rebuild the retro machine, defeat the final boss) with 8-bit sprite avatars of team members delivered post-event for Slack and stickers. For a more deduction-forward crowd that wants something distinctly non-corporate, Under the Big Top — a vintage circus mystery with a wonderfully strange cast of suspects — is one of the most-requested non-seasonal options in our catalog.
Is this a one-time event or part of a recurring program? For first-timers, simpler mechanics give the team space to find their footing. For a fourth event in an ongoing quarterly program, Stolen Hours — a genre-bending adventure across postapocalypse, cyberpunk, steampunk, and biopunk worlds — rewards teams that have built enough coordination to handle rapid context-switching between puzzle styles. The genre shifts surface different player strengths, which means the team that's been together for two years of these events gets a genuinely different result than they did in year one.
One operational note: the question of whether the audience is diverse across nationalities matters more than most people expect. Deduction-based mysteries (Wintervald Hotel Mystery, Under the Big Top) travel well across nationalities — the Agatha Christie detective-fiction genre is genuinely global, tested across 12+ countries with strong cross-cultural comfort feedback. Humor-forward formats need more care. What's an obvious joke in one cultural context can be confusing or tone-deaf in another.
Stage 4: Run the event with intention, not just participation
The event is 60–90 minutes. The engagement is largely made in the two weeks before and the week after.
Two weeks before the event: Manager activation matters more than the announcement email. The same event sent as a cold Slack post routinely gets around 40% attendance. The same event preceded by a manager saying "I've looked at the brief — I want to be on your team for Stage 2" gets 75–80%. Operationally, this means sending managers a 2-paragraph brief, not a 10-slide deck. Tell them what's coming, tell them their job is to show up enthusiastically and mention it ahead of time. That's the entire intervention.
When we ran BGaming's multi-year anniversary event — roughly 400 employees across 12+ countries — the pre-event brief to department leads was the single most operationally important decision we made together with the People Ops team. Completion rates came in at 89% against a 75% target, and team members cited the pre-event energy from their managers in the post-event free-response.
Day-of: For Big Game formats, the client team's only job is to show up. The HeySparko Game Host runs the entire session — no client MC required, no slide decks, no handoffs. For Marathon formats, each daily episode is automated, but a manager's informal 2-sentence message in Slack on Day 2 is the most effective single intervention for driving Day 3 completion. Not a corporate reminder notification. Something actual: "Who figured out the cipher in Episode 2 before me?" outperforms a well-designed automated nudge by a wide margin.
Post-event: Use the analytics report. Every HeySparko event generates a participation dashboard — completion rates, team-by-team NPS, engagement by manager pod. For the HR Leader building the business case for recurring events, this data is what turns "we ran a fun thing" into "here's which manager pods are below threshold and what the event moved for each of them." That's a defensible brief to Finance. A memory of a good Zoom call is not.
Responsibility: HR Lead owns the manager pre-brief. Managers own the activation inside their teams. HeySparko handles the day-of entirely.
Timing: Pre-brief to managers 12–14 days before the event. Post-event analytics delivered within 24 hours.
What could go wrong — and how to address it before it does
Playbooks that skip this section are missing half the operational value. These are the five failure modes we see most, in order of frequency.
The manager is visibly absent. The most reliable predictor of low attendance in any team pod is the manager being somewhere else during the event. This is not fixable through event design — it's a relationship question to address with that manager before the next cycle. The analytics will surface it: low completion rate and low NPS in one team pod against a high company average is almost always a manager-presence pattern.
Wrong format for the time zone spread. We've seen Big Games booked for teams distributed across 14 hours of working-day difference. Someone takes a 5am session. That person's post-event NPS is negative, not neutral — and their Slack message about it is visible to the whole team. Pull the time zone data when scoping the format, not after the calendar invite has already gone to 600 people.
Participation without engagement. A Marathon player who opens the game but scores zero on Day 1 puzzles is technically participating and genuinely not engaged. This usually signals a problem at the team level that predated the event — high deadline pressure, a recent reorg, friction with a manager. The event isn't the cure, but it is a diagnostic surface. Low puzzle completion plus low NPS in the same manager pod is a flag for the HRBP.
The game doesn't fit the audience. Bureau of Magical Affairs is excellent for the right team and genuinely confusing for the wrong one. We recommend a 10-minute game preview call for first-time HeySparko clients — it takes less than the alternative of running a whimsy-heavy adventure for a group of buttoned-up legal professionals who were expecting a corporate mystery. Tone mismatch is almost always avoidable in a 10-minute conversation.
Treating the event as the full program. One event per quarter is a maintenance schedule. The event creates a shared experience and a data point. The manager 1:1 cadence, the recognition moments, the development conversations that follow — those are the program. The event is the punctuation, not the sentence.
What the data says about manager-driven remote engagement
The financial case for taking this seriously starts with McKinsey Quarterly 2023 research on workplace performance: employee disengagement and attrition cost a median S&P 500 company 228 to 355 million dollars annually in lost productivity, totaling more than 1.1 billion dollars over five years. That number gets more interesting when you look at where engaged employees cluster. The same McKinsey Quarterly 2023 analysis found that only 4% of employees qualify as "thriving stars" delivering disproportionate value — and that specific thriving stars cohort breaks down as 45% remote, 36% hybrid, 19% in-person.
The implication for People Ops is direct: your highest-value employees are disproportionately in distributed work arrangements. Disengaging them is not just a culture problem with a budget line attached — it's a performance problem with a balance-sheet consequence.
Gallup's 2025 State of the Global Workplace report puts the manager as the primary lever: 70% of variance in team engagement is attributable to the direct manager. Not the company's event budget. Not the People Ops program calendar. The manager's 1:1 quality, their recognition habits, their visible presence in the channels where their team operates. For HR Leaders designing an engagement program, this framing changes the goal. The event isn't the program — it's a tool for giving managers a shared experience, team-level data, and a moment that makes subsequent 1:1 conversations easier to have.
Deloitte's 2024 Burnout in the Workplace report adds context from a different angle: 77% of US professionals report burnout at their current job, with 31% naming lack of recognition as the primary driver — ahead of workload. Workers who attended two or more company-sponsored events per quarter reported 23% lower burnout symptoms than those who didn't. Recognition and structured connection are the mechanism; structured team events are one of the most reliable vehicles for both.
The academic research validates how the mechanism works at a structural level. Anog et al. (SSRN, 2023) — a systematic review of 60+ studies — found that structured team-building activities increase satisfaction and reduce voluntary turnover, with the effect amplified when activities are integrated into a broader development strategy rather than deployed as isolated one-off interventions. This is precisely the distinction between a "fun day" and a real engagement program: what the manager does in the two weeks before and after the event determines how much of the effect sticks.
SHRM 2024 cost-per-hire data puts a non-executive departure at 15,000 to 21,000 dollars per person, factoring in recruiting, onboarding, and ramp time. At those numbers, an engagement initiative that prevents two or three departures across a 200-person team has covered its cost before the post-event analytics land in your inbox.
Our Marathon data adds a practical dimension to the picture. Across 500+ engagements in the format, we see 65–78% voluntary completion rates across all three daily episodes. These are opt-in events, not mandatory attendance. Completion at that level, without enforcement, is the clearest signal that the format design is working: players come back not because a calendar invite obligates them, but because the leaderboard creates pull and the narrative arc makes them want to know what happens next. That engagement dynamic — intrinsic, not coerced — is the one that shows up in engagement survey scores three months later.
Frequently asked questions
How do we actually measure whether a remote team engagement event worked?
Start with what comes standard: participation rate, team-by-team NPS, and completion rates for Marathon format. Then pair the event data with your next engagement pulse. The signal worth tracking isn't the average event NPS — it's whether the manager pods that showed low participation changed in subsequent cycles, and whether teams who completed the event score differently on the 90-day follow-up. HeySparko delivers a post-event analytics report within 24 hours that includes by-manager-pod breakdowns, which is the data point your Finance partner will actually want to see.
How often should we run remote team engagement events?
The connection effect from a structured team gathering decays to baseline over roughly four months — which implies about three events per year as the minimum to sustain measurable team-connection lift, based on longitudinal research in this area. In our portfolio, the companies with the most durable engagement score improvement run one Big Game or Marathon per quarter as the predictable program rhythm, with lighter optional activities in between. One event per year is a shared memory. One per quarter is a rhythm the team can anticipate — and anticipation is itself an engagement signal.
What's the actual difference between Big Game and Marathon for a distributed remote team?
Big Game is a single live 60–90 minute event where the whole team plays simultaneously — high energy, real-time leaderboard, everyone watching the same scoreboard at once. Marathon runs over 1–5 days with daily content unlocking on schedule and players engaging on their own time. For teams with a 3+ time zone spread and less than 3 hours of shared working-hour overlap, Marathon reaches significantly more participants without forcing anyone onto an inconvenient call. For teams within a 6-hour spread who want the live energy, Big Game is the natural default. The format decision usually makes itself once you've mapped the actual calendar constraints.
Do remote employees need to download or install anything to participate?
Nothing to install and no account creation required. Players join via a browser link that works on corporate-locked laptops, personal devices, and mobile. This matters operationally: "install a new app" is one of the most reliable ways to lose 15–20% of your participant pool before the event starts. Every HeySparko game — the mechanics, the leaderboard, the team chat during gameplay — runs entirely in the browser. IT doesn't need to be involved. For global teams on varied device configurations, this is not a trivial detail.
How do we get managers more invested in remote engagement events?
Two specific interventions work reliably. First, give managers the by-team analytics report after the event — their team's participation rate and NPS relative to the company median. Managers who see that data become noticeably more engaged in the next event cycle; the number makes it concrete in a way that a general "we hope everyone participates" message doesn't. Second, send a 2-paragraph pre-brief to managers 12–14 days before the event. Not a detailed playbook — just what's coming and the expectation that they mention it to their team. Manager enthusiasm in advance is the highest-return lever in remote event design.
How far in advance do we need to book a remote team engagement event?
For a stock Big Game or Marathon without customization, 7–10 business days is workable. If you want NPC customization (characters scripted in your company's voice), allow at least 14 days. Story tier customization (a full custom narrative arc tied to your specific team situation) requires 21+ days — there's a briefing call plus a revision round involved, and the quality of the customization depends on that time. For events at 500+ people with any customization, 4–6 weeks is the comfortable planning range. Pricing across all configurations is transparent at /en/pricing — no sales call required to see the numbers.