<?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: Chart Junk vs. Eye Candy: What&#8217;s the Difference?</title>
	<atom:link href="http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/feed/" rel="self" type="application/rss+xml" />
	<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/</link>
	<description>Strength in Numbers</description>
	<lastBuildDate>Sun, 12 Feb 2012 04:57:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34439</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 28 Sep 2009 21:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34439</guid>
		<description>&lt;i&gt;What do you think â€“ Is there a difference between the two?&lt;/i&gt;

No.</description>
		<content:encoded><![CDATA[<p><i>What do you think â€“ Is there a difference between the two?</i></p>
<p>No.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chart Junk vs. Eye Candy: Whatâ€™s the Difference? &#8212; Some Random Dude</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34433</link>
		<dc:creator>Chart Junk vs. Eye Candy: Whatâ€™s the Difference? &#8212; Some Random Dude</dc:creator>
		<pubDate>Mon, 28 Sep 2009 17:20:25 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34433</guid>
		<description>[...] Chart Junk vs. Eye Candy: Whatâ€™s the Difference? [...]</description>
		<content:encoded><![CDATA[<p>[...] Chart Junk vs. Eye Candy: Whatâ€™s the Difference? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrea</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34426</link>
		<dc:creator>andrea</dc:creator>
		<pubDate>Mon, 28 Sep 2009 02:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34426</guid>
		<description>like you said, Nathan, it&#039;s probably just all in the eye of the beholder.

chart junk is just the &#039;ugly&#039; extreme of a &#039;Superfluous/Redundant Elements Continuum&#039; where eye candy sits on the other end.

like you said, examples on Junk Charts are great examples of the former, and GOOD transparencies of the latter.

then, imagine a different set of axes, the &#039;Meaningfulness Continuum&#039; which describes how well a visualisation communicates a particular meaning/purpose/story/narrative/intent.

if there are design elements/features which help build the story, then they are no longer chart junk or eye candy.</description>
		<content:encoded><![CDATA[<p>like you said, Nathan, it&#8217;s probably just all in the eye of the beholder.</p>
<p>chart junk is just the &#8216;ugly&#8217; extreme of a &#8216;Superfluous/Redundant Elements Continuum&#8217; where eye candy sits on the other end.</p>
<p>like you said, examples on Junk Charts are great examples of the former, and GOOD transparencies of the latter.</p>
<p>then, imagine a different set of axes, the &#8216;Meaningfulness Continuum&#8217; which describes how well a visualisation communicates a particular meaning/purpose/story/narrative/intent.</p>
<p>if there are design elements/features which help build the story, then they are no longer chart junk or eye candy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daily Digest for September 26th</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34413</link>
		<dc:creator>Daily Digest for September 26th</dc:creator>
		<pubDate>Sat, 26 Sep 2009 07:46:58 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34413</guid>
		<description>[...] Shared Chart Junk vs. Eye Candy: Whatâ€™s the Difference?. [...]</description>
		<content:encoded><![CDATA[<p>[...] Shared Chart Junk vs. Eye Candy: Whatâ€™s the Difference?. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Weir</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34410</link>
		<dc:creator>Jeff Weir</dc:creator>
		<pubDate>Fri, 25 Sep 2009 22:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34410</guid>
		<description>Regardless of differing definitions, Ryan&#039;s comment &quot;if you canâ€™t tell a compelling story with data without extraneous crap, youâ€™re doing it wrong&quot; is spot on.  So is Pauloâ€™s comment  â€œitâ€™s all about failing or succeeding in reaching the (communicative) goalâ€

Design embellishment is not necessarily bad, if it serves to help attract readers without detracting from the underlying story. But the problem with many infographics I see is that the embellishments are more prominent than the story, and often crowd it so much that not much story is told.  

The yardstick of success for any great infographic should be &quot;has this done the best job possible of attracting and then informing/engaging the audience?&quot;...and not &quot;does this look cool, or what?&quot;

Donâ€™t focus overly on the sizzle, to the exclusion of the sausage.</description>
		<content:encoded><![CDATA[<p>Regardless of differing definitions, Ryan&#8217;s comment &#8220;if you canâ€™t tell a compelling story with data without extraneous crap, youâ€™re doing it wrong&#8221; is spot on.  So is Pauloâ€™s comment  â€œitâ€™s all about failing or succeeding in reaching the (communicative) goalâ€</p>
<p>Design embellishment is not necessarily bad, if it serves to help attract readers without detracting from the underlying story. But the problem with many infographics I see is that the embellishments are more prominent than the story, and often crowd it so much that not much story is told.  </p>
<p>The yardstick of success for any great infographic should be &#8220;has this done the best job possible of attracting and then informing/engaging the audience?&#8221;&#8230;and not &#8220;does this look cool, or what?&#8221;</p>
<p>Donâ€™t focus overly on the sizzle, to the exclusion of the sausage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noah Iliinsky</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34409</link>
		<dc:creator>Noah Iliinsky</dc:creator>
		<pubDate>Fri, 25 Sep 2009 18:26:42 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34409</guid>
		<description>The four categories I prefer to use are:
1- information
2- redundant encoding (which is good, makes data easier to absorb)
3- decoration (makes the grapic more appealing, doesn&#039;t add or detract from the data)
4- noise (distracts, makes data harder to acquire)

These are from Pg 27 of Horton, W. (1991). Illustrating Computer Documentation: the Art of Presenting Information Graphically on Paper and Online. New York: John Wiley &amp; Sons, Inc.</description>
		<content:encoded><![CDATA[<p>The four categories I prefer to use are:<br />
1- information<br />
2- redundant encoding (which is good, makes data easier to absorb)<br />
3- decoration (makes the grapic more appealing, doesn&#8217;t add or detract from the data)<br />
4- noise (distracts, makes data harder to acquire)</p>
<p>These are from Pg 27 of Horton, W. (1991). Illustrating Computer Documentation: the Art of Presenting Information Graphically on Paper and Online. New York: John Wiley &amp; Sons, Inc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34408</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Fri, 25 Sep 2009 16:32:38 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34408</guid>
		<description>I have to admit that Iâ€™m a fan of Tufte.  Do I believe that we all need to bow in honor of the Almighty One and follow his every word?  No.  But I do think that people like him, and others such as Stephen Few, have articulated reasonable standards that graphic designers and analysts alike should strive to follow.  

Unfortunately, many websites and blogs continually post examples of what you might call â€œeye candyâ€.  I can appreciate some of the hard work and artistic endeavors that graphic designers put into creating some visually appealing images.  But first and foremost they are mostly just that: interesting images (or I guess â€œinformation aestheticsâ€ as you suggest).  In these cases then, letâ€™s recognize them just as examples of art or fun graphic design, and not as examples of good charts or data visualizations.         

In many cases (particularly with the folks at GOODâ€¦the recent one on crime statistics is pertinent example), charts contain simply too much extraneous, distracting and misleading (whether purposefully so or not) graphic elements or images.   Really these are just bells and whistles that at best distract the viewer from the data, or at worst skew the data for the viewer.  

So for me, it is hard for me then to differentiate between what is intended as â€œeye candyâ€ and chartjunk.  They are one in the same and should be avoided in good examples of charts.  Data presented simply, accurately and cleanly in a well-designed chart will tell a story sufficiently.</description>
		<content:encoded><![CDATA[<p>I have to admit that Iâ€™m a fan of Tufte.  Do I believe that we all need to bow in honor of the Almighty One and follow his every word?  No.  But I do think that people like him, and others such as Stephen Few, have articulated reasonable standards that graphic designers and analysts alike should strive to follow.  </p>
<p>Unfortunately, many websites and blogs continually post examples of what you might call â€œeye candyâ€.  I can appreciate some of the hard work and artistic endeavors that graphic designers put into creating some visually appealing images.  But first and foremost they are mostly just that: interesting images (or I guess â€œinformation aestheticsâ€ as you suggest).  In these cases then, letâ€™s recognize them just as examples of art or fun graphic design, and not as examples of good charts or data visualizations.         </p>
<p>In many cases (particularly with the folks at GOODâ€¦the recent one on crime statistics is pertinent example), charts contain simply too much extraneous, distracting and misleading (whether purposefully so or not) graphic elements or images.   Really these are just bells and whistles that at best distract the viewer from the data, or at worst skew the data for the viewer.  </p>
<p>So for me, it is hard for me then to differentiate between what is intended as â€œeye candyâ€ and chartjunk.  They are one in the same and should be avoided in good examples of charts.  Data presented simply, accurately and cleanly in a well-designed chart will tell a story sufficiently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Yau</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34406</link>
		<dc:creator>Nathan Yau</dc:creator>
		<pubDate>Fri, 25 Sep 2009 15:29:56 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34406</guid>
		<description>yes, in the context of analytical charts, eye candy is derogatory. But I&#039;m not restricting this to just that, which is what I was arguing. Call a work of art just a well-designed graph, and that&#039;s derogatory too.</description>
		<content:encoded><![CDATA[<p>yes, in the context of analytical charts, eye candy is derogatory. But I&#8217;m not restricting this to just that, which is what I was arguing. Call a work of art just a well-designed graph, and that&#8217;s derogatory too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Naomi B. Robbins</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34405</link>
		<dc:creator>Naomi B. Robbins</dc:creator>
		<pubDate>Fri, 25 Sep 2009 15:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34405</guid>
		<description>You must be thin. Candy is bad for my figure and for many of the figures I&#039;ve seen eye candy applied to.</description>
		<content:encoded><![CDATA[<p>You must be thin. Candy is bad for my figure and for many of the figures I&#8217;ve seen eye candy applied to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Peltier</title>
		<link>http://flowingdata.com/2009/09/25/chart-junk-vs-eye-candy-whats-the-difference/#comment-34404</link>
		<dc:creator>Jon Peltier</dc:creator>
		<pubDate>Fri, 25 Sep 2009 15:20:05 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=3023#comment-34404</guid>
		<description>Okay, in the broader sense of hot chicks, I guess eye candy means attractive. However, this isn&#039;t a fashion blog, it&#039;s a blog about graphics and visualization. In this context, &quot;eye candy&quot; is usually used in a derogatory way, for example:
&lt;a href=&quot;http://visualrevenue.com/blog/2008/10/google-analytics-motion-charts-eye-candy.html&quot; rel=&quot;nofollow&quot;&gt;Are Google Analytics Motion Charts just Eye Candy?&lt;/a&gt;
Comment to &lt;a href=&quot;http://sixrevisions.com/flashactionscript/10-useful-flash-components-for-graphing-data/&quot; rel=&quot;nofollow&quot;&gt;10 Useful Flash Components for Graphing Data&lt;/a&gt;: &quot;Why should I be spending money on commercial components? Most of them charge $$$ just for some eye candy.&quot;
In &lt;a href=&quot;http://www.stoyko.net/smithysmithy/archives/20&quot; rel=&quot;nofollow&quot;&gt;Information Dashboards (Book Review)&lt;/a&gt;: &quot;Yet, the dashboard should not contain visual embellishments that have no function. Such &#039;eye candy&#039; takes up valuable screen space and distracts the eye.&quot;</description>
		<content:encoded><![CDATA[<p>Okay, in the broader sense of hot chicks, I guess eye candy means attractive. However, this isn&#8217;t a fashion blog, it&#8217;s a blog about graphics and visualization. In this context, &#8220;eye candy&#8221; is usually used in a derogatory way, for example:<br />
<a href="http://visualrevenue.com/blog/2008/10/google-analytics-motion-charts-eye-candy.html" rel="nofollow">Are Google Analytics Motion Charts just Eye Candy?</a><br />
Comment to <a href="http://sixrevisions.com/flashactionscript/10-useful-flash-components-for-graphing-data/" rel="nofollow">10 Useful Flash Components for Graphing Data</a>: &#8220;Why should I be spending money on commercial components? Most of them charge $$$ just for some eye candy.&#8221;<br />
In <a href="http://www.stoyko.net/smithysmithy/archives/20" rel="nofollow">Information Dashboards (Book Review)</a>: &#8220;Yet, the dashboard should not contain visual embellishments that have no function. Such &#8216;eye candy&#8217; takes up valuable screen space and distracts the eye.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

