Hi there,

Nothing quite grinds work to a halt than seeing this Slack from a colleague – Why am I not on tomorrow’s call? You said it’s at 2 pm but it’s not on my calendar.

Everything stops. 

It’s impossible to multitask while in Google Calendar (if you’ve figured this out, please let us know how).

So you pull up the calendar, confirm the invite list, and see that this person is indeed on the calendar invite.

So you start to confirm with them + then realize – ohhh, I said 2 pm because it’s at 2 pm in New York. But my colleague is in LA so it will be at 11 am for them. That’s probably why they think they’re not on the invite. Oops.

Those few wasted minutes are forever lost to the depths of Google Calendar.

Remote Octopus recommends clearly identifying time zones in Slack messages. If you’re working remotely, consider including multiple time zones based on the common locations of your team.

A handful of letters clarifying the time zone(s) in your Slack messages will help you take time back from Google Calendar. No more deep sea diving to figure out who is on which invite list due to time zone confusion. It seems small – but all of those minutes will add up over a year!

Ready to level up operational excellence for your team? Check out our resources: