<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tom LaForce &#187; Meetings</title>
	<atom:link href="http://tomlaforce.com/tag/meetings/feed/" rel="self" type="application/rss+xml" />
	<link>http://tomlaforce.com</link>
	<description>Meeting Facilitator, Public Speaker, Trainer &#38; Team Building Consultant Serving the Twin Cities of Minneapolis &#38; St. Paul</description>
	<lastBuildDate>Tue, 01 May 2012 21:15:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>5 Good Reasons to Call a Meeting</title>
		<link>http://tomlaforce.com/5-good-reasons-to-call-a-meeting/</link>
		<comments>http://tomlaforce.com/5-good-reasons-to-call-a-meeting/#comments</comments>
		<pubDate>Thu, 05 Apr 2012 18:25:20 +0000</pubDate>
		<dc:creator>Tom LaForce</dc:creator>
				<category><![CDATA[Meeting Management]]></category>
		<category><![CDATA[Meetings]]></category>
		<category><![CDATA[purpose]]></category>

		<guid isPermaLink="false">http://tomlaforce.com/?p=2998</guid>
		<description><![CDATA[Many of the worst meetings we find ourselves stuck in should never have happened in the first place. If you're thinking about calling a meeting, make sure you have a good reason for doing so.]]></description>
			<content:encoded><![CDATA[<p><a href="http://tomlaforce.com/wp-content/uploads/2012/04/Yes-No-Maybe.jpg"><img style=' display: block; margin-right: auto; margin-left: auto;'  class="aligncenter size-large wp-image-3000" title="Yes No Maybe" src="http://tomlaforce.com/wp-content/uploads/2012/04/Yes-No-Maybe-568x345.jpg" alt="" width="568" height="345" /></a></p>
<p>There are way too many meetings that should never have happened in the first place. You know it. I know it. And we are all more than a little sick of having to sit through these meetings. They waste our time and bore us to tears.</p>
<p>So what should you do if you&#8217;re thinking about calling a meeting and have doubts about whether or not you should? Let me ease your concern. Just because there are a lot of meetings that should never have occurred doesn&#8217;t mean that there aren&#8217;t some that should have been held. Your goal is to only call one when there&#8217;s a good reason for doing so. I can think of at least five good reasons to call a meeting. Would be interested in learning about others if you can think of some.</p>
<ol>
<li>You&#8217;ve got a problem you can&#8217;t solve on your own and don&#8217;t know of any one person who you can ask to solve it for you. You believe the solution will require the creative brainpower of a group.</li>
<li>You need a decision that affects a group, and you believe it should be made by the group rather than imposed upon them.</li>
<li>You need to put together a plan. You recognize the importance of involving others in order to build a better plan and generate more buy-in.</li>
<li>You&#8217;ve got news to share that will likely cause an emotional reaction and generate lots of questions. You believe that it will be best to provide the information to everyone at the same time, and let all hear the answers to the questions that others ask.</li>
<li>You are launching a new initiative and want to bring people together for the purpose of setting the direction and establishing guidelines.</li>
</ol>
<p>See a theme? All these reasons have an element of two-way interaction. Great meetings are a collaborative activity, and you should call one only if collaboration is necessary.</p>
<p>There is one more thing that&#8217;s a little harder to identify, but you should try. Assuming you have a reason, and your reason requires collaboration; ask yourself if it&#8217;s worth it. The value equation is the one we apply in all sorts of situations. It fits here as well. It boils down to &#8220;Value = Benefits &#8211; Costs.&#8221; Use your best estimates and consider not calling the meeting unless the result is positive.</p>
<p>We can tweak meetings to make them better, but the greatest impact can be realized by knowing when and when not to call a meeting in the first place.</p>
<p><em>Image credit: </em><a href="http://www.canstockphoto.com/"><em>© Can Stock Photo</em></a></p>
]]></content:encoded>
			<wfw:commentRss>http://tomlaforce.com/5-good-reasons-to-call-a-meeting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Give Them a Break</title>
		<link>http://tomlaforce.com/give-them-a-break/</link>
		<comments>http://tomlaforce.com/give-them-a-break/#comments</comments>
		<pubDate>Thu, 15 Mar 2012 13:13:05 +0000</pubDate>
		<dc:creator>Tom LaForce</dc:creator>
				<category><![CDATA[Meeting Management]]></category>
		<category><![CDATA[Breaks]]></category>
		<category><![CDATA[Meetings]]></category>
		<category><![CDATA[Time-outs]]></category>

		<guid isPermaLink="false">http://tomlaforce.com/?p=2958</guid>
		<description><![CDATA[The break is an important and useful tool that you should use when running longer meetings. Here are four situations when you should take one.]]></description>
			<content:encoded><![CDATA[<p><a href="http://tomlaforce.com/wp-content/uploads/2012/03/Breaktime-in-Paris.jpg"><img style=' display: block; margin-right: auto; margin-left: auto;'  class="aligncenter size-full wp-image-2960" title="Breaktime in Paris" src="http://tomlaforce.com/wp-content/uploads/2012/03/Breaktime-in-Paris-e1331816549972.jpg" alt="" width="568" height="319" /></a></p>
<p>In sports, teams call time outs. They do it when they want to think through their next move or when they want to stop the clock. You can do the same thing when running a meeting. There are at least four instances during a meeting when taking a break is a smart move.</p>
<h3>Butts and Bladders</h3>
<p>The first one is the obvious. People have been sitting too long and need to get up and move. I was recently appointed to a city commission. The first meeting I attended lasted four hours, without a break! By the end my chair was no longer my friend. Focusing on a meeting and focusing on one&#8217;s butt and/or bladder are mutually exclusive. And we all know which one loses when they both demand our attention. My rule is two hours max without a break. For long meetings, 90 minutes between breaks is better.</p>
<h3>Transitions</h3>
<p>A second time to use breaks is as a transition between major accomplishments. After completing one activity take a break, even if it is just for a few minutes to stretch. This does three things. It reinforces the fact that the group has just accomplished something. This is always a good thing, especially since most people believe meetings are a waste of time. Second, it serves as a reward. People like breaks. Give them one when they&#8217;ve earned it. Third, it helps people clear their minds of the previous task. Take the example of when you just finished evaluating an idea. Now you want to move to a more creative activity. The break will help you shut down the critical parts of the participants&#8217; brains and engage the idea-generating parts.</p>
<h3>Need a Plan</h3>
<p>The third reason is when you need time to figure out what happens next. Perhaps the team has come to an impasse and everyone, including yourself seems a little unsure of how to proceed. This is a perfect time to walk away from the table for a bit. Doing so relieves the pressure of having to pull the rabbit out of a hat when everyone is staring at you. It also gives people a chance to have some informal conversations at break that might help solve the problem. This is most likely to happen if you plant a seed by saying, “We need to figure out what makes most sense in terms of how we move forward. Let&#8217;s take a break and give that a little thought.”</p>
<h3>Tempers Flaring</h3>
<p>There is a last situation when taking a break makes sense. When things start getting too hot and everyone needs to cool down a bit. Hopefully this a rare occurrence in the meetings you lead, but sometimes a fight breaks out and after doing everything you can think of to restore order, you run out of options. Call a break. Here&#8217;s my caution, though. Don&#8217;t call a break just because things get uncomfortable. Often, the uncomfortable conversation is exactly the conversations that needs to happen within a group. The trick is understanding the difference between a hot situation that is productive and one that is not.</p>
<h3>Take Breaks</h3>
<p>The break is an important and useful tool that you should use when running longer meetings. In sports, you&#8217;ll rarely see a coach criticized for calling time-out. There is plenty of criticism directed at coaches that didn&#8217;t call one when it was obvious to everyone else it was needed.</p>
<p><em>Image credit: <a href="http://www.flickr.com/photos/francisco_osorio/4824522315/">Francisco_osorio</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://tomlaforce.com/give-them-a-break/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

