Comments on: 8 Tips for a Successful Social Intranet Pilot http://www.thoughtfarmer.com/blog/2009/08/26/intranet-pilot-tips/ Social Intranet Software: ThoughtFarmer is Turnkey, Microsoft Certified Thu, 09 Feb 2012 11:27:59 +0000 hourly 1 http://wordpress.org/?v= By: Google Wave, #hashtags, social Intranets and students in space | Customer Engagement Unit http://www.thoughtfarmer.com/blog/2009/08/26/intranet-pilot-tips/#comment-426 Google Wave, #hashtags, social Intranets and students in space | Customer Engagement Unit Thu, 08 Oct 2009 18:52:33 +0000 http://www.thoughtfarmer.com/?p=1120#comment-426 [...] 8 tips for a successful social Intranet pilot [...] [...] 8 tips for a successful social Intranet pilot [...]

]]> By: Library clips :: Community of Practice for Facilitators : pilot, adoption and participation :: September :: 2009 http://www.thoughtfarmer.com/blog/2009/08/26/intranet-pilot-tips/#comment-421 Library clips :: Community of Practice for Facilitators : pilot, adoption and participation :: September :: 2009 Mon, 14 Sep 2009 04:30:59 +0000 http://www.thoughtfarmer.com/?p=1120#comment-421 [...] late we have seen posts by folks at ThoughtFarmer and Socialtext on pilot/implementation methods. These are great posts and show the difference [...] [...] late we have seen posts by folks at ThoughtFarmer and Socialtext on pilot/implementation methods. These are great posts and show the difference [...]

]]> By: Chris McGrath http://www.thoughtfarmer.com/blog/2009/08/26/intranet-pilot-tips/#comment-394 Chris McGrath Tue, 01 Sep 2009 23:23:45 +0000 http://www.thoughtfarmer.com/?p=1120#comment-394 Thanks for weighing in, Kim. For the benefit of other readers, the "debate" I think Kim is referring to is Michael Idinopulos' response to this post, titled "<a href="http://michaeli.typepad.com/my_weblog/2009/08/enterprise-20-skip-the-pilot.html" rel="nofollow">Enterprise 2.0: Forget the pilot</a>" and his follow-up, "<a href="http://michaeli.typepad.com/my_weblog/2009/09/launching-at-scale-.html" rel="nofollow">Launch E2.0 Broad, Then Go Deep.</a>" Thanks for weighing in, Kim. For the benefit of other readers, the “debate” I think Kim is referring to is Michael Idinopulos’ response to this post, titled “Enterprise 2.0: Forget the pilot” and his follow-up, “Launch E2.0 Broad, Then Go Deep.“

]]> By: Kim Feraday http://www.thoughtfarmer.com/blog/2009/08/26/intranet-pilot-tips/#comment-393 Kim Feraday Tue, 01 Sep 2009 22:47:39 +0000 http://www.thoughtfarmer.com/?p=1120#comment-393 Interesting debate going on here. I think barnraising (#5) is a great idea particularly for community building. That (along with discovery services) will bridge the chasm between collective intelligence and collaborative intelligence. In the long run I believe community building will create stronger ties and more value (and faster) than large networks. Interesting debate going on here. I think barnraising (#5) is a great idea particularly for community building. That (along with discovery services) will bridge the chasm between collective intelligence and collaborative intelligence. In the long run I believe community building will create stronger ties and more value (and faster) than large networks.

]]> By: Chris http://www.thoughtfarmer.com/blog/2009/08/26/intranet-pilot-tips/#comment-384 Chris Wed, 26 Aug 2009 21:42:51 +0000 http://www.thoughtfarmer.com/?p=1120#comment-384 Thanks for that comment, Stewart! Good point. Thanks for that comment, Stewart! Good point.

]]> By: Stewart Mader http://www.thoughtfarmer.com/blog/2009/08/26/intranet-pilot-tips/#comment-383 Stewart Mader Wed, 26 Aug 2009 21:39:53 +0000 http://www.thoughtfarmer.com/?p=1120#comment-383 Chris, This is a great list. Regarding Point #7, bear in mind that a couple of assigned tasks are good, but make sure to let people in the pilot group come up with some of their own uses, and observe what works well. That becomes the basis for how you present the tool to the rest of the organization. People will be motivated by great storytelling about how the pilot group came up with an innovative use of the tool. And it's even better when members of the pilot group tell that story. Chris,
This is a great list. Regarding Point #7, bear in mind that a couple of assigned tasks are good, but make sure to let people in the pilot group come up with some of their own uses, and observe what works well. That becomes the basis for how you present the tool to the rest of the organization.

People will be motivated by great storytelling about how the pilot group came up with an innovative use of the tool. And it’s even better when members of the pilot group tell that story.

]]>