<?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>High Performance Leadership Training &#187; Team Effectiveness</title>
	<atom:link href="http://www.harveyrobbins.com/category/blog/team-effectiveness/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.harveyrobbins.com</link>
	<description>Harvey Robbins has created new tools and techniques for leadership skills and team development. Learned while working with the intelligence community, they have resulted in increased leadership capabilities and effective outcomes.</description>
	<lastBuildDate>Wed, 25 Mar 2009 05:24:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Team Effectiveness: The Hazards of Collaboration</title>
		<link>http://www.harveyrobbins.com/2007/07/08/team-effectiveness-the-hazards-of-collaboration/</link>
		<comments>http://www.harveyrobbins.com/2007/07/08/team-effectiveness-the-hazards-of-collaboration/#comments</comments>
		<pubDate>Sun, 08 Jul 2007 15:10:39 +0000</pubDate>
		<dc:creator>harveyrobbins</dc:creator>
				<category><![CDATA[Team Effectiveness]]></category>

		<guid isPermaLink="false">http://www.harveyrobbins.com/2007/07/08/team-effectiveness-the-hazards-of-collaboration/</guid>
		<description><![CDATA[If competition is &#8220;bad,&#8221; then collaboration must always be good, right?
Wrong. Pure collaboration is as problematic as pure competition. Each has its purposes. But each, practiced to the exclusion of the other, leads to collapse.
Unabated competition, like a Panzer division rolling over Poland, creates a spirit of over-the-top, scorched-earth absolutism &#8212; legitimizing whatever means result [...]]]></description>
			<content:encoded><![CDATA[<p class="dropcap-first"><img vspace="2" align="left" src="http://www.harveyrobbins.com/wp-content/uploads/2007/08/man_one.jpg" hspace="4" alt="man_one.jpg" title="man_one.jpg" />If competition is &#8220;bad,&#8221; then collaboration must always be good, right?</p>
<p>Wrong. Pure collaboration is as problematic as pure competition. Each has its purposes. But each, practiced to the exclusion of the other, leads to collapse.</p>
<p>Unabated competition, like a Panzer division rolling over Poland, creates a spirit of over-the-top, scorched-earth absolutism &#8212; legitimizing whatever means result in victory:  treachery, deceit, corruption, murder.</p>
<p>Unabated collaboration is also problematic. It is the nemesis of individuality, progress, diversity, and change.</p>
<p>Here are some of the hallmarks of supercollaboration:</p>
<p><strong>1. Sameness</strong> &#8211; Overly collaborative teams adopt rigid standards and impose them on themselves, foreclosing creative deviation.</p>
<p><strong>2. Groupthink</strong> &#8211; This leads to purges of perceived outsiders, and stultification of the ideas of insiders.</p>
<p><strong>3. Blurriness</strong> &#8211; Too much democracy leads to mush.  When everyone has full and equal input into a process, you can bet that process will lack focus.</p>
<p><strong>4. Slowness</strong> &#8211; Consensus doesn&#8217;t &#8220;snap to&#8221; the way intimidated agreement does.  It is a slow ooze, and teams lose momentum waiting for the ooze to arrive.</p>
<p><strong>5. Leaderlessness</strong> &#8211; When everyone is encouraged to lead, the end result often is that no one does.</p>
<p><strong>6. Defenselessness</strong> &#8211; When everyone knows everything, because sharing is so important, there is no confidentiality, and there are no firewalls.  Some teams become so intimate and sensitive with one another that they can&#8217;t function among outsiders.</p>
<p><strong>7. Interiority</strong> &#8211; Teams who work too long together have a way of becoming cross-eyed over time, focusing on subjects of interest exclusively to the group.</p>
<p><strong>8. Mercilessness</strong> &#8211; &#8220;The many are stronger than the one&#8221;, is the motto of supercollaboration.  It is also the motto of fascism.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.harveyrobbins.com/2007/07/08/team-effectiveness-the-hazards-of-collaboration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Team of One</title>
		<link>http://www.harveyrobbins.com/2007/05/06/the-team-of-one/</link>
		<comments>http://www.harveyrobbins.com/2007/05/06/the-team-of-one/#comments</comments>
		<pubDate>Sun, 06 May 2007 07:35:27 +0000</pubDate>
		<dc:creator>harveyrobbins</dc:creator>
				<category><![CDATA[Team Effectiveness]]></category>

		<guid isPermaLink="false">http://www.harveyrobbins.com/2007/05/06/the-team-of-one/</guid>
		<description><![CDATA[If teams mustn&#8217;t be too big, how small can they be before they stop being teams?
We define a team as being two persons or more. But it may be useful, as you sort through the people available to you, to consider &#8220;the team of one.&#8221;
People think we&#8217;re joking when we talk about teams on one [...]]]></description>
			<content:encoded><![CDATA[<p class="dropcap-first"><img vspace="2" align="left" src="http://www.harveyrobbins.com/wp-content/uploads/2007/09/teamofone.jpg" hspace="4" alt="teamofone.jpg" title="teamofone.jpg" />If teams mustn&#8217;t be too big, how small can they be before they stop being teams?</p>
<p>We define a team as being two persons or more. But it may be useful, as you sort through the people available to you, to consider &#8220;the team of one.&#8221;</p>
<p>People think we&#8217;re joking when we talk about teams on one (&#8221;Why would you call a person a team?&#8221;) but we&#8217;re not.</p>
<p>A team of one is a virtual team, a single person with lots of diverse expertise treated by others as a separate team.</p>
<p>In complex organizations, it&#8217;s very common for teams to interact. A new product team, for instance, will have dealings with the design team down the hall. They&#8217;ll get input from another team in finance, and another team in marketing.</p>
<p>Usually these teams have a number of people on them. Occasionally, though, the connection is a single person. When this happens, it is good team politics to treat that person just like a bona fide team. You extend him or her the courtesy you would extend a group. Just because the team is a singleton does not allow you to go on a blaming rampage.</p>
<p>Meanwhile, contemplate the beauty of the team of one. It means that instead of putting several people from different functions on the team, the team&#8217;s diversity is integrated in a single person. Think of the arguments that never happen. Think of the handoffs that never take place. Think of the rapidity with which the team gets through the storming phase.</p>
<p>Diversity of knowledge is the reason for teams. But the age of the corporate specialist is yielding to the age of the one-man-band &#8212; technology driven, entrepreneurial jacks of all trades.</p>
<p>A team of one is so much faster, and is much more unambiguous than a team of more than one.</p>
<p>A team of one is also a splendid way to outplace a team member who doesn&#8217;t work well on a close, daily basis with your team, but whose knowledge remains valuable &#8211; or someone who just doesn&#8217;t want to belong to you. Simply take the individual out of the team box, draw a dotted line to a box that is all his own, and poof, you have a team of one serving as a resource to the team. No muss, no fuss, and everyone is happy.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.harveyrobbins.com/2007/05/06/the-team-of-one/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>


