Meeting Agenda for March 6th, 2006
Lately it feels like I spend more time sitting in meetings than actually sitting in my office doing work. It looks like another case of Reoccurring Wasteotimeinmeetengitus; a very serious infliction that has created an estimated $600-billion revenue loss for the year of 2005. I’ve created an agenda here to help us understand the damages inflicted upon our profits and create some discussion about mainstreaming a process that will break the mold of these conventional paradigms.
To begin with, let’s look at our previous agenda and address any action items that might have arisen or need to be addressed. Alright, there looks like there are a couple of comments below that seem to confirm the last post, so nothing new needs to be addressed. Moving on to the topic at hand, there seems to be some positive energy flowing around our current value stream process deficiencies and some opportunities that lie ahead. Some data gathering has taken place to provide a more well-informed open discourse on the topic, so we’ll dive right into that.
It seems there are 21 working days in the month of March (excluding of course weekends and Friday’s off), which leaves us with 165 working hours to deal with. That number of course comes from the standard 80-hours of work on a bi-weekly basis, subtracting the time spent for lunches and non-meeting times when no meeting would ever potentially take place, theoretically. Of course the actual times for these dates are subjective to change, but barring any unforeseen schedule breaks, let’s assume that 165-hours is our potential meeting time for the month. My current estimate of meeting hours already scheduled for the month (not including the potential add/drop of meetings for the month) comes out to approximately 74 hours. Using these hypothetical values we come up with a result of about 45% of my time at work is spent in meetings.
If we extrapolate this percentage out as a yearly average then we could use it to also represent the percentage of salary made while in meetings (and thus money lost due to idleness). The result we’re looking at annually is a $31,500 revenue loss, which of course is just for one employee and if our average meeting attendance is 12-people for the year, then the loss becomes $378,000/year. This is just one part of one company so expand this out exponentially world-wide and you’ve got some serious revenue loss occurring.
There aren’t any action items to follow up on this info-sharing process, and I think what we should all take from this is an awareness of the severity of Reoccurring Wasteotimeinmeetengitus. Maybe in the future some steps can be taken to streamline these processes and build some proactive measures to address the main opportunities faced here. Thank-you all for participating in this forum and I’ll send out a notice about our next scheduled appointment.
To begin with, let’s look at our previous agenda and address any action items that might have arisen or need to be addressed. Alright, there looks like there are a couple of comments below that seem to confirm the last post, so nothing new needs to be addressed. Moving on to the topic at hand, there seems to be some positive energy flowing around our current value stream process deficiencies and some opportunities that lie ahead. Some data gathering has taken place to provide a more well-informed open discourse on the topic, so we’ll dive right into that.
It seems there are 21 working days in the month of March (excluding of course weekends and Friday’s off), which leaves us with 165 working hours to deal with. That number of course comes from the standard 80-hours of work on a bi-weekly basis, subtracting the time spent for lunches and non-meeting times when no meeting would ever potentially take place, theoretically. Of course the actual times for these dates are subjective to change, but barring any unforeseen schedule breaks, let’s assume that 165-hours is our potential meeting time for the month. My current estimate of meeting hours already scheduled for the month (not including the potential add/drop of meetings for the month) comes out to approximately 74 hours. Using these hypothetical values we come up with a result of about 45% of my time at work is spent in meetings.
If we extrapolate this percentage out as a yearly average then we could use it to also represent the percentage of salary made while in meetings (and thus money lost due to idleness). The result we’re looking at annually is a $31,500 revenue loss, which of course is just for one employee and if our average meeting attendance is 12-people for the year, then the loss becomes $378,000/year. This is just one part of one company so expand this out exponentially world-wide and you’ve got some serious revenue loss occurring.
There aren’t any action items to follow up on this info-sharing process, and I think what we should all take from this is an awareness of the severity of Reoccurring Wasteotimeinmeetengitus. Maybe in the future some steps can be taken to streamline these processes and build some proactive measures to address the main opportunities faced here. Thank-you all for participating in this forum and I’ll send out a notice about our next scheduled appointment.
posted by Chris Burzlaff @ 3/08/2006
<< Home