<?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"
	>
<channel>
	<title>Comments on: &#8220;Don&#8217;t pee in the pool,&#8221; one customer&#8217;s rollout strategy</title>
	<atom:link href="http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/</link>
	<description></description>
	<pubDate>Fri, 22 Aug 2008 02:37:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Go Big Always - Nike + Community = Leadership</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-889</link>
		<dc:creator>Go Big Always - Nike + Community = Leadership</dc:creator>
		<pubDate>Wed, 30 Apr 2008 13:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-889</guid>
		<description>[...] Since the last customer highlight was so popular and since Nike&#8217;s newest online community went live yesterday, I thought I&#8217;d share some of the kick-butt things that they&#8217;re doing. They are an unbelievably creative company that spends a huge amount of time engaging with their customers. Loic had already interviewed Michael Tchao (first video). I got a chance to do the same with Roberto Tagliabue (who also provided videos about how Nike puts on events for their community&#8217;s &#8220;super users&#8221; as well as a commercial they made highlighting their top community member). [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Since the last customer highlight was so popular and since Nike&#8217;s newest online community went live yesterday, I thought I&#8217;d share some of the kick-butt things that they&#8217;re doing. They are an unbelievably creative company that spends a huge amount of time engaging with their customers. Loic had already interviewed Michael Tchao (first video). I got a chance to do the same with Roberto Tagliabue (who also provided videos about how Nike puts on events for their community&#8217;s &#8220;super users&#8221; as well as a commercial they made highlighting their top community member). [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Kass</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-844</link>
		<dc:creator>Malcolm Kass</dc:creator>
		<pubDate>Wed, 23 Apr 2008 16:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-844</guid>
		<description>Good post, a little bit about what Gia Lyons had to say.  When Sabre Holdings (Travelocity) rolled out Cubeless, exec buy-in really wasn't the issue, or at least the "biggest" issue. Problems came in two different forms...

1.  Openness, in a way, can turn people off.  Where I am coming from is the inevitability of a small fraction of your employee base that will be so enamored with your networking product that they will overload  ti with, to be frank, crap content.   Granted, it not necessarily an HR problem, but for those to have legit business related questions, your product may not feel like the right "forum".  I guess "too slapstick" for a hardcore technical question. 

2. Bitch is fine.  Bitch, bitch, bitch, bitch is not.  Its a social networking turn off when there are individuals who bitch constantly in the community.  The community doesn't want to be social then, who wants to. 

