Yes. (Or better, give employees flexibility to come in at a time that works for them).

> If you take away timezones and just say "everybody use UTC and somehow figure out how to adjust it to your local conditions", you've just pushed the cost of figuring out reasonable start & end times for different geographies onto every single member of society. All that will happen is people will come up with their own mappings between UTC and local conditions and guess what? They will look pretty close to what we have with timezones right now only it won't be standardized at all--making a huge mess of things. Outlook calendar will have its own mapping and Google Calendar will have a different one. Your company might have its own internal mapping that is different from your suppliers. Whoa be the person who tries to coordinate an event across these mappings ("your company does lunch at 17:49? Ours does it at 18:42 because that is closer to when the sun is overhead and people like to get in around 12:42")

"Mapping UTC onto local conditions" is not a problem that you ever have to solve. There are two kinds of problems you need to solve: coordinating events that happen in one location, and coordinating events that happen at a particular instant with people from multiple locations. For the first kind it doesn't matter if every office has its own solution - indeed it's better if every office has its own solution that fits their own conditions and the Norway office can start work at 8 and the Spain office can start at 11 if that suits the local climate, rather than deciding that both those countries are on CET so they'd both better start at 9AM CET. For coordinating a simultaneous event, UTC is the only thing that works (because if you try to use your local time and you get the offsets wrong, neither of you will notice).

> Whoa be the person who tries to coordinate an event across these mappings ("your company does lunch at 17:49? Ours does it at 18:42 because that is closer to when the sun is overhead and people like to get in around 12:42")

What problem does this create that doesn't already exist? If you're trying to arrange a lunch today, some people have lunch at 12, 1 or even 1:30 local time.