<?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: A Lesson in Recycling Chartjunk as Junk Art</title>
	<atom:link href="http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/feed/" rel="self" type="application/rss+xml" />
	<link>http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/</link>
	<description>Strength in Numbers</description>
	<lastBuildDate>Tue, 16 Mar 2010 18:15:01 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Zbicyclist</title>
		<link>http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1776</link>
		<dc:creator>Zbicyclist</dc:creator>
		<pubDate>Thu, 21 Feb 2008 05:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1776</guid>
		<description>Nathan asks: &quot;Can we think of information, insights, or intelligence as simply processed, cleaned, and/or processed data?&quot;

Yes, with the added requirement that it be processed (usually aggregated or summarized) for some purpose. For example, a moving average used as a naive forecast is information -- to a person who needs a naive forecast.

&quot;Insights&quot; is a current business buzzword. A lot of former VP&#039;s of Marketing Research became VP&#039;s of Insights over the past few years. It&#039;s a cooler, less descriptive title.</description>
		<content:encoded><![CDATA[<p>Nathan asks: &#8220;Can we think of information, insights, or intelligence as simply processed, cleaned, and/or processed data?&#8221;</p>
<p>Yes, with the added requirement that it be processed (usually aggregated or summarized) for some purpose. For example, a moving average used as a naive forecast is information &#8212; to a person who needs a naive forecast.</p>
<p>&#8220;Insights&#8221; is a current business buzzword. A lot of former VP&#8217;s of Marketing Research became VP&#8217;s of Insights over the past few years. It&#8217;s a cooler, less descriptive title.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1673</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Thu, 14 Feb 2008 05:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1673</guid>
		<description>Can we think of information, insights, or intelligence as simply processed, cleaned, and/or processed data?</description>
		<content:encoded><![CDATA[<p>Can we think of information, insights, or intelligence as simply processed, cleaned, and/or processed data?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ZBicyclist</title>
		<link>http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1667</link>
		<dc:creator>ZBicyclist</dc:creator>
		<pubDate>Wed, 13 Feb 2008 14:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1667</guid>
		<description>The usual distinction drawn in the BI community is between data (where Wal-mart has 500 terabytes) and information. 

Information might also be called &quot;insights&quot; or &quot;intelligence&quot; or something else, but involves some form of summary that makes the information useful to a decision maker.

This distinction is neither new nor ignored. 

Are gigantic databases the new world? Sure. 

Do they change the way we deal with statistics? Sure. 

For one thing, there&#039;s my old motto: &quot;Data drives out analysis.&quot;  For example, if you are just able to keep aggregate data, you might need to model how much of a particular product to send to a store depending on size of store, seasonality, demographics of the trading area, and other analytic factors. Once you have all this data,  in many cases you can simply say: what&#039;s the average sales rate in this store at this price?

For another thing, large databases put a premium on the ability to automate analysis, so the statistician&#039;s task isn&#039;t to analyze a particular data set, but to figure out how to analyze data sets of this type (and define &quot;type&quot;) so useful results can be displayed. This puts a big premium on &quot;robust&quot;.</description>
		<content:encoded><![CDATA[<p>The usual distinction drawn in the BI community is between data (where Wal-mart has 500 terabytes) and information. </p>
<p>Information might also be called &#8220;insights&#8221; or &#8220;intelligence&#8221; or something else, but involves some form of summary that makes the information useful to a decision maker.</p>
<p>This distinction is neither new nor ignored. </p>
<p>Are gigantic databases the new world? Sure. </p>
<p>Do they change the way we deal with statistics? Sure. </p>
<p>For one thing, there&#8217;s my old motto: &#8220;Data drives out analysis.&#8221;  For example, if you are just able to keep aggregate data, you might need to model how much of a particular product to send to a store depending on size of store, seasonality, demographics of the trading area, and other analytic factors. Once you have all this data,  in many cases you can simply say: what&#8217;s the average sales rate in this store at this price?</p>
<p>For another thing, large databases put a premium on the ability to automate analysis, so the statistician&#8217;s task isn&#8217;t to analyze a particular data set, but to figure out how to analyze data sets of this type (and define &#8220;type&#8221;) so useful results can be displayed. This puts a big premium on &#8220;robust&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Peltier</title>
		<link>http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1649</link>
		<dc:creator>Jon Peltier</dc:creator>
		<pubDate>Tue, 12 Feb 2008 16:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/2008/02/12/a-lesson-in-recycling-chartjunk-as-junk-art/#comment-1649</guid>
		<description>The most-to-least-tenured/color-by-business-function data rich graphic would probably only be useful and relevant up to a very small total number of employees.

The NY Times chart on deaths in Iraq is interesting and loaded with data. I&#039;m not sure it wouldn&#039;t be better to use multiple charts to present different aspects of the data separately. For example, a timeline of death count by day would give a better picture of this particular stat than does looking at rows and rows of boxes (it&#039;s hard to note days with zero deaths unless one studies the dates).

Similar timelines showing the different causes of fatalities would help to note patterns in prevalence of, say, hostile fire vs suicide bombings. I find it harder to get this from the jumbled blobs of color in the large chart than I would from multiple-series timelines.

But as Nathan has reminded me in a private communication, you often need to attract readers to your analysis with colorful, attractive, &quot;fun&quot; charts.</description>
		<content:encoded><![CDATA[<p>The most-to-least-tenured/color-by-business-function data rich graphic would probably only be useful and relevant up to a very small total number of employees.</p>
<p>The NY Times chart on deaths in Iraq is interesting and loaded with data. I&#8217;m not sure it wouldn&#8217;t be better to use multiple charts to present different aspects of the data separately. For example, a timeline of death count by day would give a better picture of this particular stat than does looking at rows and rows of boxes (it&#8217;s hard to note days with zero deaths unless one studies the dates).</p>
<p>Similar timelines showing the different causes of fatalities would help to note patterns in prevalence of, say, hostile fire vs suicide bombings. I find it harder to get this from the jumbled blobs of color in the large chart than I would from multiple-series timelines.</p>
<p>But as Nathan has reminded me in a private communication, you often need to attract readers to your analysis with colorful, attractive, &#8220;fun&#8221; charts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
