Jason Fried had a nice post the other day about the true cost of meetings. Many people think that a one hour meeting is just that, a one hour meeting, but they are completely ignoring the fact that a one hour meeting is actually one hour times however many people you invited to come to the meeting. When you take the true cost into account, it’s easier to decide if having the meeting is truly necessary. A very plausible example would be a one hour meeting for 5 developers who make $50-100 an hour; that ends up costing the company $250-500. It would only take a few of these five-hour meetings per week to start hurting the bottom line.
Archives
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- October 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- June 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006

This has a lot to do with the presentation by 37signals’ Jason Fried that I posted about a couple days ago. Its not just the one hour (times each person) that you lose, but rather the one hour times each person plus the added time it takes each of those people to get back “in their groove” of working. It isn’t a light switch that can be switched on and off.
There is an interesting interview thread with Jason and Matt from 37signals and Khoi Vinh (Design Director at the NY Times) and Jeffrey Veen (Product Director for Measure Map among other things) that discusses meetings and how the need for meetings may be something that increases with team size.
Making meetings optional is also a sort of Darwinian way to make sure meeting leaders make sure that their meetings are relevant and important. I like it.