Running Standups Across Time Zones Without Losing Anyone

Somewhere between three and four timezones, "let's find a time that works for everyone" stops being a scheduling problem and starts being a math problem with no solution. A team split across San Francisco, Berlin, and Bangalore doesn't have a shared working hour — it has a choice about whose morning gets sacrificed.

The "least bad" time is still bad for someone

Most teams solve this by rotating the pain — one week the Berlin team joins at 6pm their time, the next week Bangalore joins at 10pm. It feels fair on paper. In practice, it means a third of the team is tired or distracted at any given standup, and everyone's slightly resentful on their rotation week. Rotating unfairness is still unfairness, just spread out.

The deeper issue is that a live meeting assumes a shared "now." A globally distributed team doesn't have one, and no scheduling trick actually creates one — it just picks who has to pretend.

What works instead

• Drop the live requirement for status. If the goal is "know what everyone did and what's blocking them," that doesn't need real-time presence. It needs everyone to write it down within a window that fits their own day.
• Give each person their own working hours, not one global slot. A cutoff that's "end of your working day" respects a 9-to-5 in Bangalore exactly as much as one in Berlin, without anyone joining a call at midnight.
• Reserve live time for the rare thing that needs it. When two people genuinely need to talk something through in real time, that's a two-person conversation, scheduled for when both are actually awake — not a whole-team meeting forced into an inconvenient slot for everyone else.
• Make the async version the source of truth, not a consolation prize. If the real information lives in a call half the team missed, async was never actually adopted — it was just added on top.

Coverage matters more than synchronicity

What a distributed team actually needs isn't everyone online at once — it's confidence that today is covered, wherever "today" happens to fall for each person. A team lead in San Francisco should be able to open a board at 9am their time and see who's already posted, who's still working, and who's out, without needing anyone else awake to explain it.

Strova handles this with per-person and per-team schedules — working days, hours, and holidays configured individually — so the cutoff and grace period respect each person's actual day, and the DSM board shows real-time coverage across every timezone your team spans, without anyone joining a call outside their working hours.