click anywhere to close
Meeting Impact Calculator

Meeting Delays

Why does it take a long time to get anything done in some organizations? If meetings among busy people are required to make progress, things slow down. Just how much?

See this simple simulation below. You could get large gains even with a small reduction in the number of meetings.

Say 5 people have to collaborate on a 40 person hour project.
How long does it actually take to complete?
Meeting Delays Calculator
Multitasking Level (1-10)
Parallel projects each person is involved in
% Collaboration Level
Total time spent in meetings
Answer: ?

How Kamune helps

Even if Kamune helps decrease the need for one meeting, you get savings. Here are severals ways Kamune helps:

  • People can get good context and updates from the logbooks that they otherwise get from meetings.
  • People that just attend a meetingto see what was going on can skip the meeting and read the transcripts at their convenience instead.
  • Someone on the road can read the transcripts on Kamune from their mobile phone.
  • People can hold meetings on Kamune (no audio/video yet), through text chat, sharing and custom slide presentations. These are surprisingly effective when participants are in different cities or countries.
  • Questions that don't need a full meeting can be answered through other means on Kamune, from chat to bubbles to to logbooks.
  • Some routine meetings, like status updates, can be eliminated altogether by using logbooks on Kamune.
What should you try?
a. Click simulate several times for each set of data, to get a sense of the averages and variance.
b. Increase the multitasking level slowly to see that project completion time takes a really long time. Notice that if this is the only project everyone works on, completion time is low
c. Increase collaboration level and notice that the more meetings they have, the longer it takes. Also notice that at 0 meetings, you get the fastest project completion time.

Key Assumptions
One key assumption is that the need for the meeting is not known in advance. The wait time is computed at the time that the meeting is supposed to take place. The modeling leans towards fluid collaboration more than assembly line style collaboration. The plan essentially is a dependency graph with meetings serving as synchronization points.

Copyright © 2009 Navaraga Corporation