I once missed a flight not because I overslept, but because I trusted a calendar invite. The meeting organizer had set it for “9 AM” without specifying a time zone, and by the time I realized the mistake, I was three hours off and standing at a gate that had already closed. It sounds like a small thing. It wasn’t. That missed flight cost me a client, a hotel deposit, and two days of rescheduling that rippled through the rest of the month.
Most people don’t think about time until it betrays them like that.
We treat clocks as background noise, something that just works, quietly syncing on our phones, adjusting itself when we land somewhere new. And for the most part, it does work. But the moment your life or your business crosses a border, time stops being simple. It becomes a variable you have to manage, the same way you’d manage a budget or a schedule of deliverables.
The pieces nobody warns you about
Not every country shifts its clocks for daylight saving. Some do it on different dates than others, even within the same hemisphere. A handful of regions run on half-hour or 45-minute offsets instead of clean hourly differences (India, for instance, or parts of Australia). If you’re coordinating a call between London, Mumbai, and Adelaide, you’re not just subtracting a few hours; you’re navigating a small puzzle that changes twice a year depending on who observes what.
I keep a habit now of checking a live world clock before I book anything that spans more than one country, something like worldtimedata.com, because doing the math in my head has burned me too many times. It takes fifteen seconds and it’s saved me from double-booking calls, from showing up to video meetings at the wrong hour, from the quiet embarrassment of asking “wait, is it tomorrow for you already?”
Jet lag is not a personality flaw
There’s a strange tendency among frequent travelers to treat jet lag as something you should just push through, as if suffering is a badge of professionalism. It isn’t. Your circadian rhythm needs roughly a day to adjust for every hour of time difference you cross. Fly from New York to Tokyo and you’re looking at nearly two weeks before your body fully catches up, though most people function reasonably well after three or four days if they sleep smart.
The people who handle this best aren’t the ones who “power through.” They’re the ones who build in a buffer: arriving a full day early before anything important, shifting their sleep schedule gradually in the days leading up to a trip, and accepting that the first meeting after a long-haul flight will not be their sharpest one, no matter how much coffee is involved.
Why logistics teams live and die by this
If you’ve ever worked adjacent to supply chains, you already know that “today” in a Shenzhen warehouse can already be “tomorrow” for a customer in Los Angeles. That gap isn’t trivial. It affects when orders are confirmed, when customs paperwork gets processed, and when a shipment officially “misses” a cutoff. A logistics coordinator who doesn’t account for this ends up explaining delays that were never really delays, just misread clocks.
The same applies, on a smaller scale, to freelancers and small business owners working with overseas clients. A deadline stated as “end of day Friday” means almost nothing unless both sides agree on whose Friday.
A few things that actually help
Writing meeting times in UTC, at least as a reference point, removes almost all the ambiguity, since everyone can convert from there. Checking whether a country still observes daylight saving before assuming a time difference stays constant year-round is worth the extra minute, especially since several countries have quietly dropped the practice in recent years. And building slack into any schedule that spans multiple time zones, even just twenty minutes, gives you room when someone inevitably gets the math wrong.
Where the whole system actually comes from
It’s easy to forget that standardized time zones are a fairly recent invention. Before railways forced the issue in the late 1800s, towns kept their own local solar time, set by whenever the sun hit its highest point overhead. A train timetable that had to account for hundreds of slightly different “noons” across a single country was unworkable, which is essentially how the modern system of time zones was born: a practical fix for a scheduling headache, not some grand scientific decree.
If you want the fuller version of that history, how UTC became the global reference point, why the international date line sits where it does, and how the whole system holds together, Understanding Time lays it out clearly without turning it into a physics lecture.
None of this requires becoming obsessive about clocks. It just means treating time the way you’d treat any other resource that’s easy to waste and hard to get back, worth a little more attention than we usually give it, especially right before the moments that actually matter.
