<?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: Confessing a dirty little secret</title>
	<atom:link href="http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret/feed" rel="self" type="application/rss+xml" />
	<link>http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret</link>
	<description>Picking out patterns in the chaos</description>
	<pubDate>Mon, 21 May 2012 13:37:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: New Media Mania &#187; Blog Archive &#187; Ignorance is Not Bliss: People and Processes in KM</title>
		<link>http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-3724</link>
		<dc:creator>New Media Mania &#187; Blog Archive &#187; Ignorance is Not Bliss: People and Processes in KM</dc:creator>
		<pubDate>Mon, 01 Dec 2008 03:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-3724</guid>
		<description>[...] Charman-Anderson, Suw; “Confessing a Dirty Little Secret”; http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret [...]</description>
		<content:encoded><![CDATA[<p>[...] Charman-Anderson, Suw; “Confessing a Dirty Little Secret”; <a href="http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret" rel="nofollow">http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Strange Attractor &#187; Blog Archive &#187; An adoption strategy for social software in enterprise</title>
		<link>http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-3209</link>
		<dc:creator>Strange Attractor &#187; Blog Archive &#187; An adoption strategy for social software in enterprise</dc:creator>
		<pubDate>Wed, 08 Oct 2008 09:47:17 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-3209</guid>
		<description>[...] UPDATE: I don&#8217;t believe that supernodes are key anymore. I do believe that oft-ignored groups who are not traditionally thought of as influential, such as PAs, can in sometimes be crucial to an adoption strategy. But it&#8217;s far more important to focus on groups who share aims, actions, and information and who show existing enthusiasm for change and learning new stuff. This post explains in more detail why I changed my mind. [...]</description>
		<content:encoded><![CDATA[<p>[...] UPDATE: I don&#8217;t believe that supernodes are key anymore. I do believe that oft-ignored groups who are not traditionally thought of as influential, such as PAs, can in sometimes be crucial to an adoption strategy. But it&#8217;s far more important to focus on groups who share aims, actions, and information and who show existing enthusiasm for change and learning new stuff. This post explains in more detail why I changed my mind. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-2850</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Wed, 30 Apr 2008 15:11:23 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-2850</guid>
		<description>Have you seen this site where people confess their sins online, anonymously? http://iconfessmyself.blogspot.com
</description>
		<content:encoded><![CDATA[<p>Have you seen this site where people confess their sins online, anonymously? <a href="http://iconfessmyself.blogspot.com" rel="nofollow">http://iconfessmyself.blogspot.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Ross</title>
		<link>http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-2849</link>
		<dc:creator>Gordon Ross</dc:creator>
		<pubDate>Sat, 12 Apr 2008 05:18:54 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-2849</guid>
		<description>I think given all the hard work you've put into writing and discussing the dynamics of social software and its adoption in corporate settings, you can be excused from propagating a fairly persuasive meme, Suw... Without having the types of tools available to us that Duncan Watts does, it's also significantly more difficult to disprove such a theory, other than through gut feeling. And Gladwell is such a convincing writer, you *want* to believe that he's right and done his homework (Blink aside).

One quick addition to your thoughts here: while those with significant influence in the organization (note: people with a lot of say or power are different than Gladwell's definition of "influencers" in his tipping point analogy) may not be necessary for adoption, their lack of involvement may jeopardize the project, no matter how wildly successful amongst the rest of the participants. Like any technology project, the old stakeholder analysis matrix is good to trot out and look for interest vs. influence within the organization. In your typical hierarchical org-chart-driven company, this shouldn't be too hard to do and the risk you mitigate is substantial.

High interest, high influence? Brilliant, we want some of them on our team please. Low interest, low influence? Perhaps we don't spend as much time trying to get them excited. High interest, low influence? They're on the right side of the fence -- good supporters, the unsung heroes and everyday adopters of social tools in the enterprise. Low interest, high influence? Oh dear -- be sure to keep an eye out on this crowd, it's a potentially volatile bunch.

How many projects have you been involved with where a senior stakeholder in the organization came out of the woodwork at the 11th hour and put an end to the project? If the answer is not many, then you've done a brilliant job in managing your stakeholders well. But I'd be guessing that you're in the minority of consultants in terms of projects involving organizational change and technology.

So perhaps a bit tangential to Gladwell's concept of influencers per se, but something to remember when introducing potentially disruptive social tools in an organization where bottom-up network dynamics can be seen as undermining authority of those with influence.
</description>
		<content:encoded><![CDATA[<p>I think given all the hard work you&#8217;ve put into writing and discussing the dynamics of social software and its adoption in corporate settings, you can be excused from propagating a fairly persuasive meme, Suw&#8230; Without having the types of tools available to us that Duncan Watts does, it&#8217;s also significantly more difficult to disprove such a theory, other than through gut feeling. And Gladwell is such a convincing writer, you *want* to believe that he&#8217;s right and done his homework (Blink aside).</p>
<p>One quick addition to your thoughts here: while those with significant influence in the organization (note: people with a lot of say or power are different than Gladwell&#8217;s definition of &#8220;influencers&#8221; in his tipping point analogy) may not be necessary for adoption, their lack of involvement may jeopardize the project, no matter how wildly successful amongst the rest of the participants. Like any technology project, the old stakeholder analysis matrix is good to trot out and look for interest vs. influence within the organization. In your typical hierarchical org-chart-driven company, this shouldn&#8217;t be too hard to do and the risk you mitigate is substantial.</p>
<p>High interest, high influence? Brilliant, we want some of them on our team please. Low interest, low influence? Perhaps we don&#8217;t spend as much time trying to get them excited. High interest, low influence? They&#8217;re on the right side of the fence &#8212; good supporters, the unsung heroes and everyday adopters of social tools in the enterprise. Low interest, high influence? Oh dear &#8212; be sure to keep an eye out on this crowd, it&#8217;s a potentially volatile bunch.</p>
<p>How many projects have you been involved with where a senior stakeholder in the organization came out of the woodwork at the 11th hour and put an end to the project? If the answer is not many, then you&#8217;ve done a brilliant job in managing your stakeholders well. But I&#8217;d be guessing that you&#8217;re in the minority of consultants in terms of projects involving organizational change and technology.</p>
<p>So perhaps a bit tangential to Gladwell&#8217;s concept of influencers per se, but something to remember when introducing potentially disruptive social tools in an organization where bottom-up network dynamics can be seen as undermining authority of those with influence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Black</title>
		<link>http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-2848</link>
		<dc:creator>George Black</dc:creator>
		<pubDate>Fri, 11 Apr 2008 18:13:02 +0000</pubDate>
		<guid isPermaLink="false">http://strange.corante.com/2008/04/10/confessing-a-dirty-little-secret#comment-2848</guid>
		<description>Great article Suw, your article makes a lot of sense. I agree entirely about identifying the people who are "chomping at the bit to work differently", these people very often have a frustration which can be solved by social software.

We have found a couple of other factors. One is that these social tools have to be as simple to use as possible for the rest of the team. People are so resistant to change even the smallest hurdle can be too much and a lot of tools are still lacking basic usability. The team being introduced to the tool need to be focusing on the content and the task not the actual tool itself. This also means they are much more likely to propagate the use throughout the organisation.

The second factor is more difficult as it involves the personal politics of the team or organisation. If there are already problems these don’t go away with new tools. Having said that some collaboration tools can improve relationships as people can stay in the loop and join in when they are ready in a way they would never do in a physical meeting.

</description>
		<content:encoded><![CDATA[<p>Great article Suw, your article makes a lot of sense. I agree entirely about identifying the people who are &#8220;chomping at the bit to work differently&#8221;, these people very often have a frustration which can be solved by social software.</p>
<p>We have found a couple of other factors. One is that these social tools have to be as simple to use as possible for the rest of the team. People are so resistant to change even the smallest hurdle can be too much and a lot of tools are still lacking basic usability. The team being introduced to the tool need to be focusing on the content and the task not the actual tool itself. This also means they are much more likely to propagate the use throughout the organisation.</p>
<p>The second factor is more difficult as it involves the personal politics of the team or organisation. If there are already problems these don’t go away with new tools. Having said that some collaboration tools can improve relationships as people can stay in the loop and join in when they are ready in a way they would never do in a physical meeting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

