Ramon never complained, which was part of the problem. Every week the design sync landed at what the calendar invite cheerfully called “10:00 AM,” and every week that 10:00 was somebody’s morning coffee, somebody’s working lunch, and — for Ramon, eleven time zones east — the dead middle of the night. He would join anyway, camera on, voice bright, a lamp burning behind him at three in the morning in Manila.
No one meant to do this to him. That is what made it stubborn. The team was kind. They would say “let’s find a time that works for everyone,” and then do the time-zone math in their heads — a calculation that, it turns out, quietly rounds toward whoever is doing the calculating. The person furthest away becomes a rounding error. The rounding error was a human being setting an alarm for 2:45 a.m.
Why “what time works for you?” keeps failing
Ask a distributed team to agree on a time and you are really asking each person to translate every proposed slot into their own local reality — and to do it in a shared thread where half the times are written without a zone at all. “Does 4 work?” Four where? By the time everyone has converted, misconverted, and re-asked, the meeting has cost more coordination than it will ever deliver.
A time zone isn’t a detail you add at the end. For half your team, it’s the whole question.
The breakthrough wasn’t a heroic act of empathy. It was smaller than that. Instead of proposing one time and asking everyone to bend around it, Ramon’s lead sent a poll — several candidate slots at once — and asked a different question: not “can you make 10 a.m.?” but “which of these actually work for you?”
Let everyone answer in their own hours
The trick is that each person saw every option in their own local time. No mental conversion, no zone abbreviations to decode. Ramon looked at a list of times that were already his times, marked the two that fell inside his waking life, and moved on. Everyone else did the same.
When the responses came back, something became visible that heads-in-a-thread had never been able to see: a genuine overlap. Not perfect — someone in California took an early start, someone in Berlin stayed a little late — but a slot where nobody was asleep. The 3 a.m. shift didn’t get reassigned. It just stopped existing, because the meeting moved to an hour that was fair to all of them at once.
Coordinating across zones isn’t about being clever with arithmetic; it’s about not making anyone do the arithmetic in the first place. Meeting Time shows each participant their own local time and lays every option side by side, so the humane overlap you were hoping existed turns out to be something you can actually see — and book.