You glance at the meeting invite: 2:00 PM. You pause. 2:00 PM where? Yours? Theirs? The server’s? You spend another forty seconds mentally converting, checking if daylight saving is involved, and still send a follow-up asking, “Wait, that’s my time or yours?”
This tiny ritual of confusion happens millions of times a day. And it’s not your fault. It’s the fault of a system we inherited from an era of steam trains and telegraphs—time zones. They are a 140-year-old hack that we’ve been too polite to admit is broken.
The sun doesn’t care about your time zone. It’s always noon somewhere, and that’s the problem. We’ve built a global digital civilization on a local, analog clock. The result: friction, delays, and a chronic low-grade headache that we’ve normalized.
Enter New Earth Time (NET). It’s not a gimmick. It’s a radical simplification: a single, decimalized time standard based on a 360-degree circle. The Earth rotates one degree every four minutes. So 0° NET is midnight at the Prime Meridian. Each degree is a unit. No time zones. No offsets. No confusion.
You’ve probably already felt the pain this solves. You work remotely with someone in Singapore, a client in London, and a team in São Paulo. Every scheduling decision is a negotiation. Every deadline is a translation. Time zones are a form of temporal tribalism—they make you feel safe at home while silently sabotaging global collaboration.
The psychological comfort of “local time” is real. We wake with the sun, we eat when it’s dark. But that’s an emotion, not a necessity. We already override local time with electric lights, shift work, and Zoom calls. The sun is no longer the boss of our schedules. So why are we still pretending time zones are natural? They are as natural as standardized railroad gauges—useful once, now a bottleneck.
I saw this firsthand while coordinating a cross-continent product launch. We had a Slack channel called #what-time-is-it. It was a joke. It was also a cry for help. On New Earth Time, that channel disappears. You say “meet at 45° NET” and everyone knows exactly when that is. No conversion. No second-guessing.
Critics will say: “But what about sunrise? What about lunch?” The answer: you can still have local habits. You just stop using them as global anchors. You keep your 7 AM coffee ritual, but you don’t force the rest of the planet to decode it. Neutrality in time is death for efficiency. Pick a universal standard or accept endless friction.
New Earth Time isn’t perfect. It requires relearning a skill we thought was basic: telling time. But the payoff is a world where a timestamp means the same thing to everyone, everywhere. No more “I’ll send it tomorrow” (which day? which time zone?). No more missed deadlines because someone was on daylight saving and someone wasn’t.
The twist? The system already exists. It was proposed in 2000. It’s been gathering digital dust for 24 years. We just weren’t ready. But now, with remote work permanent, with AI agents scheduling across borders, with a generation that thinks in UTC anyway—the moment is ripe. The most revolutionary idea in timekeeping is not a new clock. It’s realizing that the old one was never about time at all—it was about power. Who decided that Greenwich gets to be zero? Who decided that your noon must be my midnight? Time zones are not physics; they are politics. And politics can be rewritten.
So the next time you waste five minutes deciphering a time zone, ask yourself: Why? Why are we still using a system designed for a world that no longer exists? The answer is inertia. But inertia is not a reason. It’s an excuse. And it’s time we stopped making it.
FAQ
Q: Doesn't New Earth Time ignore the fact that humans have biological clocks tied to the sun?
A: Not at all. You can still eat, sleep, and work based on your local solar cycle. NET is a global communication standard, not a replacement for your local schedule. Just like you use UTC for servers but live by local time, NET is a neutral reference—except it's much easier to read and convert.
Q: What's the practical benefit of switching to a 360-degree time system?
A: It eliminates every time-zone related error in scheduling, deadlines, and coordination. For a remote team, that means no more missed calls, no more 'is that my time or yours?' emails, and no more accidental 3 AM meetings. It turns a constant source of friction into a single, unambiguous number.
Q: Isn't this just adding another layer of complexity? Why not just use UTC?
A: UTC is already a universal standard, but it's still based on a 24-hour cycle with 60-minute hours—a legacy from Babylonian astronomy. NET's decimal system makes mental arithmetic trivial: 15° = 1 hour, 1° = 4 minutes. No more converting hours to minutes or remembering which timezone has an offset of +5:30. It's simpler in the same way decimal currency is simpler than pounds, shillings, and pence.