<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Cluetrainings</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2008/10/27/cluetrainings-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2008/10/27/cluetrainings-2/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Sat, 28 Nov 2009 21:14:31 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jMac</title>
		<link>http://blogs.law.harvard.edu/doc/2008/10/27/cluetrainings-2/comment-page-1/#comment-99294</link>
		<dc:creator>jMac</dc:creator>
		<pubDate>Wed, 29 Oct 2008 08:39:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1067#comment-99294</guid>
		<description>Doc - truly honored you liked this...

Yesterday I gave a keynote in Berlin - all based on CT - tomorrow I address the IAB in Amsterdam and again, as ever, the CT theses play a leading role.

I have registered for VRM so will see you there - very happy you are coming to the UK :)</description>
		<content:encoded><![CDATA[<p>Doc &#8211; truly honored you liked this&#8230;</p>
<p>Yesterday I gave a keynote in Berlin &#8211; all based on CT &#8211; tomorrow I address the IAB in Amsterdam and again, as ever, the CT theses play a leading role.</p>
<p>I have registered for VRM so will see you there &#8211; very happy you are coming to the UK <img src='http://blogs.law.harvard.edu/doc/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Magee</title>
		<link>http://blogs.law.harvard.edu/doc/2008/10/27/cluetrainings-2/comment-page-1/#comment-98853</link>
		<dc:creator>Kevin Magee</dc:creator>
		<pubDate>Tue, 28 Oct 2008 15:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/?p=1067#comment-98853</guid>
		<description>Doc, really interesting testimonial from Jonathan re Cluetrain. I&#039;ve been following a lot of the Cluetrain thesis myself over the years in various projects I&#039;ve been involved with. I have to say, in pretty much every case where we kept the communication open and honest the projects were very successful. They weren&#039;t necessarily easy and there were times when we got severely criticized from less enlightened higher-ups for &quot;telling the clients too much&quot;. 

Earlier this year I was involved with a number of projects which had hit a wall and didn&#039;t look like they would ever get done. We changed to a very open and collaborative communication style to guide our clients over the line. It worked. The projects were successfully delivered. 

One interesting aspect was where we ran up against the culture of our clients which in some cases was very closed. The joint project team (supplier + client) was trying to keep huge levels of open communication going and was gaining from it - and everybody knew it. However, management on the client side did the usual interaction with a vendor where they wanted us to be really open but everything was a secret from their perspective - or so they thought. The open project level communication flow basically meant we knew what was going on despite attempts at controlling the information. 

Cluetrain is totally correct. Trying to shut down information doesn&#039;t work. Old style command and control is counterproductive. I believe embracing this open and honest Cluetrain communication approach is the only way to achieve success for projects or companies. 

My blog: http://inchpebbles.blogspot.com/</description>
		<content:encoded><![CDATA[<p>Doc, really interesting testimonial from Jonathan re Cluetrain. I&#8217;ve been following a lot of the Cluetrain thesis myself over the years in various projects I&#8217;ve been involved with. I have to say, in pretty much every case where we kept the communication open and honest the projects were very successful. They weren&#8217;t necessarily easy and there were times when we got severely criticized from less enlightened higher-ups for &#8220;telling the clients too much&#8221;. </p>
<p>Earlier this year I was involved with a number of projects which had hit a wall and didn&#8217;t look like they would ever get done. We changed to a very open and collaborative communication style to guide our clients over the line. It worked. The projects were successfully delivered. </p>
<p>One interesting aspect was where we ran up against the culture of our clients which in some cases was very closed. The joint project team (supplier + client) was trying to keep huge levels of open communication going and was gaining from it &#8211; and everybody knew it. However, management on the client side did the usual interaction with a vendor where they wanted us to be really open but everything was a secret from their perspective &#8211; or so they thought. The open project level communication flow basically meant we knew what was going on despite attempts at controlling the information. </p>
<p>Cluetrain is totally correct. Trying to shut down information doesn&#8217;t work. Old style command and control is counterproductive. I believe embracing this open and honest Cluetrain communication approach is the only way to achieve success for projects or companies. </p>
<p>My blog: <a href="http://inchpebbles.blogspot.com/" rel="nofollow">http://inchpebbles.blogspot.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
