So now, if you're living on the East Coast and you want to get up at 8am local time you need to set your alarm to 12pm UTC instead. But when you travel to Hawaii you need to set your alarm to 6pm UTC. And now every single one of your waking days is distributed across two days with the day change happening at local 2pm in the afternoon. Your work week is Monday through Saturday, your weekend is Saturday through Monday.
I do not understand why anyone ever thinks this insanity sounds like a good idea.
It also makes it easier to talk to others, if they say "6pm" you think "dinner time" or "just off work" without having to know the location of the person, at the time they're talking about, which may not even be where they are.
The phrase "Dinner on Thursday" would become really confusing. ("Do you mean after work on Wednesday? Or before the football game on Friday?")
This kind of local planning is far more common than long-range travel, and should be optimized for.
For edge cases involving cross-time-zone travel and communication, the solution I've seen implemented most often is to have two date-times shown in parallel. e.g. a flight is from 12:00 Pacific (4:00 Japan) - 14:00 Japan (22:00 Pacific).
The tldr; is that humans still operate more or less on the cycle of the sun