<?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: The diminishing returns of too much information</title>
	<atom:link href="http://dangerouslyirrelevant.org/2008/05/information-ove.html/feed" rel="self" type="application/rss+xml" />
	<link>http://dangerouslyirrelevant.org/2008/05/information-ove.html</link>
	<description>Technology, leadership, and the future of schools</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:00:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Justin B.</title>
		<link>http://dangerouslyirrelevant.org/2008/05/information-ove.html/comment-page-1#comment-12771</link>
		<dc:creator>Justin B.</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/05/information-ove.html#comment-12771</guid>
		<description>I think this is a great point, but I am going to suggest a minor change. I think the label on the X axis should read &quot;Amount of Information Under Consideration&quot; instead of just &quot;Amount of Information.&quot; I like your way of putting it better than Morville&#039;s &quot;Volume of Information,&quot; but I still think the essential part is &quot;under consideration,&quot; not the &quot;volume&quot; or &quot;amount&quot;.

I don&#039;t see any problem whatsoever with increased volume of information. The more we know the better - if the information just sits there and is never used, so be it, it is not harming anything. For instance, I don&#039;t think that a larger dataset with 50 columns is any worse than a smaller dataset with 20 columns of information. The trick is to know which columns are relevant and which are not. But, we shouldn&#039;t use rationale as a justification to limit information production, we should use this as a justification to get better at information management.
</description>
		<content:encoded><![CDATA[<p>I think this is a great point, but I am going to suggest a minor change. I think the label on the X axis should read &#8220;Amount of Information Under Consideration&#8221; instead of just &#8220;Amount of Information.&#8221; I like your way of putting it better than Morville&#8217;s &#8220;Volume of Information,&#8221; but I still think the essential part is &#8220;under consideration,&#8221; not the &#8220;volume&#8221; or &#8220;amount&#8221;.</p>
<p>I don&#8217;t see any problem whatsoever with increased volume of information. The more we know the better &#8211; if the information just sits there and is never used, so be it, it is not harming anything. For instance, I don&#8217;t think that a larger dataset with 50 columns is any worse than a smaller dataset with 20 columns of information. The trick is to know which columns are relevant and which are not. But, we shouldn&#8217;t use rationale as a justification to limit information production, we should use this as a justification to get better at information management.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott McLeod</title>
		<link>http://dangerouslyirrelevant.org/2008/05/information-ove.html/comment-page-1#comment-12772</link>
		<dc:creator>Scott McLeod</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/05/information-ove.html#comment-12772</guid>
		<description>Maybe, Justin, but there&#039;s also the &#039;signal-to-noise&#039; ratio to consider. At some point, filtering through the excess (e.g., my Internet browser bookmarks!) to get to what you want becomes too difficult and/or time-consuming. Why dig through 50 columns when you only want 6?

That said, you can add whatever qualifiers you want to the graph - that&#039;s okay with me!
</description>
		<content:encoded><![CDATA[<p>Maybe, Justin, but there&#8217;s also the &#8216;signal-to-noise&#8217; ratio to consider. At some point, filtering through the excess (e.g., my Internet browser bookmarks!) to get to what you want becomes too difficult and/or time-consuming. Why dig through 50 columns when you only want 6?</p>
<p>That said, you can add whatever qualifiers you want to the graph &#8211; that&#8217;s okay with me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pavel</title>
		<link>http://dangerouslyirrelevant.org/2008/05/information-ove.html/comment-page-1#comment-12773</link>
		<dc:creator>Pavel</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/05/information-ove.html#comment-12773</guid>
		<description>Very helpful visualization, thanks. Although the issue may well be semantic, I wonder how data quality - rather than simply quantity - affects this graph. What I take from this is despite (maybe because of?) a phenomenological argument like Morville&#039;s seems to be, what I take away is an increasing need for information literacy education rather than simply letting our students &#039;become what they find.&#039;
</description>
		<content:encoded><![CDATA[<p>Very helpful visualization, thanks. Although the issue may well be semantic, I wonder how data quality &#8211; rather than simply quantity &#8211; affects this graph. What I take from this is despite (maybe because of?) a phenomenological argument like Morville&#8217;s seems to be, what I take away is an increasing need for information literacy education rather than simply letting our students &#8216;become what they find.&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Hetherington</title>
		<link>http://dangerouslyirrelevant.org/2008/05/information-ove.html/comment-page-1#comment-12774</link>
		<dc:creator>Mike Hetherington</dc:creator>
		<pubDate>Tue, 30 Nov 1999 05:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://annahein.com/2008/05/information-ove.html#comment-12774</guid>
		<description>Scott, I like your visual of the inverted U. Information is excessive if it&#039;s not somehow pertinent to the goal or if it&#039;s relevant but can be consolidated into a more readable and therefor more useful form. Almost anything can be quantified, (for example, the number of cells lost from my fingertips during this exercise!)but unless it ultimately relates to the chosen topic, that data is noise. Data teams need to consistently review the relevance of their data and the targets of the measurement to avoid &quot;data overload&quot; or worse, drawing conclusions from irrelevant noise.


</description>
		<content:encoded><![CDATA[<p>Scott, I like your visual of the inverted U. Information is excessive if it&#8217;s not somehow pertinent to the goal or if it&#8217;s relevant but can be consolidated into a more readable and therefor more useful form. Almost anything can be quantified, (for example, the number of cells lost from my fingertips during this exercise!)but unless it ultimately relates to the chosen topic, that data is noise. Data teams need to consistently review the relevance of their data and the targets of the measurement to avoid &#8220;data overload&#8221; or worse, drawing conclusions from irrelevant noise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

