Remote work gets painful when “what time is it for you?” becomes the main topic of every chat. This workflow helps you find overlap fast, communicate expectations, and keep meetings fair.
Why “overlap” is the only scheduling metric that matters
Don’t start with “who can attend at 9am.” Start with shared working hours. Once you see overlap, you can decide whether the meeting belongs inside core hours, should rotate, or should be async.
A simple workflow for teams in 2–6 time zones
1) Define “working hours” (not just time zones)
Time zone alone is not enough. Two people in the same city can still have non-overlapping schedules. Agree on a default window (e.g. 09:00–17:00) and treat it as a starting point, not a rule.
2) Find the overlap window
Use a visual tool (like ZoneGrid) to locate the shared block. If the overlap is less than ~2 hours, consider making the meeting async or rotating.
3) Decide: core hours vs rotation vs async
A quick rule of thumb:
- Core hours for recurring team meetings.
- Rotation for cross-region meetings where a single slot hurts one group every time.
- Async when overlap is too small or meeting value is low.
Sharing setups with your team
If your ZoneGrid configuration lives in the URL, you can paste it into docs or Slack and everyone sees the same setup. That avoids the “wait, which time zone did you pick?” confusion.
/app.html?tz=America/New_York,Europe/Warsaw&hours=9-17
Common mistakes
- Scheduling based on one person’s convenience.
- Assuming “9–5” means the same in every country or role.
- Recurring meetings that never rotate.
- Overusing meetings when async would do.
Next steps
If you want to go deeper, read: Best meeting time across multiple time zones.