<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why Most Meetings Still Suck</title>
	<atom:link href="http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/feed" rel="self" type="application/rss+xml" />
	<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html</link>
	<description>CEO, Thomas Nelson Publishers</description>
	<lastBuildDate>Thu, 18 Mar 2010 23:13:51 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Most Tweeted Articles by Leadership Development Experts</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-49138</link>
		<dc:creator>Most Tweeted Articles by Leadership Development Experts</dc:creator>
		<pubDate>Thu, 04 Mar 2010 02:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-49138</guid>
		<description>[...] initiative and to be...         2  Tweets     iTunes Store     iTunes Store         2  Tweets     Why Most Meetings Still Suck     As long as you have to have meetings, you might as well do them well. Before you plan another [...]</description>
		<content:encoded><![CDATA[<p>[...] initiative and to be&#8230;         2  Tweets     iTunes Store     iTunes Store         2  Tweets     Why Most Meetings Still Suck     As long as you have to have meetings, you might as well do them well. Before you plan another [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @RichardJett</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-48914</link>
		<dc:creator>@RichardJett</dc:creator>
		<pubDate>Mon, 01 Mar 2010 17:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-48914</guid>
		<description>Is giving money or a treat to those who answer/interact inappropriate? Kidding...kind of. Great article. </description>
		<content:encoded><![CDATA[<p>Is giving money or a treat to those who answer/interact inappropriate? Kidding&#8230;kind of. Great article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fran</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-42724</link>
		<dc:creator>Fran</dc:creator>
		<pubDate>Thu, 31 Dec 2009 22:22:59 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-42724</guid>
		<description>These are good suggestions. I don&#039;t enforce a &quot;no electronics&quot; rule - I find that by having the agenda published in advance, starting on time, moving quickly through the topics and soliciting input (i.e. &quot;Michael, what are your thoughts on this?&quot;) people tend to stay engaged. The only other suggestion I might add is to publish minutes.  
My recent post &lt;a href=&quot;http://amothersangst.blogspot.com/2009/12/bos-cafe-book-review.html&quot; target=&quot;_blank&quot;&gt;Bo&#039;s Cafe - a Book Review&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>These are good suggestions. I don&#039;t enforce a &quot;no electronics&quot; rule &#8211; I find that by having the agenda published in advance, starting on time, moving quickly through the topics and soliciting input (i.e. &quot;Michael, what are your thoughts on this?&quot;) people tend to stay engaged. The only other suggestion I might add is to publish minutes.<br />
My recent post <a href="http://amothersangst.blogspot.com/2009/12/bos-cafe-book-review.html" target="_blank">Bo&#039;s Cafe &#8211; a Book Review</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D Shick</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-42711</link>
		<dc:creator>D Shick</dc:creator>
		<pubDate>Thu, 31 Dec 2009 18:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-42711</guid>
		<description>While I understand the motive behind the no blackberry/no laptop rule, I have begun using Microsoft One Note to input my personal meeting notes.  I&#039;ve also found it helpful to look back on the notes from previous meetings using the programs valuable search tool.  So I&#039;m not ready to subscribe to that rule just yet and wonder how others feel?  Good topic. </description>
		<content:encoded><![CDATA[<p>While I understand the motive behind the no blackberry/no laptop rule, I have begun using Microsoft One Note to input my personal meeting notes.  I&#039;ve also found it helpful to look back on the notes from previous meetings using the programs valuable search tool.  So I&#039;m not ready to subscribe to that rule just yet and wonder how others feel?  Good topic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeff</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-27093</link>
		<dc:creator>jeff</dc:creator>
		<pubDate>Wed, 24 Jun 2009 21:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-27093</guid>
		<description>Nice post, Michael - looks like an oldie, but a goodie. Not to sound contradictory, but my experience has been showed me that sometimes, meetings that even meet these parameters can still suck. They can be dull or predictable. They can become rote or meaningless. 
 
For me, a remarkable meeting shows respect to all of the attendees (a non-negotiable), but it also goes beyond that. It&#039;s creative, interactive, and, in some cases, leaderless. Most meetings are monologues or uncreative in their use of technology and media. I like having an predefined outcome/goal, but sometimes that can be as simple as saying, &quot;We&#039;re going to discover X&quot; in this meeting. 
 
For me, a meeting is a success if people want to come back to the next one. We do evaluations at the end of each meeting, and this keeps my humble. Some are great; some, not so much. I experiment with giving the floor to different speakers/facilitators, and we&#039;re learning together how to makes these times more valuable. 
 
Other than Lencioni, who else would you recommend? </description>
		<content:encoded><![CDATA[<p>Nice post, Michael &#8211; looks like an oldie, but a goodie. Not to sound contradictory, but my experience has been showed me that sometimes, meetings that even meet these parameters can still suck. They can be dull or predictable. They can become rote or meaningless. </p>
<p>For me, a remarkable meeting shows respect to all of the attendees (a non-negotiable), but it also goes beyond that. It&#039;s creative, interactive, and, in some cases, leaderless. Most meetings are monologues or uncreative in their use of technology and media. I like having an predefined outcome/goal, but sometimes that can be as simple as saying, &quot;We&#039;re going to discover X&quot; in this meeting. </p>
<p>For me, a meeting is a success if people want to come back to the next one. We do evaluations at the end of each meeting, and this keeps my humble. Some are great; some, not so much. I experiment with giving the floor to different speakers/facilitators, and we&#039;re learning together how to makes these times more valuable. </p>
<p>Other than Lencioni, who else would you recommend?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leadership, Productivity and Books&#8230; &#187; 17 Hours &#8211; This Better Be Worth It!</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-6770</link>
		<dc:creator>Leadership, Productivity and Books&#8230; &#187; 17 Hours &#8211; This Better Be Worth It!</dc:creator>
		<pubDate>Thu, 26 Mar 2009 15:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-6770</guid>
		<description>[...] Well, that’s about how many person hours are taken up in our monthly leadership meeting at church and we are determined not to have our volunteers give up their precious time on meetings that suck (thanks Michael Hyatt). [...]</description>
		<content:encoded><![CDATA[<p>[...] Well, that’s about how many person hours are taken up in our monthly leadership meeting at church and we are determined not to have our volunteers give up their precious time on meetings that suck (thanks Michael Hyatt). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Olund</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-999</link>
		<dc:creator>Kyle Olund</dc:creator>
		<pubDate>Thu, 06 Nov 2008 22:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-999</guid>
		<description>Good thoughts, Pete. What is necessary is better discernment to know when an e-mail should be sent instead of a meeting request, and when a meeting should be called to avoid an onslaught of e-mails on one topic/problem (that happened yesterday, and if we were all in the same building we could have met instead of seen 40+ e-mails exchange between different people--a least that&#039;s how many ended up in my in- or cc-box).
</description>
		<content:encoded><![CDATA[<p>Good thoughts, Pete. What is necessary is better discernment to know when an e-mail should be sent instead of a meeting request, and when a meeting should be called to avoid an onslaught of e-mails on one topic/problem (that happened yesterday, and if we were all in the same building we could have met instead of seen 40+ e-mails exchange between different people&#8211;a least that&#8217;s how many ended up in my in- or cc-box).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Gallagher</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-1000</link>
		<dc:creator>John Gallagher</dc:creator>
		<pubDate>Thu, 06 Nov 2008 01:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-1000</guid>
		<description>Not enough just to focus.  It is important to PARTICIPATE.
</description>
		<content:encoded><![CDATA[<p>Not enough just to focus.  It is important to PARTICIPATE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Nikolai</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-1001</link>
		<dc:creator>Pete Nikolai</dc:creator>
		<pubDate>Wed, 05 Nov 2008 16:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-1001</guid>
		<description>Would it be productive to establish the following Meeting Mandates here at Nelson?

1) an explicit outcome/purpose in the Meeting Request

2) an agenda at least 24 hours prior to the meeting with clear indication of who is responsible for taking and forwarding the notes within 24 hours after the meeting

The consequence of violating either of these Mandates could be as simple as people declining the Meeting Request.

From my perspective, the only valid purposes for meetings are to debate (and possibly then to make a decision), to brainstorm, to celebrate positive accomplishments, and to acknowledge major negative developments and brainstorm course corrections. Meetings should never be used just to communicate information or build relationships.

Most workers can quickly identify their co-workers who seem to think that nothing can get done without discussing it in a meeting first. While there are legitimate reasons for gathering people together (as stated above), far too often the little that is actually accomplished in a meeting could have been done in more efficient ways. Information could be communicated via email. Relationships could be built over lunch or a round of golf. Socializing could happen at more appropriate times in more appropriate places.

The other dysfunctional aspect of many meetings is the strange manifestation known as the “presentation.” Any vital information (other than surprise announcements) contained in a presentation should be sent in an email at least 24 hours in advance so that participants have time to review and research prior to the meeting. Then the meeting should consist of a quick debate or brainstorming session by informed participants. Vital information can be put on screen, but there is no need for that information to be presented—people need to be trusted to have done their homework.

Perhaps the most frustrating thing about meetings is that many of the people involved know they could be using that time to get their prioritized Tasks done so that they can have more time for other important things (at work or elsewhere). If the organization clearly supports best practices such as those outlined above, workers should be able to reclaim considerable time to do just that.

</description>
		<content:encoded><![CDATA[<p>Would it be productive to establish the following Meeting Mandates here at Nelson?</p>
<p>1) an explicit outcome/purpose in the Meeting Request</p>
<p>2) an agenda at least 24 hours prior to the meeting with clear indication of who is responsible for taking and forwarding the notes within 24 hours after the meeting</p>
<p>The consequence of violating either of these Mandates could be as simple as people declining the Meeting Request.</p>
<p>From my perspective, the only valid purposes for meetings are to debate (and possibly then to make a decision), to brainstorm, to celebrate positive accomplishments, and to acknowledge major negative developments and brainstorm course corrections. Meetings should never be used just to communicate information or build relationships.</p>
<p>Most workers can quickly identify their co-workers who seem to think that nothing can get done without discussing it in a meeting first. While there are legitimate reasons for gathering people together (as stated above), far too often the little that is actually accomplished in a meeting could have been done in more efficient ways. Information could be communicated via email. Relationships could be built over lunch or a round of golf. Socializing could happen at more appropriate times in more appropriate places.</p>
<p>The other dysfunctional aspect of many meetings is the strange manifestation known as the “presentation.” Any vital information (other than surprise announcements) contained in a presentation should be sent in an email at least 24 hours in advance so that participants have time to review and research prior to the meeting. Then the meeting should consist of a quick debate or brainstorming session by informed participants. Vital information can be put on screen, but there is no need for that information to be presented—people need to be trusted to have done their homework.</p>
<p>Perhaps the most frustrating thing about meetings is that many of the people involved know they could be using that time to get their prioritized Tasks done so that they can have more time for other important things (at work or elsewhere). If the organization clearly supports best practices such as those outlined above, workers should be able to reclaim considerable time to do just that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Wallis</title>
		<link>http://michaelhyatt.com/2008/11/why-most-meetings-still-suck.html/comment-page-1#comment-1002</link>
		<dc:creator>Paul Wallis</dc:creator>
		<pubDate>Wed, 05 Nov 2008 14:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhyatt.com/?p=29#comment-1002</guid>
		<description>Hi Mike,
Amen to what you&#039;ve shared here. When applied thoughtfully all these points apply to church-gathering too.

In any meeting where conversation and decisions are involved our group also follows the advice of St Benedict in his C6th &quot;Little Rule for Beginners&quot;, Chapter Three - &quot;concerning the calling of the brethren to council&quot;.

Benedict&#039;s main points are that the leader&#039;s role is to facilitate a conversation in which:

1) every person is heard, even the most junior

2) the matter must be clarified,

3) everyone to seek first to understand the matter in hand

4) each one speaks to the group&#039;s purpose not out of a purely personal agenda

5)the leader facilitates the drawing of a conclusion and the putting forward of a proposal for the group to own and act upon

6) the right of the leader is reserved to &#039;lead from the front&#039; and act on his own judgment. However Benedict&#039;s strong advice is always to seek counsel before making a decision and as rarely as possible to act outside of the group&#039;s conclusions. Benedict takes this as a tool for safeguarding God&#039;s timing in important matters.

We find all this still incredibly relevant. It may be relevant even to team meetings at ThomasNelson?!

Thanks Again,

Paul Wallis
</description>
		<content:encoded><![CDATA[<p>Hi Mike,<br />
Amen to what you&#8217;ve shared here. When applied thoughtfully all these points apply to church-gathering too.</p>
<p>In any meeting where conversation and decisions are involved our group also follows the advice of St Benedict in his C6th &#8220;Little Rule for Beginners&#8221;, Chapter Three &#8211; &#8220;concerning the calling of the brethren to council&#8221;.</p>
<p>Benedict&#8217;s main points are that the leader&#8217;s role is to facilitate a conversation in which:</p>
<p>1) every person is heard, even the most junior</p>
<p>2) the matter must be clarified,</p>
<p>3) everyone to seek first to understand the matter in hand</p>
<p>4) each one speaks to the group&#8217;s purpose not out of a purely personal agenda</p>
<p>5)the leader facilitates the drawing of a conclusion and the putting forward of a proposal for the group to own and act upon</p>
<p>6) the right of the leader is reserved to &#8216;lead from the front&#8217; and act on his own judgment. However Benedict&#8217;s strong advice is always to seek counsel before making a decision and as rarely as possible to act outside of the group&#8217;s conclusions. Benedict takes this as a tool for safeguarding God&#8217;s timing in important matters.</p>
<p>We find all this still incredibly relevant. It may be relevant even to team meetings at ThomasNelson?!</p>
<p>Thanks Again,</p>
<p>Paul Wallis</p>
]]></content:encoded>
	</item>
</channel>
</rss>
