<?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: It&#8217;s Not Not About the Technology</title>
	<atom:link href="http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/</link>
	<description>The Business Impact of IT</description>
	<lastBuildDate>Tue, 09 Mar 2010 16:08:14 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: itjobs1</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-19197</link>
		<dc:creator>itjobs1</dc:creator>
		<pubDate>Wed, 09 Dec 2009 15:13:48 +0000</pubDate>
		<guid isPermaLink="false">#comment-19197</guid>
		<description>I agree with that. Have we all become more productive through using the latest version of Word as opposed to the first version? No. Even an increase in user-friendliness of software products has often been negated by an increase in functionality and therefore complexity for the end user. Similarly, when looking at blogs, wikis etc, INATT in this sense means we shouldn’t get hung up on features, we should concentrate on implementation and take-up.&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Find more jobs:    &lt;a href=&quot;http://www.staffingpower.com/&quot; rel=&quot;nofollow&quot;&gt;http://www.staffingpower.com/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I agree with that. Have we all become more productive through using the latest version of Word as opposed to the first version? No. Even an increase in user-friendliness of software products has often been negated by an increase in functionality and therefore complexity for the end user. Similarly, when looking at blogs, wikis etc, INATT in this sense means we shouldn’t get hung up on features, we should concentrate on implementation and take-up.</p>
