Celebrating a Win When Half the Team Wasn’t in the Room

A project wraps successfully, and the office-based half of the team goes out for lunch to mark it. Photos get posted in the team channel afterward — genuine, warm, well-intentioned. For the half of the team joining from home or another location, the message that actually lands isn’t “we did something great together.” It’s a quieter, harder-to-name feeling of having been present for the work but absent for the moment the work got acknowledged. Nobody meant to create that gap. The format of the celebration created it anyway.

Recognition Formats Often Assume Everyone’s in the Same Room

Most default ways of celebrating a win — an in-person gathering, a round of drinks after work, an impromptu team lunch — were designed for a fully co-located team and still carry that assumption even after a team has become distributed. This isn’t a moral failing on the part of whoever organizes it; it’s simply the default that comes to mind first, because it’s what celebration has always looked like. The gap only becomes visible when someone actually asks how it felt to the people who couldn’t be there, and that question often doesn’t get asked, because the celebration itself felt successful to the people who experienced it directly.

Why a Video Call Version Often Falls Flat Too

The obvious fix — hold the celebration on a video call so everyone can join — solves the exclusion problem but often introduces a different one: recognition delivered through a screen, competing with the awkwardness of a group video call, frequently reads as performative rather than genuine, precisely because video calls are the same format used for status meetings and difficult conversations. Asking a team to suddenly feel celebratory in the same medium they associate with routine business rarely produces the warmth an in-person gathering generates naturally, even when the intent behind it is identical.

What Actually Translates Across a Distributed Team

Recognition approach	Why it does or doesn’t translate
In-person lunch or drinks	Excludes anyone not co-located, however warmly intended
Group video call celebration	Includes everyone, but the format often feels forced
Personal, specific written recognition	Translates well; doesn’t depend on shared physical presence
Small tangible gesture sent to each person	Requires more effort but reaches people wherever they are
Public recognition in a shared channel, specific rather than generic	Works if it names real contributions, not just a generic “great job team”

The pattern across the rows that actually work is specificity and individual reach, rather than a shared physical or synchronous experience that assumes everyone can be present for it.

Specific Recognition Beats Shared Presence

A distributed team doesn’t need every celebration to replicate the feeling of being physically together — that’s a genuinely hard thing to manufacture remotely and chasing it often produces a worse version of the in-person experience rather than a good version of something else. What actually lands well remotely is recognition that’s specific to each person’s real contribution, delivered in a way that reaches them individually rather than requiring them to be present at a particular moment. A message that names exactly what someone did and why it mattered carries real weight whether it’s read live in a meeting or found later in an inbox, in a way that a generic “great job everyone” attached to a lunch photo simply doesn’t.

Avoiding the Trap of a Two-Tier Celebration

The most damaging version of this problem isn’t lacking any celebration for remote team members — it’s an unintentional two-tier system where the in-person team gets a genuine, warm moment and everyone else gets a follow-up message summarizing what they missed. This is worse than no celebration at all in some ways, because it makes the divide between co-located and remote experience explicit and visible rather than simply absent. If a celebration can’t practically include everyone equally, it’s often better to choose a format that reaches everyone at a slightly lower intensity than to run a high-intensity version for some and a diminished echo for the rest.

Asking Rather Than Assuming What Feels Meaningful

Different people, in different roles and different locations, often have genuinely different preferences for what recognition feels meaningful to them — some value public acknowledgment, others find it uncomfortable and would rather receive something private and specific. A team that asks directly, even informally, tends to land on approaches that actually resonate rather than defaulting to whatever the person organizing recognition would personally find meaningful, which may not match what the actual recipients would.

Making Recognition a Habit, Not Just an Event

Milestone celebrations matter, but they’re infrequent by nature, and a distributed team benefits from smaller, more regular recognition that doesn’t depend on a major win to justify it — a specific callout in a regular team update, a habit of naming individual contributions rather than only team-level outcomes. This kind of steady, distributed recognition reaches remote team members as reliably as it reaches co-located ones, because it was never built around a shared physical moment to begin with, and it reduces how much weight any single celebration event has to carry on its own.

The goal isn’t manufacturing a remote equivalent of an in-person party — that’s usually a losing effort. It’s building recognition habits from the start that don’t quietly assume everyone is in the same building, so that when a real win happens, celebrating it doesn’t accidentally remind half the team of exactly how far away they are from where the moment is actually happening.

Letting Co-Located Teams Still Have Their Own Moment

None of this means co-located team members should be discouraged from ever going to lunch together to mark a win — that impulse is genuine and healthy, and suppressing it entirely in the name of equity often just produces resentment in the opposite direction. The more useful distinction is between a spontaneous, informal gathering among people who happen to share an office, which doesn’t need to be treated as the team’s official celebration, and the actual, deliberate act of recognizing the win as a team, which should be designed to reach everyone. Keeping these two things separate — a casual local moment that’s allowed to exist on its own terms, and a genuine team-wide recognition that doesn’t depend on physical presence — avoids both the trap of an accidental two-tier celebration and the overcorrection of eliminating spontaneous local warmth altogether.

Budgeting Real Effort for Distributed Recognition

Recognition that reaches a distributed team well rarely happens by accident — it requires someone to actually think through who’s on the team, what would land for each of them, and to follow through on individual outreach rather than defaulting to a single group message and calling it done. This takes more deliberate effort than booking a table at a restaurant, and teams that get this right tend to treat it as seriously as they’d treat any other piece of team-building work, rather than assuming good intentions alone will translate automatically into people actually feeling seen.