This question carries hints of annoyance or laughter (or both), and when tossed at you in a conference call, it can be a frustrating one.
People tend to place more trust in those we can physically interact with, and technical issues never seem to fully disappear. A conference call simply has more dependencies than gathering in a meeting room, and occasionally it takes our focus away from accomplishing more interesting things!
Below are my tips and tricks to reduce friction throughout the call experience, all under the purview of remote attendees. Later, you’ll meet Meekee, a Slack & Google Calendar bot that I built with Marion to make it all easier.
Before the call:
Starting the call:
During the call:
Ending the call:
What works for your team? I’d love to keep expanding this list.
As you can see, many of the things we can do to gracefully join a call, we need to do at the start. It’s especially important to get right when we have multiple calls throughout the day. Switching contexts between meetings is hard enough without having to deal with the technology.
My typical work day in Paris starts with 2–3 hours of calls with colleagues and clients in the Asian timezones. The calls are scheduled back-to-back. Sometimes, everyone else is in the same room on the other side of the world. It’s stressful to be late and under-prepared — and I really dislike stress that’s small, recurring and unnecessary. 😣
After scrambling one too many times to open the right Hangout link on whatever device I wanted to take the call from, I started looking for a way to get Slack notifications: IFTTT, Zapier, the official Gcal/Slack integration etc.
(I’m a big fan of Slack’s thoughtful cross-device notification system. Have you seen their marvelous decision flowchart?)
They offer varying degrees of customization, including the ability to be pinged 5, 10, 15 minutes before the next event. The problem was that none of these solutions include the Google Hangout link — a tiny but critical piece of the puzzle. I also encountered a signal vs noise problem with getting buzzed about solo work or loose placeholders. Lunch, for example.
So, I teamed up with Marion to make a small piece of ‘glue’ between Slack, Google Calendar and Google Hangout — three apps which most of us at AQ keep open throughout the day and access from multiple devices. It’s a just-in-time notification bot that nudges you to start preparing for an upcoming meeting via a Direct Message on Slack.
Let me point out the key design decisions:
Pronounced Meeeee Keeee, short for Meeting Keeper. It includes the Hangout link (all GCal events have one by default) and the name of a physical room if one is reserved. Marion added the randomized emoji on a whim, and it’s turned out to be a small detail that we really enjoy. Along with the Meekee character that our creative director Ryan designed, it brings a bit of quiet fun to what’s inherently a dry message that you’ll receive many, many times 😙
Meekee is quite the opinionated creature. It will be wildly useful or absolutely useless. The criteria for the former is so rigid, it seemed almost absurd to build it: you have to be using these three apps in a pretty specific way… and care enough about being on time for meetings. Which is not a given, tbh.
But amidst all the excitement and confusion over AI-powered chatbots, it tickled us to roll a teeny tiny single-celled bot that’s super helpful for 1 second, a few times a day, every workday.
You can give it a whirl here: Meekee - get just-in-time meeting Slack notifications from Google Calendar
We hope it’s helpful for other geeky teams who centralize meeting invites to GCal, rely on Slack for communication, and…www.meekee.io
And watch out for Marion’s upcoming write-up about the technical side of building a Slack bot that connects with Google services. Bonus: the code is open source!
September 16, 2017