<?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/"
		>
<channel>
	<title>Comments on: OGI Conference: Recommended for enterprise CTOs in the federal space</title>
	<atom:link href="http://ctovision.com/2009/06/opengovinnovations-gov-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://ctovision.com/2009/06/opengovinnovations-gov-2/</link>
	<description>Context for the enterprise technologist</description>
	<lastBuildDate>Sun, 20 May 2012 18:25:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Bob Gourley</title>
		<link>http://ctovision.com/2009/06/opengovinnovations-gov-2/#comment-453</link>
		<dc:creator>Bob Gourley</dc:creator>
		<pubDate>Mon, 27 Jul 2009 13:44:14 +0000</pubDate>
		<guid isPermaLink="false">http://ctovision.com/?p=512#comment-453</guid>
		<description>Dave thanks for the note and for the link.

Cheers,
Bob </description>
		<content:encoded><![CDATA[<p>Dave thanks for the note and for the link.</p>
<p>Cheers,<br />
Bob </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Lush</title>
		<link>http://ctovision.com/2009/06/opengovinnovations-gov-2/#comment-452</link>
		<dc:creator>Dave Lush</dc:creator>
		<pubDate>Sun, 28 Jun 2009 05:55:47 +0000</pubDate>
		<guid isPermaLink="false">http://ctovision.com/?p=512#comment-452</guid>
		<description>Bob,  I agree whole heartedly with your observation about analyst culture and the rate of tool adoption.   I have written a few think pieces on this matter because in my view it is one of the most serious problems that we have in the IC today.  I have posted some thoughts  on this matter on my blog;  the specific piece is at &lt;a href=&quot;http://davelush.typepad.com/extracts_from_the_discomf/2008/02/the-threat-knowledge-management-imperative-and-the-analyst-culture-trap.html&quot; rel=&quot;nofollow&quot;&gt;http://davelush.typepad.com/extracts_from_the_dis...&lt;/a&gt;.   Suffice to say here that I believe the problem is largely one for leadership which in my view has thus far generally &quot;caved&quot; to the  whims of the analyst community. I have seen numerous situations in which a small handful of right thinking analysts applied new tools with great effectiveness thus proving the worth of the tool but nevertheless the bulk of the analysts still didn&#039;t adapt and the leadership didn&#039;t lead even tho the benefits of the tool were in essence demonstrated and proven.  This is not good!



Be well!  your blog is great!



Dave Lush </description>
		<content:encoded><![CDATA[<p>Bob,  I agree whole heartedly with your observation about analyst culture and the rate of tool adoption.   I have written a few think pieces on this matter because in my view it is one of the most serious problems that we have in the IC today.  I have posted some thoughts  on this matter on my blog;  the specific piece is at <a href="http://davelush.typepad.com/extracts_from_the_discomf/2008/02/the-threat-knowledge-management-imperative-and-the-analyst-culture-trap.html" rel="nofollow"></a><a href="http://davelush.typepad.com/extracts_from_the_dis" rel="nofollow">http://davelush.typepad.com/extracts_from_the_dis</a>&#8230;.   Suffice to say here that I believe the problem is largely one for leadership which in my view has thus far generally &quot;caved&quot; to the  whims of the analyst community. I have seen numerous situations in which a small handful of right thinking analysts applied new tools with great effectiveness thus proving the worth of the tool but nevertheless the bulk of the analysts still didn&#039;t adapt and the leadership didn&#039;t lead even tho the benefits of the tool were in essence demonstrated and proven.  This is not good!</p>
<p>Be well!  your blog is great!</p>
<p>Dave Lush </p>
]]></content:encoded>
	</item>
</channel>
</rss>