FYI.  Magnets worked really well for us to spread the word about cubeless.</description>
		<content:encoded><![CDATA[<p>Good post, a little bit about what Gia Lyons had to say.  When Sabre Holdings (Travelocity) rolled out Cubeless, exec buy-in really wasn&#8217;t the issue, or at least the &#8220;biggest&#8221; issue. Problems came in two different forms&#8230;</p>
<p>1.  Openness, in a way, can turn people off.  Where I am coming from is the inevitability of a small fraction of your employee base that will be so enamored with your networking product that they will overload  ti with, to be frank, crap content.   Granted, it not necessarily an HR problem, but for those to have legit business related questions, your product may not feel like the right &#8220;forum&#8221;.  I guess &#8220;too slapstick&#8221; for a hardcore technical question. </p>
<p>2. Bitch is fine.  Bitch, bitch, bitch, bitch is not.  Its a social networking turn off when there are individuals who bitch constantly in the community.  The community doesn&#8217;t want to be social then, who wants to. </p>
<p>FYI.  Magnets worked really well for us to spread the word about cubeless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Effective Collaboration</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-835</link>
		<dc:creator>Effective Collaboration</dc:creator>
		<pubDate>Wed, 23 Apr 2008 09:14:01 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-835</guid>
		<description>&lt;strong&gt;Enterprise Collaboration and Virtual Teams Report (April 23, 2008)...&lt;/strong&gt;

The People Part of Enterprise Collaboration and Virtual Teams SearchCIO released a series of papers on planning an enterprise collaboration strategy, including "Getting Everyone on Board", "Improving Productivity" and "Tools and Technologies". Pa...</description>
		<content:encoded><![CDATA[<p><strong>Enterprise Collaboration and Virtual Teams Report (April 23, 2008)&#8230;</strong></p>
<p>The People Part of Enterprise Collaboration and Virtual Teams SearchCIO released a series of papers on planning an enterprise collaboration strategy, including &#8220;Getting Everyone on Board&#8221;, &#8220;Improving Productivity&#8221; and &#8220;Tools and Technologies&#8221;. Pa&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-809</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 21 Apr 2008 17:29:56 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-809</guid>
		<description>Sam,
This is a great example of a well planned roll out. What a contrast to the top down, "Use this tool!" roll outs that are still common.

Thank you for sharing this.</description>
		<content:encoded><![CDATA[<p>Sam,<br />
This is a great example of a well planned roll out. What a contrast to the top down, &#8220;Use this tool!&#8221; roll outs that are still common.</p>
<p>Thank you for sharing this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Murgel</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-800</link>
		<dc:creator>Sarah Murgel</dc:creator>
		<pubDate>Fri, 18 Apr 2008 16:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-800</guid>
		<description>I was part of this initial project team and cannot agree more with Chuck Hollis -- it was the passion, focus and involvement of the team with the user that made it successful. Congratulations, guys! Great job. I'm proud.</description>
		<content:encoded><![CDATA[<p>I was part of this initial project team and cannot agree more with Chuck Hollis &#8212; it was the passion, focus and involvement of the team with the user that made it successful. Congratulations, guys! Great job. I&#8217;m proud.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Hollis</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-760</link>
		<dc:creator>Chuck Hollis</dc:creator>
		<pubDate>Thu, 17 Apr 2008 13:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-760</guid>
		<description>I love all of this.  And Gia's tips are really good.

So, one thing is in common for all of these successful internal rollouts: a core of very passionate and very talented people who are committed to making it happen; not because they have to, but because they want to.

I can't see any of this stuff working without that important ingredient.

Thanks for sharing, Sam!  I wonder where the "pool" analogy came from?  ;-)</description>
		<content:encoded><![CDATA[<p>I love all of this.  And Gia&#8217;s tips are really good.</p>
<p>So, one thing is in common for all of these successful internal rollouts: a core of very passionate and very talented people who are committed to making it happen; not because they have to, but because they want to.</p>
<p>I can&#8217;t see any of this stuff working without that important ingredient.</p>
<p>Thanks for sharing, Sam!  I wonder where the &#8220;pool&#8221; analogy came from?  <img src='http://gobigalways.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-04-16 at John Bowersox</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-754</link>
		<dc:creator>links for 2008-04-16 at John Bowersox</dc:creator>
		<pubDate>Wed, 16 Apr 2008 23:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-754</guid>
		<description>[...] Go Big Always - “Don’t pee in the pool,” one customer’s rollout strategy (tags: enterprise2.0 blogs collaboration community management socialmedia socialnetworking toread) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Go Big Always - “Don’t pee in the pool,” one customer’s rollout strategy (tags: enterprise2.0 blogs collaboration community management socialmedia socialnetworking toread) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dianne Conley</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-753</link>
		<dc:creator>Dianne Conley</dc:creator>
		<pubDate>Wed, 16 Apr 2008 21:45:22 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-753</guid>
		<description>Great stuff...thanks for sharing.  We're just beginning to build an external Clearspace community and have been struggling to find an apt metaphor of our own, let alone integrate it into our roll-out strategy.  This case study gives us a fabulous example on how to do it right.</description>
		<content:encoded><![CDATA[<p>Great stuff&#8230;thanks for sharing.  We&#8217;re just beginning to build an external Clearspace community and have been struggling to find an apt metaphor of our own, let alone integrate it into our roll-out strategy.  This case study gives us a fabulous example on how to do it right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Irregular Enterprise mobile edition</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-750</link>
		<dc:creator>Irregular Enterprise mobile edition</dc:creator>
		<pubDate>Wed, 16 Apr 2008 13:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-750</guid>
		<description>[...] Rather than repeat the latest story, I&#8217;ll simply point to the provocatively titled Don&#8217;t pee in the pool post which sets out some of the tactics a client operated to implement his company&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Rather than repeat the latest story, I&#8217;ll simply point to the provocatively titled Don&#8217;t pee in the pool post which sets out some of the tactics a client operated to implement his company&#8217;s [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-745</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Wed, 16 Apr 2008 03:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://gobigalways.com/dont-pee-in-the-pool-one-customers-rollout-strategy/#comment-745</guid>
		<description>@Dan We got lucky when we started because nobody cared about what we were doing. We were left alone, there were very few pesky questions from question-people.  Today if you try anything social everyone is interested.

Our community is external with a lot of participation from internal people.  It's at the middle-aged state where decisions made years ago have locked us into many, how should I put it, non-optimal patterns.  On the  other hand it's still thriving and has launched more than a few careers within the company.  I guess we're still at the bleeding edge but for us it's what to do with an existing community that could be so much more.  There isn't much research for that, it's all around how to start a community.

Blow it up? Sure I'd be game for that a lot of days. Where's the dynamite?

@Gia or Carl Spackler.</description>
		<content:encoded><![CDATA[<p>@Dan We got lucky when we started because nobody cared about what we were doing. We were left alone, there were very few pesky questions from question-people.  Today if you try anything social everyone is interested.</p>
<p>Our community is external with a lot of participation from internal people.  It&#8217;s at the middle-aged state where decisions made years ago have locked us into many, how should I put it, non-optimal patterns.  On the  other hand it&#8217;s still thriving and has launched more than a few careers within the company.  I guess we&#8217;re still at the bleeding edge but for us it&#8217;s what to do with an existing community that could be so much more.  There isn&#8217;t much research for that, it&#8217;s all around how to start a community.</p>
<p>Blow it up? Sure I&#8217;d be game for that a lot of days. Where&#8217;s the dynamite?</p>
<p>@Gia or Carl Spackler.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.286 seconds -->
