{"id":599,"date":"2016-08-30T11:28:14","date_gmt":"2016-08-30T15:28:14","guid":{"rendered":"https:\/\/words.tev.net\/?p=599"},"modified":"2016-08-30T11:28:14","modified_gmt":"2016-08-30T15:28:14","slug":"outlook-and-google-calendar-suck-at-meetings","status":"publish","type":"post","link":"https:\/\/words.tev.net\/?p=599","title":{"rendered":"Outlook and Google Calendar Suck at Meetings"},"content":{"rendered":"<p>I want to talk for a moment about Outlook and Google Calendars, and how they suck for corporate business\u00c2\u00a0use.<\/p>\n<p>Both products use an &#8220;event&#8221; model for creating calendar items &#8211; this make sense for actual events like birthday parties and appointments like visits to the doctor. When you go to create a calendar item, the starting questions are: WHEN is this event, and WHERE will it be?<\/p>\n<p>But for business use, the use case is usually &#8220;we need to get these 5 people in a room to discuss something and make a decision&#8221;. The starting question is: WHO needs to attend, and what is the meeting LENGTH? There may be a day in mind, but the specific time and place are driven by when each attendee has available time, and when a meeting room is available.<\/p>\n<p>Despite this being the primary model for most business meetings, I have never seen a tool take this approach for building meetings.<\/p>\n<p>Here is how I would design the flow for this tool:<\/p>\n<p>Inputs: \u00c2\u00a0Attendees (+optional\/required), meeting length, desired day<\/p>\n<p>Data: Attendee availability, room availability, room size<\/p>\n<p>Output: List of room\/time pairs that would work for the meeting that day. Optionally, times that would work the previous or next business day (assuming the previous day is still in the future).<\/p>\n<p>Action: User selects\u00c2\u00a0one of the returned time\/place results, is prompted for meeting name\/description and clicks &#8220;Create meeting&#8221;<\/p>\n<p>Result: Meeting is created at the selected time with the room and attendees specified, using the provided name\/description.<\/p>\n<p>This flow would make much more sense for booking meetings in a corporate setting. The default event method is fine for actual events, or larger meetings where the meeting can happen without all attendees present (e.g. department quarterly meeting).<\/p>\n<p>I&#8217;m tempted to give this a shot with the Google Calendar API, although a quick look appears to show the only method for checking if someone has a time free is to send a specific time range and get back a boolean, so there may be a lot of queries required to find a common time that works for everyone.<\/p>\n<p>One approach might be to take the required attendee count, query for rooms available that day (filtered by working hours and no meetings from noon-1pm), then for the times rooms are available, query each attendee.<\/p>\n<p>Results could be weighted, so if there are no times that would work for everyone, the count of free vs total attendees for a given time would be used for the sort, and could return with a &#8220;warning: X, Y and Z cannot attend at this time&#8221;.<\/p>\n<p>Definitely something worth playing around\u00c2\u00a0with.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I want to talk for a moment about Outlook and Google Calendars, and how they suck for corporate business\u00c2\u00a0use. Both products use an &#8220;event&#8221; model for creating calendar items &#8211; this make sense for actual events like birthday parties and appointments like visits to the doctor. When you go to create a calendar item, the &hellip; <a href=\"https:\/\/words.tev.net\/?p=599\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Outlook and Google Calendar Suck at Meetings<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-599","post","type-post","status-publish","format-standard","hentry","category-post"],"_links":{"self":[{"href":"https:\/\/words.tev.net\/index.php?rest_route=\/wp\/v2\/posts\/599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/words.tev.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/words.tev.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/words.tev.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/words.tev.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=599"}],"version-history":[{"count":0,"href":"https:\/\/words.tev.net\/index.php?rest_route=\/wp\/v2\/posts\/599\/revisions"}],"wp:attachment":[{"href":"https:\/\/words.tev.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/words.tev.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/words.tev.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}