TL;DR — Culture built around a live meeting only reaches whoever is awake for it. A distributed team needs culture that works asynchronously by default, with recognition, milestones and check-ins designed so no region is quietly left out. This is a practical playbook for making that work.
- Default to async for anything cultural; treat a live moment as a bonus, not the main event.
- Rotate meeting times rather than fixing them permanently to one region's convenience.
- Recognition and milestones need the same time-zone thinking as meetings do.
On this page
Why culture breaks first across time zones
Process tends to survive a distributed team reasonably well; culture is what erodes first. A live all-hands, a Friday social call, a birthday shout-out in a channel at 4pm — all of these quietly exclude whoever is asleep when they happen. Nobody intends this, but a team that never audits its own schedule for whose convenience it favours ends up building culture for one region and calling it company culture.
Designing for async first
The reliable fix is treating anything live as optional and anything asynchronous as the real version. A recorded video message, a written update anyone can read when they start their day, or a shared link people respond to on their own time all survive time zones in a way a scheduled call never will. Live moments still have value for the people who can make them, but they should never be the only version of the thing.
A time-zone-fairness check
Run this check against anything recurring on the culture calendar — meetings, recognition moments, social events.
| Question | What to do if the answer is no |
|---|---|
| Does this work for people in every region on the team, not just the one hosting it? | Move to an async format or rotate the time. |
| If this is a recurring meeting, does the inconvenient slot rotate across regions? | Set up a rotation rather than fixing it to one region permanently. |
| Can someone fully participate without attending live? | Record it, or replace it with a written or video update. |
| Would a new hire in the most distant time zone feel included by this? | Redesign with that person's week in mind, not the founding team's. |
Recognition and milestones across regions
Recognition is especially vulnerable to time-zone bias, since it often happens spontaneously in whichever channel is most active at that moment — usually wherever the most people are currently awake. Building recognition around a shared, asynchronous link rather than a live channel shout-out keeps every region equally able to contribute. The same applies to farewells and anniversaries; see Culture Pulse on Video: Wellbeing Check-ins People Answer Honestly for the same async-first thinking applied to check-ins.
A simple rhythm that scales
Most distributed teams that get this right settle into a similar rhythm: a weekly async update everyone reads in their own time, one rotating live touchpoint that moves across time zones, and a standing async channel for recognition and milestones that nobody has to be awake for. None of it is complicated; the discipline is in checking it against the fairness questions above rather than letting it default to whoever set it up first.
How to do this in Whoosh
Recognition, farewells, milestones and check-ins can all run through a single shared link that works the same regardless of time zone — no live call to schedule, no region left guessing what they missed.
Start freeFrequently asked questions
Is a live all-hands ever worth keeping?
Yes, as a bonus for whoever can attend — just make sure a recorded or written version covers everyone else fully, not as an afterthought.
How do we rotate meeting times fairly?
Alternate which region takes the inconvenient slot on a fixed schedule, rather than leaving it to whoever complains loudest.
Does async culture feel less personal?
Not if it carries tone — a short video message async still feels more personal than a scheduled meeting nobody from a distant region could attend.
What's the first thing to fix if culture already skews toward one region?
Audit recognition and milestones first — they are usually the most visibly skewed and the easiest to move to an async format.