ETA: @HMS_Irruncible two posts up …
I’m not suggesting it’s a bad thing. I am suggesting it will add more variety and hence more frictional vexation to many interactions.
As you yourself said to @thorny_locust 2 posts ago, what matters is knowing when something is open or when somebody is at work. That need is there now under the current system and it would still be there under any proposed replacement system, including yours.
Right now I can guess that I can call somebody at work or call some customer service department whenever it’s between about 9am and 5pm in their local time zone. I might miss them at the ends of the day, and I might be leaving out some time they are open, but I have that rule of thumb to go by. But that certainly doesn’t work even now for people or businesses that operate with non-traditional hours. Such as myself and my employer.
The rule of thumb would be totally out the window in your system. The only way to know when someone or something is available for business is to ask them. Or, more logically, we’d all end up with our contact info including our contact days/hours expressed in UTC as well as our emails, phone numbers, etc. And yes, our chosen personal pronouns too.
Many US national businesses websites already publish contact info like “Telephone customer service available at 800-123-4567 on Mon-Fri from 8am Eastern to 7pm Pacific.” Wherein the hours are a) longer than just the “normal” 8 hours and b) are expressed in one or more time zones.
As you rightly suggest, it’d be trivial for that to change to read “Telephone customer service available at 800-123-4567 on Mon-Fri from 1300Z to 0300Z.”
But …
One legit issue this does raise, which we already deal with frequently in my industry, is that the UTC date and day of the week will change during the middle of the workday for many people.
e.g. In the early evening on the US east coast under the current system, when it’s 10pm on Fri Mar 16th (2023-03-16T22:00:00) local, it’s 2am on Sat Mar 17th in UTC (2023-03-17T02:00:00Z). In all the airlines’ interactions with the public, that’s late on Fri the 16th. In all our internal systems and in dealings with worldwide air traffic control, that’s early on Sat the 17th. We’re all used to making that conversion back and forth many times every single evening, but mistakes still happen.
Getting the public on board with the name of the day and the date changing at dinner time, or at lunch time, or after breakfast but while they’re still driving to work will be … challenging.
We in the airline industry have a problem right now with flights that depart shortly after midnight local time. Statistically speaking, a larger than normal number of both passengers and crew no-show these flights because they get confused that a flight departing at, say, 1am on Saturday means they need to get ready then show up on Friday evening, not get ready on Saturday evening for what they think of as their Saturday departure. Oops. Suxs to be them.
Having that day-of-week/date changeover occur in the midst of the local daylight period will greatly multiply the oopsies. Humanity may become more technologically advanced, but individual humans will remain as clueless and distracted as ever. The kid’s school day starts on Thursday, but it’ll be Friday before you get to work 90 minutes later? Recipe for confusion. And not just during the transition from traditional timekeeping. At the unluckiest longitudes It’ll be every day of every week.
And even more so if at the higher latitudes society takes advantage of the flexibility to in effect have latitude-based DST, where organized hours for schools, work, retail, etc., really follow the sun and shift several times per year as the length of daylight waxes and wanes and waxes again. We in the airline industry deal with this now, where the start time and duration of our operational workday alternately shrinks and stretches in the two hemispheres to provide product when the customers want it.
My bottom line: Flex is good. Flex adds complexity. Flex adds vexation. There is no free lunch where obstinate and clueless bulk humans are involved.