<p>Find more jobs:    <a href="http://www.staffingpower.com/" rel="nofollow">http://www.staffingpower.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Just another assessment of the E 2.O Conference: How Beautiful it is, and How Easily it can be Broken &#171; Fredzimny&#8217;s CCCCC Blog</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-18447</link>
		<dc:creator>Just another assessment of the E 2.O Conference: How Beautiful it is, and How Easily it can be Broken &#171; Fredzimny&#8217;s CCCCC Blog</dc:creator>
		<pubDate>Tue, 07 Jul 2009 18:26:43 +0000</pubDate>
		<guid isPermaLink="false">#comment-18447</guid>
		<description>[...] and usable technologies. I know that E2.0 is not about the technology. But it’s also not not about the technologies deployed. They had better be appropriate to the goal(s) of the initiative, and they had better be freeform, [...]</description>
		<content:encoded><![CDATA[<p>[...] and usable technologies. I know that E2.0 is not about the technology. But it’s also not not about the technologies deployed. They had better be appropriate to the goal(s) of the initiative, and they had better be freeform, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How Beautiful it is, and How Easily it can be Broken : Andrew McAfee&#8217;s Blog</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-16995</link>
		<dc:creator>How Beautiful it is, and How Easily it can be Broken : Andrew McAfee&#8217;s Blog</dc:creator>
		<pubDate>Mon, 29 Jun 2009 13:25:58 +0000</pubDate>
		<guid isPermaLink="false">#comment-16995</guid>
		<description>[...] and usable technologies. I know that E2.0 is not about the technology. But it&#8217;s also not not about the technologies deployed. They had better be appropriate to the goal(s) of the initiative, and they had better be freeform, [...]</description>
		<content:encoded><![CDATA[<p>[...] and usable technologies. I know that E2.0 is not about the technology. But it&#8217;s also not not about the technologies deployed. They had better be appropriate to the goal(s) of the initiative, and they had better be freeform, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Explosives Automation</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-14034</link>
		<dc:creator>Explosives Automation</dc:creator>
		<pubDate>Fri, 05 Jun 2009 04:44:02 +0000</pubDate>
		<guid isPermaLink="false">#comment-14034</guid>
		<description>Technology had been a big influence for all of  us no wonder why many people are into technology,  technology had affected our way of living as we can see every house and store has technology in it.</description>
		<content:encoded><![CDATA[<p>Technology had been a big influence for all of  us no wonder why many people are into technology,  technology had affected our way of living as we can see every house and store has technology in it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: energy saving devices</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-3285</link>
		<dc:creator>energy saving devices</dc:creator>
		<pubDate>Tue, 06 Jan 2009 07:38:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-3285</guid>
		<description>Dear Andrew,

INATT - isn&#039;t exactly right in my humble opinion. Only when a number of positive usages come out of a technology, people can use it, or can say &quot;usable technology&quot;. Technology takes a long time in the research phase to eventually come out ready for the consumption of the general public. But i think its a little disrespect to the people who work years to bring a technology in the usable format. Just think about Solid State drives - its a brand new technology explored right now which will eventually replace all the cylindrical disk drives. 

My point is - technology should always be hailed, but in order to use the technology - there can be numerous determinant factors behind. Whats a labrat today may eventually open the gates for a whole new world of invention in the future.

Best Regards.</description>
		<content:encoded><![CDATA[<p>Dear Andrew,</p>
<p>INATT &#8211; isn&#8217;t exactly right in my humble opinion. Only when a number of positive usages come out of a technology, people can use it, or can say &#8220;usable technology&#8221;. Technology takes a long time in the research phase to eventually come out ready for the consumption of the general public. But i think its a little disrespect to the people who work years to bring a technology in the usable format. Just think about Solid State drives &#8211; its a brand new technology explored right now which will eventually replace all the cylindrical disk drives. </p>
<p>My point is &#8211; technology should always be hailed, but in order to use the technology &#8211; there can be numerous determinant factors behind. Whats a labrat today may eventually open the gates for a whole new world of invention in the future.</p>
<p>Best Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ZTR Man</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-3286</link>
		<dc:creator>ZTR Man</dc:creator>
		<pubDate>Mon, 29 Dec 2008 16:41:29 +0000</pubDate>
		<guid isPermaLink="false">#comment-3286</guid>
		<description>I think it IS about the technology. Without technology we wouldn&#039;t be having this discussion while we are sitting at home (or work, or wherever).

Sometimes people can forget though, it isn&#039;t ONLY about the technology.  Once the basic framework is in place, its time for the end users to move in and put it to use.  If no one uses your shiny new piece of technology, then it is just as good as a doorjamb.  Thats why usability and appeal are equally as important as the technology that runs the thing.</description>
		<content:encoded><![CDATA[<p>I think it IS about the technology. Without technology we wouldn&#8217;t be having this discussion while we are sitting at home (or work, or wherever).</p>
<p>Sometimes people can forget though, it isn&#8217;t ONLY about the technology.  Once the basic framework is in place, its time for the end users to move in and put it to use.  If no one uses your shiny new piece of technology, then it is just as good as a doorjamb.  Thats why usability and appeal are equally as important as the technology that runs the thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: izlekop</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-3284</link>
		<dc:creator>izlekop</dc:creator>
		<pubDate>Wed, 15 Oct 2008 17:20:30 +0000</pubDate>
		<guid isPermaLink="false">#comment-3284</guid>
		<description>INATT in the second sense can also mean &#8220;it&#8217;s not about the bells and whistles of the technology&#8221; - it&#8217;s the essence of the tool that is important, not the detailed bits of functionality.  I agree with that.  Have we all become more productive through using the latest version of Word as opposed to the first version?  No.  Even an increase in user-friendliness of software products has often been negated by an increase in functionality and therefore complexity for the end user.  Similarly, when looking at blogs, wikis etc, INATT in this sense means we shouldn&#8217;t get hung up on features, we should concentrate on implementation and take-up.</description>
		<content:encoded><![CDATA[<p>INATT in the second sense can also mean &#8220;it&#8217;s not about the bells and whistles of the technology&#8221; &#8211; it&#8217;s the essence of the tool that is important, not the detailed bits of functionality.  I agree with that.  Have we all become more productive through using the latest version of Word as opposed to the first version?  No.  Even an increase in user-friendliness of software products has often been negated by an increase in functionality and therefore complexity for the end user.  Similarly, when looking at blogs, wikis etc, INATT in this sense means we shouldn&#8217;t get hung up on features, we should concentrate on implementation and take-up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Kresta</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-3283</link>
		<dc:creator>Dave Kresta</dc:creator>
		<pubDate>Mon, 30 Jul 2007 19:57:01 +0000</pubDate>
		<guid isPermaLink="false">#comment-3283</guid>
		<description>I agree that sometimes we too easily dismiss technology, but this is usually in reaction to vendors who DO seem to think they have the magic bullet. Technology of course DOES matter when it changes the fundamental economics of a system - for example in Wikinomics, Tapscott and Williams draw attention to Coase&#039;s law that says that firms &quot;will tend to expand until the costs of organizing an extra transaction within the firm become equal to the costs of carrying out the same transaction on the open market.&quot; In this case, it is about the technology opening up new value producing avenues. Read more about this at http://www.collaborativeye.com/wikinomics/</description>
		<content:encoded><![CDATA[<p>I agree that sometimes we too easily dismiss technology, but this is usually in reaction to vendors who DO seem to think they have the magic bullet. Technology of course DOES matter when it changes the fundamental economics of a system &#8211; for example in Wikinomics, Tapscott and Williams draw attention to Coase&#8217;s law that says that firms &#8220;will tend to expand until the costs of organizing an extra transaction within the firm become equal to the costs of carrying out the same transaction on the open market.&#8221; In this case, it is about the technology opening up new value producing avenues. Read more about this at <a href="http://www.collaborativeye.com/wikinomics/" rel="nofollow">http://www.collaborativeye.com/wikinomics/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Frank</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-3278</link>
		<dc:creator>Jordan Frank</dc:creator>
		<pubDate>Wed, 18 Jul 2007 16:34:15 +0000</pubDate>
		<guid isPermaLink="false">#comment-3278</guid>
		<description>The strongest INATT supporters are the consultants and some pundits whose interest is to sell coaching and training services. There is a certain bias here! For some reason, there is a parallel debate about the structure. So, I recently wrote a companion post to yours here which advocates the position that (a href=&quot;https://traction.tractionsoftware.com/traction/permalink/Blog426&quot;&gt;Its Not Not About the Structure INNATS&gt;&lt;/a&gt;. 

By the same line of reasoning that collaboration success is driven in part by choosing the right technology and in part by other factors -- the training, process fit, technology use pattern, and stakeholder support (and I argue that culture has little to do with it if you get the other four factors mentioned here correct) -- some structure and some creative freedom must balance to achieve consistent positive results from an E2.0 workspace, be it blog or wiki, or whatever.</description>
		<content:encoded><![CDATA[<p>The strongest INATT supporters are the consultants and some pundits whose interest is to sell coaching and training services. There is a certain bias here! For some reason, there is a parallel debate about the structure. So, I recently wrote a companion post to yours here which advocates the position that (a href=&#8221;https://traction.tractionsoftware.com/traction/permalink/Blog426&#8243;>Its Not Not About the Structure INNATS>. </p>
<p>By the same line of reasoning that collaboration success is driven in part by choosing the right technology and in part by other factors &#8212; the training, process fit, technology use pattern, and stakeholder support (and I argue that culture has little to do with it if you get the other four factors mentioned here correct) &#8212; some structure and some creative freedom must balance to achieve consistent positive results from an E2.0 workspace, be it blog or wiki, or whatever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edmund Ng</title>
		<link>http://andrewmcafee.org/2007/07/its_not_not_about_the_technology/comment-page-1/#comment-3282</link>
		<dc:creator>Edmund Ng</dc:creator>
		<pubDate>Wed, 18 Jul 2007 11:41:28 +0000</pubDate>
		<guid isPermaLink="false">#comment-3282</guid>
		<description>It&#039;s about time everything go open standards but is it really possible? Everybody says J2EE is based on open standards but the truth is all vendors have their own intepretation of open standards.

They have successfully made it uniquely &#039;their platform&#039; so that the customers still have to use their solutions, their consultants, their vendors and their solution integration team.


Edmund Ng</description>
		<content:encoded><![CDATA[<p>It&#8217;s about time everything go open standards but is it really possible? Everybody says J2EE is based on open standards but the truth is all vendors have their own intepretation of open standards.</p>
<p>They have successfully made it uniquely &#8216;their platform&#8217; so that the customers still have to use their solutions, their consultants, their vendors and their solution integration team.</p>
<p>Edmund Ng</p>
]]></content:encoded>
	</item>
</channel>
</rss>
