<?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>minding the gaps &#187; GTD</title>
	<atom:link href="http://www.mindingthegaps.com/blog/category/gtd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mindingthegaps.com/blog</link>
	<description>The discovery, acceptance &#38; management of life&#039;s gaps</description>
	<lastBuildDate>Tue, 31 Aug 2010 12:09:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>GREAT Meetings &#8211; Project Team Principles</title>
		<link>http://www.mindingthegaps.com/blog/2010/07/31/great-meetings-project-team-principles/</link>
		<comments>http://www.mindingthegaps.com/blog/2010/07/31/great-meetings-project-team-principles/#comments</comments>
		<pubDate>Sun, 01 Aug 2010 03:20:45 +0000</pubDate>
		<dc:creator>Russ Leseberg</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[gaps]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[PMO]]></category>
		<category><![CDATA[PMP]]></category>

		<guid isPermaLink="false">http://www.mindingthegaps.com/blog/?p=2392</guid>
		<description><![CDATA[GREAT Meetings happen when everyone understands what is expected of them and other team members. GREAT stands for Goals, Roles, Expectations, Accountability and Timing.
Goals &#8211; Knowledge of a project’s overarching goals provides the context for understanding the specific objectives/ tasks of individual team members. All team members should understand and be able to communicate the [...]]]></description>
			<content:encoded><![CDATA[<p><strong>GREAT</strong> Meetings happen when everyone understands what is expected of them and other team members. <strong>GREAT</strong> stands for <strong>Goals, Roles, Expectations, Accountability and Timing</strong>.</p>
<p><strong>Goals</strong> &#8211; Knowledge of a project’s overarching goals provides the context for understanding the specific objectives/ tasks of individual team members. All team members should understand and be able to communicate the driving business needs and the project&#8217;s expected outcome. Those leading group interaction/ meetings should state the specific goals of the meeting, phone conference or other team communication. It&#8217;s everyones&#8217; job to maintain focus on the goals of a particular meeting, thus respecting each others time.</p>
<p><strong>Roles</strong> &#8211; Every team member needs to understand his/ her individual role and specific responsibilities. Teams are interdependent by design, heavily reliant on each member fulfilling their respective roles. Teams are intentionally comprised of individuals with unique skills, expertise and differing perspectives. As such, it is not possible for every team member to fully understand everyone&#8217;s role and responsibilities. However, members should have a basic comprehension of the duties and activities of others, especially where it directly impacts them.</p>
<p><strong>Expectations</strong> &#8211; Communicating expectations is just as important within a project team as it is with the customer. Every team member not only has the right to know what is expected of them, but the personal obligation to find out. Once an individual learns he or she is assigned to a project, he or she inherits the responsibility of learning what is expected&#8230; not waiting to be told.</p>
<p><strong>Accountability</strong> &#8211; Accountability is the backbone of teamwork and trust. Teams where each member meets his/ her personal project responsibilities enjoy a greater degree of mutual success than those who can’t count on each other to follow through.</p>
<p><strong>Timing</strong> &#8211; In order to coordinate project activities and ensure milestones are met, team members must be personally committed to the team and deliver on their individual deadlines.</p>
<p><strong>How to leverage the GREAT acronym&#8230;</strong><br />
Use the <strong>GREAT</strong> acronym, during meetings, phone/ video conferences, or other group discussions, to keep the focus on&#8230;<br />
<strong>G. (Goals) &#8230; </strong>the goals of the particular discussion as well as the goals of the overall project.<br />
<strong>R. (Roles) &#8230; </strong>the individual roles of team members.<br />
<strong>E. (Expectations) &#8230; </strong>everyone understanding what is expected of them.<br />
<strong>A. (Accountability) &#8230; </strong>what each team member is accountable for, the current status and ongoing progress reporting.<br />
<strong>T. (Timing) &#8230; </strong>task deadlines and the individual commitment to their completion.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mindingthegaps.com/blog/2010/07/31/great-meetings-project-team-principles/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Countdown to iPad – Teammate (Use Case 12)</title>
		<link>http://www.mindingthegaps.com/blog/2010/02/26/countdown-to-ipad-%e2%80%93-teammate-use-case-12/</link>
		<comments>http://www.mindingthegaps.com/blog/2010/02/26/countdown-to-ipad-%e2%80%93-teammate-use-case-12/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 13:40:49 +0000</pubDate>
		<dc:creator>Russ Leseberg</dc:creator>
				<category><![CDATA[GTD]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[gaps]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[tech]]></category>
		<category><![CDATA[use case]]></category>

		<guid isPermaLink="false">http://www.mindingthegaps.com/blog/?p=902</guid>
		<description><![CDATA[Another day&#8230; another meeting. Reach for your smart phone to take notes and get the evil eye. Go for your laptop and you&#8217;re likely to get the same. What&#8217;s a paper liberated/tech devotee to do? Well, pad-based note taking, the long accepted darling of meetings, is about to get a make-over. Meet iPad, your newest [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Another day&#8230; another meeting</strong>. Reach for your smart phone to take notes and get the evil eye. Go for your laptop and you&#8217;re likely to get the same. What&#8217;s a paper liberated/tech devotee to do? Well, pad-based note taking, the long accepted darling of meetings, is about to get a make-over. Meet <strong>iPad</strong>, your newest <strong>teammate</strong>. <strong>iPad is the politically correct meeting tech</strong>. iPad is just the right size, it&#8217;s always ready, easy to carry, and your notes are always with you. <strong>iPad</strong>, we&#8217;ve got to <strong>START meeting like this</strong>.</p>
<div id="attachment_901" class="wp-caption alignnone" style="width: 522px"><img src="http://www.mindingthegaps.com/blog/wp-content/uploads/2010/02/meetingPad_wr.jpg" alt="iPad shown with Pogo Sketch" title="meetingPad_wr" width="512" height="384" class="size-full wp-image-901" /><p class="wp-caption-text">iPad shown with Pogo Sketch</p></div>
<p><strong>iPad: </strong>more stares of admiration / less stares of contempt. </p>
<hr />
<p>We have many iPad use case scenarios queued up, but could always use more. Please comment and share your iPad ideas below.</p>
<hr />
<p>iPad &#8211; Copyright © 2010 Apple Inc. (<a href="http://www.apple.com">www.apple.com</a>)</p>
<p>Pogo Sketch &#8211; Ten One Design (<a href="http://www.tenonedesign.com">www.tenonedesign.com</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mindingthegaps.com/blog/2010/02/26/countdown-to-ipad-%e2%80%93-teammate-use-case-12/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Team Principles &#8211; Minding Team Gaps</title>
		<link>http://www.mindingthegaps.com/blog/2010/01/31/minding-team-gaps/</link>
		<comments>http://www.mindingthegaps.com/blog/2010/01/31/minding-team-gaps/#comments</comments>
		<pubDate>Mon, 01 Feb 2010 03:57:05 +0000</pubDate>
		<dc:creator>Russ Leseberg</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[gaps]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[PMO]]></category>
		<category><![CDATA[PMP]]></category>

		<guid isPermaLink="false">http://www.mindingthegaps.com/blog/?p=474</guid>
		<description><![CDATA[Projects succeed when teams succeed. Successful teams share a congruent vision, pursue coordinated objectives, are bound by trust &#038; adhere to timeless principles.
Through years of managing projects I have identified 31 prompts to keep critical team principles at the forefront &#038; in focus. These reminders are presented in the form of six acronyms, keeping them [...]]]></description>
			<content:encoded><![CDATA[<p>Projects succeed when teams succeed. Successful teams share a congruent vision, pursue coordinated objectives, are bound by trust &#038; adhere to timeless principles.</p>
<p>Through years of managing projects I have identified 31 prompts to keep critical team principles at the forefront &#038; in focus. These reminders are presented in the form of six acronyms, keeping them easy to remember. The acronyms are: <strong>GREAT</strong>, <strong>FLAVOR</strong>, <strong>DREAM</strong>, <strong>ANSWER</strong>, <strong>SMART</strong> &#038; <strong>SAFE</strong>.</p>
<p><strong>G.R.E.A.T.</strong> (<strong>G</strong>oals, <strong>R</strong>oles, <strong>E</strong>xpectations, <strong>A</strong>ccountability &#038; <strong>T</strong>iming)<br />
GREAT Interactions/meetings take place when everyone understands what is expected of them and others.</p>
<p><strong>F.L.A.V.O.R.</strong> (<strong>F</strong>ollow, <strong>L</strong>ead, <strong>A</strong>ttitude, <strong>V</strong>alue, <strong>O</strong>wnership &#038; <strong>R</strong>espect)<br />
It is the personal responsibility of everyone to add FLAVOR to the team.</p>
<p><strong>D.R.E.A.M.</strong> (<strong>D</strong>ecision <strong>M</strong>akers, <strong>R</strong>epresentation, <strong>E</strong>xpertise, <strong>A</strong>bility &#038; <strong>M</strong>anageability)<br />
When building project teams, remember that DREAM Teams are winning teams.</p>
<p><strong>A.N.S.W.E.R.</strong> (<strong>A</strong>ccurate, <strong>N</strong>ecessary, <strong>S</strong>uccinct, <strong>W</strong>ritten, <strong>E</strong>ffective &#038; <strong>R</strong>esponsive)<br />
ANSWER serves as a guide toward successful communication.</p>
<p><strong>S.M.A.R.T.</strong> (<strong>S</strong>pecific, <strong>M</strong>easurable, <strong>A</strong>greed, <strong>R</strong>ealistic &#038; <strong>T</strong>ime-based)<br />
Efficient project management begins with developing SMART Objectives.</p>
<p><strong>S.A.F.E.</strong> (<strong>S</strong>imple, <strong>A</strong>ffordable, <strong>F</strong>lexible &#038; <strong>E</strong>fficient)<br />
Provide SAFE solutions to internal &#038; external customers.</p>
<p>In subsequent posts I will delve deeper into each acronym. Until then, I leave you with a memory key. Committing the silly phrase &#8220;<strong>GREAT</strong> Interactions add <strong>FLAVOR</strong>, while <strong>DREAM</strong> Teams <strong>ANSWER</strong> Communications, &#038; <strong>SMART</strong> Objectives lead to <strong>SAFE</strong> Solutions,&#8221; to memory will help you recall these important team principles.<br />
____________________________________________<br />
I first saw the S.M.A.R.T. acronym in use by various entities on the web. All other acronyms presented herein are original creations.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mindingthegaps.com/blog/2010/01/31/minding-team-gaps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
