<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for The GroupSwim Diving Board</title>
	<atom:link href="http://blog.groupswim.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.groupswim.com</link>
	<description>Thoughts on Collaboration, Enterprise 2.0, and SaaS</description>
	<lastBuildDate>Wed, 06 Jan 2010 14:38:35 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on GroupSwim is now part of salesforce.com by bernard lunn</title>
		<link>http://blog.groupswim.com/2009/12/11/groupswim-is-now-part-of-salesforce-com/#comment-519</link>
		<dc:creator>bernard lunn</dc:creator>
		<pubDate>Wed, 06 Jan 2010 14:38:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=807#comment-519</guid>
		<description>Jason, just saw this news! Congrats. Bernard</description>
		<content:encoded><![CDATA[<p>Jason, just saw this news! Congrats. Bernard</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GroupSwim is now part of salesforce.com by Thorsten Arndt</title>
		<link>http://blog.groupswim.com/2009/12/11/groupswim-is-now-part-of-salesforce-com/#comment-513</link>
		<dc:creator>Thorsten Arndt</dc:creator>
		<pubDate>Sat, 12 Dec 2009 11:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=807#comment-513</guid>
		<description>Guys,

Congratulations. You deserve this. Great product, and probably the best customer service I&#039;ve ever experienced. I almost had the feeling that you were consultants working for me, instead of me being one of many customers.

Thorsten</description>
		<content:encoded><![CDATA[<p>Guys,</p>
<p>Congratulations. You deserve this. Great product, and probably the best customer service I&#8217;ve ever experienced. I almost had the feeling that you were consultants working for me, instead of me being one of many customers.</p>
<p>Thorsten</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Change Just One Thing by Jade</title>
		<link>http://blog.groupswim.com/2009/10/07/change-just-one-thing/#comment-506</link>
		<dc:creator>Jade</dc:creator>
		<pubDate>Thu, 19 Nov 2009 23:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=804#comment-506</guid>
		<description>Interesting article. Although I would suggest changing it to &quot;ask questions in person.&quot; Even as a copywriter myself it is amazing the amount of miscommunication that flies back and forth over written questions and answers. I find that a simple phone call can clear up hours of confusing threads. Just a thought!</description>
		<content:encoded><![CDATA[<p>Interesting article. Although I would suggest changing it to &#8220;ask questions in person.&#8221; Even as a copywriter myself it is amazing the amount of miscommunication that flies back and forth over written questions and answers. I find that a simple phone call can clear up hours of confusing threads. Just a thought!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Change Just One Thing by Christian DE NEEF</title>
		<link>http://blog.groupswim.com/2009/10/07/change-just-one-thing/#comment-505</link>
		<dc:creator>Christian DE NEEF</dc:creator>
		<pubDate>Thu, 12 Nov 2009 07:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=804#comment-505</guid>
		<description>One argument in favor of this approach is that (i) it seems simple enough to put in practice and actually deliver tangible results, and (ii) it allows for measuring the impact of that particular change that we focus on.  Indeed, if we change many things at the same time, then how do we know which change has what impact?  

However, something seems wrong.  It certainly goes against one of my consulting principles, which is that change has to be holistic and driven across multiple perspectives at once to be effective.  The model I most often use in change management is Leavitt&#039;s Diamond, a balancing act in which four variables - technology, organization, processes and people - must be included in any enterprise change.  Indeed, what I see most often in my practice, is that companies change only one single thing (e.g., introduce new technology) and don&#039;t adapt the other dimensions to the change (don&#039;t train their people, adapt business processes accordingly, provide support organization, etc.).  Most often, the benefits from that single change will then not be reaped.  More significantly, the change may simply be rejected by the organization.  


@cdn</description>
		<content:encoded><![CDATA[<p>One argument in favor of this approach is that (i) it seems simple enough to put in practice and actually deliver tangible results, and (ii) it allows for measuring the impact of that particular change that we focus on.  Indeed, if we change many things at the same time, then how do we know which change has what impact?  </p>
<p>However, something seems wrong.  It certainly goes against one of my consulting principles, which is that change has to be holistic and driven across multiple perspectives at once to be effective.  The model I most often use in change management is Leavitt&#8217;s Diamond, a balancing act in which four variables &#8211; technology, organization, processes and people &#8211; must be included in any enterprise change.  Indeed, what I see most often in my practice, is that companies change only one single thing (e.g., introduce new technology) and don&#8217;t adapt the other dimensions to the change (don&#8217;t train their people, adapt business processes accordingly, provide support organization, etc.).  Most often, the benefits from that single change will then not be reaped.  More significantly, the change may simply be rejected by the organization.  </p>
<p>@cdn</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Change Just One Thing by MILIARDERR</title>
		<link>http://blog.groupswim.com/2009/10/07/change-just-one-thing/#comment-501</link>
		<dc:creator>MILIARDERR</dc:creator>
		<pubDate>Tue, 03 Nov 2009 19:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=804#comment-501</guid>
		<description>&quot;Use the wiki page for all teams to report on progress 
meeting is moving forward &quot; 
Of course you can use the wiki there are even special services to work in a team. The main thing to get people to change their approach to work-it is very difficult!</description>
		<content:encoded><![CDATA[<p>&#8220;Use the wiki page for all teams to report on progress<br />
meeting is moving forward &#8221;<br />
Of course you can use the wiki there are even special services to work in a team. The main thing to get people to change their approach to work-it is very difficult!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 7 Habits of Highly Ineffective People by Ashley</title>
		<link>http://blog.groupswim.com/2009/08/11/7-habits-of-highly-ineffective-people/#comment-488</link>
		<dc:creator>Ashley</dc:creator>
		<pubDate>Fri, 18 Sep 2009 23:59:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=777#comment-488</guid>
		<description>Very amusing!</description>
		<content:encoded><![CDATA[<p>Very amusing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 7 Habits of Highly Ineffective People by Today&#8217;s Startup Updates &#8211; August 12 &#124; CenterNetworks</title>
		<link>http://blog.groupswim.com/2009/08/11/7-habits-of-highly-ineffective-people/#comment-472</link>
		<dc:creator>Today&#8217;s Startup Updates &#8211; August 12 &#124; CenterNetworks</dc:creator>
		<pubDate>Wed, 12 Aug 2009 11:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=777#comment-472</guid>
		<description>[...] Very readable post about the 7 highly ineffective habits &#8211; GroupSwim [...]</description>
		<content:encoded><![CDATA[<p>[...] Very readable post about the 7 highly ineffective habits &#8211; GroupSwim [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 7 Habits of Highly Ineffective People by Peter Luke Baptiste</title>
		<link>http://blog.groupswim.com/2009/08/11/7-habits-of-highly-ineffective-people/#comment-470</link>
		<dc:creator>Peter Luke Baptiste</dc:creator>
		<pubDate>Wed, 12 Aug 2009 00:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=777#comment-470</guid>
		<description>Nice tricks . thanks for sharing!</description>
		<content:encoded><![CDATA[<p>Nice tricks . thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Use Wiki Pages for Project Management by Tackling Project Task Management - Powerful Project Planning &#124; Self Help Blog</title>
		<link>http://blog.groupswim.com/2009/05/13/use-wiki-pages-for-project-management/#comment-390</link>
		<dc:creator>Tackling Project Task Management - Powerful Project Planning &#124; Self Help Blog</dc:creator>
		<pubDate>Sat, 16 May 2009 08:43:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=701#comment-390</guid>
		<description>[...] Use Wiki Pages for Project Management « The GroupSwim Diving Board [...]</description>
		<content:encoded><![CDATA[<p>[...] Use Wiki Pages for Project Management « The GroupSwim Diving Board [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Use Wiki Pages for Project Management by Scott</title>
		<link>http://blog.groupswim.com/2009/05/13/use-wiki-pages-for-project-management/#comment-387</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Thu, 14 May 2009 17:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.groupswim.com/?p=701#comment-387</guid>
		<description>Tasty!</description>
		<content:encoded><![CDATA[<p>Tasty!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
