Browse Prior Art Database

Using analytics to avoid unnecessary meetings

IP.com Disclosure Number: IPCOM000241945D
Publication Date: 2015-Jun-10

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes a mechanism to use analytics to avoid unnecessary meetings. It's done by analyzing the user's meeting history and other data like organization structure and social relationship, and it notifies the user whether he should attend a meeting or not when he receives a meeting invitation.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 79% of the total text.

Page 01 of 10

Using analytics to avoid unnecessary meetings

There are tons of meetings being held in every company everyday, but big part of them are not effective for part of their attendees. Remember attending an hour long meeting where only one minute of it was related to you? This happens almost everyday to many people, and companies waste tens or even hundreds of million of dollars on those meetings. A tool that can help everyone identify meetings that will potentially be ineffective for him so he can ignore that meeting is highly desired, and will save a lot of money for companies.

The overall architecture looks like this:

The detailed flow for how we establish the knowledge base for helping user avoid meetings can be explained by this chart:

1



Page 02 of 10

2



Page 03 of 10

And this is how the "Identify Patterns" in the above chart is done:

3



Page 04 of 10

After we have built the capability, the advice will be sent out and determined at three specific time: At the time the user receives the invitation or reschedule, the time the meeting is about to start, and after the meeting. The detailed flow of these specific time are displayed below:

4



Page 05 of 10

When receiving invitation

5



Page 06 of 10

6



Page 07 of 10

When the meeting is about to start:

When the meeting is finished:

An example of what is being evaluate to make our decision and how that is done is displayed in charts below:

Looking at the reporting structure relationship between the user and the host and atten...