<?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>Sun, 01 Jan 2012 02:07:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>ANSWER Communication(s) &#8211; Project Team Principles</title>
		<link>http://www.mindingthegaps.com/blog/2011/02/21/answer-communications-project-team-principles/</link>
		<comments>http://www.mindingthegaps.com/blog/2011/02/21/answer-communications-project-team-principles/#comments</comments>
		<pubDate>Mon, 21 Feb 2011 23:27:40 +0000</pubDate>
		<dc:creator>Russ Leseberg</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[gaps]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Personal Responsibility]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[PMO]]></category>
		<category><![CDATA[PMP]]></category>

		<guid isPermaLink="false">http://www.mindingthegaps.com/blog/?p=2651</guid>
		<description><![CDATA[The acronym ANSWER serves as a guide to successful communication. ANSWER stands for Accurate, Necessary, Succinct, Written, Effective and Responsive. Accurate &#8211; Accurate information is critical to the success of any endeavor. When providing information, verify the source and the data. It is better to have no data than bad data, as inaccuracy leads to [...]]]></description>
			<content:encoded><![CDATA[<p>The acronym <strong>ANSWER</strong> serves as <strong>a guide to successful communication</strong>. <strong>ANSWER</strong> stands for <strong>Accurate, Necessary, Succinct, Written, Effective and Responsive</strong>.</p>
<p><strong>Accurate</strong> &#8211; Accurate information is critical to the success of any endeavor. When providing information, verify the source and the data. It is better to have no data than bad data, as inaccuracy leads to waste and frustration. When forced to guess, estimate or provide other “less-than-precise” information, identify it as such.</p>
<p>Though often overlooked/avoided&#8230; effective project communication requires us to accurately document our activities and progress. The entire team benefits when each member lives the mantra, “Do what you say and say what you do.”</p>
<p><strong>Necessary</strong> &#8211; I have often heard it said, “You cannot over-communicate.” Though I understand the statement&#8217;s intent, I must disagree. Anyone who has sat through countless unproductive meetings or digs out daily from under a pile of e-mail knows over-communication is possible. Though an often over-looked criteria, simply ensuring your communications are necessary saves time and frustration. If it doesn&#8217;t bring value, don&#8217;t say/send it.</p>
<p><strong>Succinct</strong> &#8211; An economy of words doesn’t simply save time, it eliminates the necessity of sorting the needle of importance from a haystack of trivia. Keep all communication short and concise.</p>
<p><strong>Written</strong> &#8211; If it is worth saying, it is worth writing. Documenting specifications, plans, procedures, etc., facilitates understanding today and provides confirmation tomorrow.</p>
<p><strong>Effective</strong> &#8211; A message sent is only as useful as the message received. Creating an effective communiqué requires a full understanding of the objective and the audience. E-mail, reports, charts, or information in any form, are only effective when concepts are easily understood and can be quickly acted upon.</p>
<p>Effective communication is an investment in mutual success&#8230; paying repeated dividends to the recipients; the team and the project. When a picture is truly “worth a thousand words,” let it do the talking. Never underestimate the power of shared vision- go to the effort of creating a chart or diagram. Even when our utilitarian mainstay, e-mail, is the most fitting form of communication, take time to choose your words carefully.</p>
<p><strong>Responsive</strong> &#8211; Good communicators are responsive communicators. A quick note letting the team know you got it is just as important as working on it. And when your task is complete&#8230; return and report.</p>
<p><strong>How to leverage the ANSWER acronym..</strong>.<br />
When communicating with others, use the <strong>ANSWER</strong> acronym. Let it remind you that project communication&#8230;<br />
<strong>A. (Accurate) &#8230;</strong> must be accurate.<br />
<strong>N. (Necessary) &#8230;</strong> adds value only when it is necessary.<br />
<strong>S. (Succinct) &#8230;</strong> should be succinct.<br />
<strong>W. (Written) &#8230;</strong> is most useful when written.<br />
<strong>E. (Effective) &#8230;</strong> is worth additional preparation to provide effective presentation.<br />
<strong>R. (Responsive) &#8230;</strong> should be responsive in content, form and timeliness.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mindingthegaps.com/blog/2011/02/21/answer-communications-project-team-principles/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DREAM Teams – Project Team Principles</title>
		<link>http://www.mindingthegaps.com/blog/2011/01/30/dream-teams-project-team-principles/</link>
		<comments>http://www.mindingthegaps.com/blog/2011/01/30/dream-teams-project-team-principles/#comments</comments>
		<pubDate>Mon, 31 Jan 2011 00:35:10 +0000</pubDate>
		<dc:creator>Russ Leseberg</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[gaps]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Personal Responsibility]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[PMO]]></category>
		<category><![CDATA[PMP]]></category>

		<guid isPermaLink="false">http://www.mindingthegaps.com/blog/?p=2617</guid>
		<description><![CDATA[When building project teams, remember that DREAM Teams are winning teams. DREAM stands for Decision Makers, Representation, Expertise, Ability and Manageability. Decision Makers &#8211; Involving decision makers (management) on project teams is essential, but projects represent additional burden on already limited schedules. Most decision makers understand the need for their participation and will embrace decision-point [...]]]></description>
			<content:encoded><![CDATA[<p>When building project teams, remember that <strong>DREAM Teams are winning teams</strong>. <strong>DREAM</strong> stands for <strong>Decision Makers, Representation, Expertise, Ability and Manageability</strong>.</p>
<p><strong>Decision Makers</strong> &#8211; Involving decision makers (management) on project teams is essential, but projects represent additional burden on already limited schedules. Most decision makers understand the need for their participation and will embrace decision-point activities when demands on their time are respected, planned for and efficiently coordinated with their other duties. In cases where management appoints a “decision delegate” [entrusting limited decision-making authority], it is imperative that all guidelines/parameters surrounding the extension of trust be followed implicitly. A project is not a license to assume/abuse authority. Any extended decision-making authority must be officially/openly expressed and outlined in the project documentation.</p>
<p><strong>Representation</strong> &#8211; Appropriate stakeholder representation is key to the success of any project. Project stakeholders include anyone affected, anyone responsible for people and/or areas affected, management and those charged with the completion of the project. Stakeholder representatives act as agents of all stakeholders and have a duty to ensure that the needs of the many are reflected in the activities of the few.</p>
<p><strong>Expertise</strong> &#8211; The inclusion of appropriate SMEs (subject matter experts) assures that the right knowledge, skills and expertise are brought to bear on project objectives/solutions.</p>
<p><strong>Ability</strong> &#8211; Project teams need members with the ability to carry out their individual tasks. A person’s ability is not only demonstrated by his or her talents and skills, but also his/ her “avail-ability.” For teams to perform successfully they need the opportunity and the “cap-ability”.</p>
<p><strong>Manageability</strong> &#8211; Project management is not possible if the team is not manageable. Limiting the size of project teams increases manageability and allows for more projects to proceed. Furthermore, managing how often, how long and how many team members are involved in each activity buys back valuable time, allowing more work to proceed simultaneously.</p>
<p><strong>How to leverage the DREAM acronym&#8230;</strong><br />
When assembling teams, ensure they have all the needed ingredients. A successful project <strong>DREAM</strong> Team&#8230;<br />
<strong>D. (Decision Makers) ..</strong>. includes the involvement of the appropriate decision makers or their delegates.<br />
<strong>R. (Representation) &#8230;</strong> has appropriate stakeholder representation.<br />
<strong>E. (Expertise)</strong> &#8230;has the needed expertise.<br />
<strong>A. (Ability) &#8230;</strong> consists of those with the ability to devote themselves to the team and the project.<br />
<strong>M. (Manageability) &#8230;</strong> is manageable when it is the right size with the right people in the right places.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mindingthegaps.com/blog/2011/01/30/dream-teams-project-team-principles/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Add FLAVOR &#8211; Project Team Principles</title>
		<link>http://www.mindingthegaps.com/blog/2010/12/31/add-flavor-project-team-principles/</link>
		<comments>http://www.mindingthegaps.com/blog/2010/12/31/add-flavor-project-team-principles/#comments</comments>
		<pubDate>Fri, 31 Dec 2010 22:56:46 +0000</pubDate>
		<dc:creator>Russ Leseberg</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[gaps]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Personal Responsibility]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[PMO]]></category>
		<category><![CDATA[PMP]]></category>

		<guid isPermaLink="false">http://www.mindingthegaps.com/blog/?p=2582</guid>
		<description><![CDATA[It is the personal responsibility of every project team member to add FLAVOR. FLAVOR stands for Follow, Lead, Attitude, Value, Ownership and Respect. Follow &#8211; A critical skill for all team members to master is that of following someone else’s lead. In project driven organizations, leadership roles can change from one meeting to the next. [...]]]></description>
			<content:encoded><![CDATA[<p>It is the personal responsibility of every project team member to <strong>add FLAVOR</strong>. <strong>FLAVOR</strong> stands for <strong>Follow, Lead, Attitude, Value, Ownership and Respect</strong>.</p>
<p><strong>Follow</strong> &#8211; A critical skill for all team members to master is that of following someone else’s lead. In project driven organizations, leadership roles can change from one meeting to the next. When someone else is leading, fully support him or her. <strong>Great leaders are first great followers</strong>.</p>
<p><strong>Lead</strong> &#8211; Everyone ends up in a leadership role at one time or another. When it is your turn, don’t be afraid to lead. When given the lead, treat your role and all team members with respect. When leading, you have the dual obligation of managing activities and resources efficiently while managing relationships respectfully.</p>
<p><strong>Attitude</strong> &#8211; The most important contribution anyone makes to the team is his or her attitude. You ultimately have to hold yourself accountable for a positive, cooperative, and success focused attitude. Before managing anything or anyone else, you must first be willing and able to manage your attitude.</p>
<p><strong>Value</strong> &#8211; Always add value. Bring it to your meetings, your projects, your solutions and ultimately your customers. In any given situation, be willing to ask, and ready to answer the question, “What value does my participation add?” Recognize and celebrate the value in others. Learn to measure and assess value within the context of the objective(s).</p>
<p><strong>Ownership</strong> &#8211; Take personal ownership for all you do. When given a task, stay with it. When ownership passes to someone else, don’t drop it, hand it off. Own your words, your actions, your attitude and your assignments.</p>
<p><strong>Respect</strong> &#8211; Everyone has the right to be respected, and the obligation to respect others. To be successful, those you serve and those you serve with need to be assured of your respect. Show it in your meetings, e-mails, after-hours discussions, etc. Respect each other’s ideas, time, abilities and responsibilities.</p>
<p><strong>How to leverage the FLAVOR acronym&#8230;</strong><br />
You begin to realize your full potential and what your contribution means to a team, when you recognize the power of individual choice. Choose to make a positive difference and let the <strong>FLAVOR</strong> acronym serve as a personal reminder&#8230;<br />
<strong>F. (Follow) &#8230; </strong>for you to follow when appropriate.<br />
<strong>L. (Lead) &#8230; </strong>for you to lead when appropriate.<br />
<strong>A. (Attitude) &#8230; </strong>that you and you alone are responsible for your attitude.<br />
<strong>V. (Value) &#8230;</strong> of the constant obligation of finding ways to bring value to the team and to the project.<br />
<strong>O. (Ownership) &#8230; </strong>to take personal ownership of assigned duties, deadlines and deliverables.<br />
<strong>R. (Respect) &#8230; </strong>to treat everyone with respect and ensure it is evident in all you say and do.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mindingthegaps.com/blog/2010/12/31/add-flavor-project-team-principles/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<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[gaps]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Teams]]></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 [...]]]></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[mobile]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Technology]]></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[gaps]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Teams]]></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 [...]]]></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>

