<?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>Tech Opener &#187; leadership</title>
	<atom:link href="http://techopener.com/blog/category/leadership/feed/" rel="self" type="application/rss+xml" />
	<link>http://techopener.com/blog</link>
	<description>Lets share more</description>
	<lastBuildDate>Sun, 02 May 2010 23:36:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/><cloud domain='techopener.com' port='80' path='/blog/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Effective Meetings 101</title>
		<link>http://techopener.com/blog/2009/10/effective-meetings-101/</link>
		<comments>http://techopener.com/blog/2009/10/effective-meetings-101/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 12:33:01 +0000</pubDate>
		<dc:creator>kenan</dc:creator>
				<category><![CDATA[leadership]]></category>
		<category><![CDATA[effective]]></category>
		<category><![CDATA[meetings]]></category>

		<guid isPermaLink="false">http://techopener.com/blog/?p=211</guid>
		<description><![CDATA[One thing that really bothers me is long in-effective meetings.  Here are a few basic meeting tips. Always have and distribute the objectives of the meeting beforehand.   (Hint: if you don&#8217;t have an objective, then you don&#8217;t need a &#8230; <a href="http://techopener.com/blog/2009/10/effective-meetings-101/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>One thing that really bothers me is long in-effective meetings.  Here are a few basic meeting tips.</p>
<ol>
<li>Always have and distribute the objectives of the meeting beforehand.   (Hint: if you don&#8217;t have an objective, then you don&#8217;t need a meeting.)</li>
<li>Meetings do not always have to be 1 hour in length.  If you just need 15 minutes, then schedule 15 minutes.</li>
<li>Once you complete the agenda of the meeting, end it.  Do not fill the rest of the meeting time with something unrelated.</li>
<li>Take notes and distribute them after the meeting to all attendees.  This makes sure everyone is on the same page and does not forget any conclusions.  Often handy for any follow-up meetings.</li>
<li>Start on time.  If people are frequently late, it becomes a trend and more people will show up later next time to avoid waiting for the late people!</li>
<li>If there are action items identified, note them and be sure to assigned to an owner.</li>
<li>Always come prepared with any documentation or diagrams to facilitate the conversation.  (For example, I don&#8217;t need to spend 15 minutes watching you draw our existing network diagram on the white board.  This is what printers and projectors are for.)</li>
<li>Stay on point.  It is easy to lose focus and have attendees push discussion onto something unrelated to the objectives.  Table any off topic discussion and move on.</li>
<li>Limit the attendees to only those people required.  It is very difficult to keep everyone on the same page when there too many people in the discussion.  (Keep in mind that presentations can have lot of people, however presentations are not meetings!)</li>
<li>Lastly, improve every meeting.  After the meeting think about how the meeting went and how you can make improvements.</li>
</ol>
<p>What tips do you recommend to make a meeting more effective?</p>
]]></content:encoded>
			<wfw:commentRss>http://techopener.com/blog/2009/10/effective-meetings-101/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
