When I worked for a nationwide company, that was chiefly WFH with several small satellite offices, and a few abroad as well, we had some timezone issues.
The main one, which became my pet peeve about event and meeting announcements, was that they always, always used Standard Time abbreviations, whether it was DST or not DST, they always specified standard time.
So if a meeting was at 3pm on June 13 in Delaware, it was announced as "3pm EST". If the meeting was at 9am on August 8 in California, it was announced "9am PST".
This drove me up the wall because, living in Arizona, there is a legitimate difference for us between "MDT" and "MST". Now if we anticipate this quirk, it is really not a problem, except for edge-cases.
But I complained and asked why they were doing it, and they said they'd always done it that way, and even implied that it was written into policy somehow, and I came to discover it was far more widespread than just our one company's internal comms, and my brain exploded with ASD dissonance.
The main one, which became my pet peeve about event and meeting announcements, was that they always, always used Standard Time abbreviations, whether it was DST or not DST, they always specified standard time.
So if a meeting was at 3pm on June 13 in Delaware, it was announced as "3pm EST". If the meeting was at 9am on August 8 in California, it was announced "9am PST".
This drove me up the wall because, living in Arizona, there is a legitimate difference for us between "MDT" and "MST". Now if we anticipate this quirk, it is really not a problem, except for edge-cases.
But I complained and asked why they were doing it, and they said they'd always done it that way, and even implied that it was written into policy somehow, and I came to discover it was far more widespread than just our one company's internal comms, and my brain exploded with ASD dissonance.