The IT Manager (ITMGR.org)
Musings on IT management, project management, and security

   ★ Breaking ★    ★   News:    ★
  • Home
  • The IT Manager’s Blog
  • IT?
  • People
  • Technology
  • Process
  • Project Management
  • Security & Compliance
  • Resources

Blog Categories

  • Compliance
  • Cool Stuff
  • Databases
  • End User Computing
  • IT management
  • MSP
  • Networking
  • Note to self
  • Old Technology
  • Project management
  • SDLC
  • Security
  • SharePoint/SPS/MOSS
  • Social Media
  • Systems Administration
  • Tech News & Gossip
  • Telecom
  • The Cloud
  • Uncategorized
  • Unix/Linux
  • Vendor Management
  • Windows Server
  • Wordpress

Archives

  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009

The IT Manager’s Blog:

 

______________________________________________________________________________________________________

Rumsfeld's meeting rules

Posted on May 12, 2013 by Shannon Gaw

This weekend’s WSJ printed an excerpt from a forth coming book by Donald Rumsfeld regarding meetings. As Rumsfeld has held posts as a CEO and Secretary of Defense, he should know something about this.

Here’s the meat of it…

  1.  Do we need a meeting?   ”The default tendency in any bureaucracy, especially in government, is to substitute discussion for decision-making. If you are the leader of an organization and call a meeting, make sure you have something to communicate or need to learn in a group setting. If the meeting is to be purely informational, without much back and forth, that information could probably be as easily relayed in a memo or email.”
  2.  Avoid a meandering session. Rumsfeld says “When I moved into my first executive position in government in 1969, I had a stand-up desk…. standing up while working tends to be an incentive for those who come in for a discussion to say what they need to say, and not linger”.
  3. Invite the right people. He thinks that generally too many unnecessary people are invited to meetings.
  4. Start and end on time.  This is universal meeting advice.
  5. Be prepared and expect preparedness. “During meetings, I confess to being less than patient with folks who bring up irrelevant information or are ill-prepared. I also tend to lack patience with PowerPoint presentations that convey obvious information or slides with grammatical errors and that lack page numbers. There were occasions when I abruptly ended a meeting in progress and advised the participants that we would reconvene when everyone had had time to fully prepare. The response was usually surprised looks all around. In my experience some leaders don’t end meetings when it’s clear they’ve become a waste of time. Instead they sit there and let the meeting experience a slow, painful death.”
  6.  ”Encourage others to give their views, even if it may ruffle some feathers.”
  7. And then expect resistance to new thinking. “Keep in mind that when new ideas are broached in a meeting, there is often an instinctive and immediate opposition. Large bureaucracies can be masterful at creating an insular and self-serving culture in which people reinforce each other and become captive to what becomes the conventional wisdom. Meetings are a good place to discover whether an organization might be suffering from groupthink. If everyone in the room seems convinced of the brilliance of an idea, it may be a sign that the organization would benefit from more dissent and debate.”
  8. Summarize important points and action items. Also, he says “I’ve found it can also be helpful to offer a last opportunity for anyone in the room to speak up by my asking, ‘Is there anything else?’ or ‘What have we missed?’ There often is something important that someone was thinking of saying and never found the opportunity for.”

 

 

  Add to Google Reader or Homepage

Recent Posts

  • Rumsfeld’s meeting rules
  • Why aren’t you here?
  • Project Management Now and Later Tasks
  • Obsolete IT skills – 2013 version
  • AA/SABRE outage
  • Good Stuff
  • Yahoo questions telecommuting
  • Honesty
  • PMBOK v5
  • Cisco sells Linksys

Tags

Amazon Apple AWS Certifications chrome Cisco Cloud COBIT DBA Dell DR employment Gartner Google HP interviewing iPad iPhone IPv6 ITIL jobs Manager Tools meetings Microsoft Office Oracle Paul Glen People PM QA RIM Security Social Media SOPA SQL Server Stupid holiday tablet TCP/IPv6 telecom TMG VMWare Windows Windows Server Wordpress Yahoo
The IT Manager (ITMGR.org)
Copyright © 2013 All Rights Reserved
                                              Sitemap   |     About     |     Contact
Web Design by Gaw Systems