When a meeting lands at 6 a.m. for one person and 9 p.m. for another, the usual response is to ask someone to “be flexible.” That framing treats the problem as individual goodwill instead of calendar design. Time zones are a design problem. Once you treat them that way, the solutions become clearer and fairer.
I am Dan Whitaker. I work with distributed teams across multiple time zones and live in Raleigh with my family. I have watched the same pattern repeat: the person who is easiest to reach absorbs the inconvenience until they burn out or quietly disengage. Less hassle starts with better defaults.
Why “Just Be Flexible” Fails
Flexibility is a limited resource. When every scheduling decision relies on someone giving it up, the same people usually pay the cost. Parents of young children, caregivers, and people in less common time zones end up with the worst slots. The calendar looks full of collaboration while the actual load is uneven.
I have been on both sides of this. Early in my career I said yes to almost every early or late call because it felt easier than pushing back. Later, as someone helping teams design better workflows, I saw how quickly “temporary flexibility” becomes permanent expectation. The people who pay the price are rarely the ones setting the meeting.
Better Design Defaults
Label every meeting with at least two time zones in the title or description.
Default to async updates unless a live conversation is clearly required.
Rotate early and late slots when live meetings are unavoidable.
Protect core focus hours for each major region instead of treating every hour as available.
Write down the shared definition of “reasonable hours” so it is not renegotiated every week.
These defaults do not eliminate the need for occasional inconvenient meetings. They prevent inconvenience from becoming the default setting for the same people.
A Practical Scheduling Approach
If I were setting this up for a normal distributed team I would start with a shared understanding of “reasonable hours” for each location, then build the calendar around that. Tools that display multiple time zones help, but the real work is the agreement about what is fair.
Meeting Decision Guide
Situation | Prefer Live Meeting | Prefer Async |
|---|---|---|
Quick status share | No | Yes |
Complex decision with many stakeholders | Yes | Sometimes |
Handoff between regions | Rarely | Yes |
Relationship or sensitive feedback | Yes | No |
Recurring check-in with no decisions | No | Yes |
Urgent incident response | Yes | No |
The table is a starting point, not a rigid rule. The goal is to stop treating every conversation as something that requires everyone to be awake at the same time. Most status updates and handoffs work better as written records that people can read when they are actually working.
What Teams Can Do This Week
Add time-zone labels to existing recurring meetings.
Move one low-value live meeting to an async update format.
Agree on a simple “no-meeting” block that respects the largest overlapping work window.
Write down the handoff expectations so people are not left waiting for a reply that will not come until the next day.
Review the last two weeks of meetings and notice who repeatedly took the early or late slot.
Small changes compound. Teams that treat time zones as a design problem spend less time apologizing and more time doing the actual work. The calendar becomes a tool for fairness instead of a source of quiet resentment.
Simpler is better. Clear labels, async defaults, and shared fairness rules reduce the daily friction more than any new scheduling tool. Made simple means the process itself stays light enough that people actually follow it.
Additional Notes from the Field
The hidden cost of poor time-zone design is not just lost sleep. It is the slow erosion of trust when the same people repeatedly absorb the inconvenience. Teams that fix the design problem often notice that participation becomes more even and that the quality of written updates improves because people are no longer rushing to join a call at an awkward hour.
I still keep a personal rule: if a meeting requires someone to be awake outside their normal working window, it needs a clear reason and a rotating fairness check. Without that, the calendar quietly becomes a tax on the people least able to push back.
The practical test I use is simple: after two weeks of the new default, are people spending less time coordinating and more time doing the actual work? If the answer is yes, the design is working. If the answer is no, the default needs another adjustment. The goal is not a perfect calendar or a perfect tool list. The goal is a system that creates less daily friction for the people who have to live with it.
The calendar becomes a tool for fairness instead of a quiet source of resentment. Teams that treat time zones as a design problem spend less time apologizing and more time doing the actual work. Clear labels, async defaults, and shared fairness rules reduce daily friction more than any new scheduling tool.
Made simple. Simpler is better. Less hassle. More life.