<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Visual.ly Blog &#187; Ross Perez</title>
	<atom:link href="http://blog.visual.ly/author/ross-perez/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.visual.ly</link>
	<description></description>
	<lastBuildDate>Fri, 17 May 2013 18:58:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Four Easy Visualization Mistakes to Avoid</title>
		<link>http://blog.visual.ly/data-visualization-mistakes-to-avoid/</link>
		<comments>http://blog.visual.ly/data-visualization-mistakes-to-avoid/#comments</comments>
		<pubDate>Tue, 10 Apr 2012 22:29:37 +0000</pubDate>
		<dc:creator>Ross Perez</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://blog.visual.ly/?p=3688</guid>
		<description><![CDATA[Creating a great visualization is not as hard as it seems. Provided you have some interesting data and an effective tool with which to visualize it, a little bit of thoughtful design will lead to a decent result. That said, there are some mistakes that are very easy to make, but can ruin even a thoughtfully-made piece. Here are four data visualization mistakes you should avoid. 1. Serving the Presentation Without the Data Which comes first: the presentation or the data? Oftentimes, in an effort to make a visualization more “interesting” or “cool”, designers will allow the presentation layer of a visualization to become more important than the data itself. The visualization captured below is an unfortunate casualty. A considerable amount of work went into it and there are parts that are informative, like the summary counters at the top left. However, without a scale or axis, the time series... <a class="more-link" href="http://blog.visual.ly/data-visualization-mistakes-to-avoid/">keep reading</a>]]></description>
			<content:encoded><![CDATA[<p>Creating a great visualization is not as hard as it seems. Provided you have some interesting data and an effective tool with which to visualize it, a little bit of thoughtful design will lead to a decent result. That said, there are some mistakes that are very easy to make, but can ruin even a thoughtfully-made piece. Here are four data visualization mistakes you should avoid.</p>
<h2>1. Serving the Presentation Without the Data</h2>
<p>Which comes first: the presentation or the data? Oftentimes, in an effort to make a visualization more “interesting” or “cool”, designers will allow the presentation layer of a visualization to become more important than the data itself. The visualization captured below is an unfortunate casualty. A considerable amount of work went into it and there are parts that are informative, like the summary counters at the top left. However, without a scale or axis, the time series on the bottom right is meaningless and the 3D chart in the center is even more opaque. Tooltips (pop ups) would help, if they were there. Instead, this looks amazing, but does little. </p>
<p><a href="http://blog.visual.ly/wp-content/uploads/2012/04/Screen-Shot-2012-04-10-at-2.53.28-PM.png?547b7b" title="NBA visualization"><img src="http://blog.visual.ly/wp-content/uploads/2012/04/NBA_thumb.jpg?547b7b" alt="" title="NBA_thumb" width="618" height="300" class="alignnone size-full wp-image-3744" /></a><br />
(<a href="http://wheredoesmytweetgo.com/#" target="_blank">source</a>)</p>
<h2>2. Showing Too Much Detail</h2>
<p>We all know the feeling of finding a dataset that is rich and easy to visualize, with numerous usable categorical and numerical fields. The temptation is to show everything at once, and allow users to drill down to the finest level of detail. Often, that actually makes a visualization superfluous because the user could simply look at the dataset itself if they wanted to see the finest level of detail. The trick, then, is to show enough detail to tell a story, but not so much that that story is convoluted and hidden. More data can be revealed as the reader progresses through the story. This visualization could have been great but there is so much detail it is hard to garner much information from it.</p>
<div class='visually_embed' data-category='Science' rel='interactive' ><img class='visually_embed_infographic' src='http://visually.visually.netdna-cdn.com/Citeology_4f05bba5e0375_w610.PNG' rel='http://visually.visually.netdna-cdn.com/Citeology_4f05bba5e0375.PNG' />
<div class='visually_embed_bar' > <span class='visually_embed_cycle'>Browse more <a href='http://visual.ly'>infographics</a>.</span></div>
<p><a id='visually_embed_view_more' target='_blank' href='http://visual.ly/citeology'></a>
<link rel='stylesheet' type='text/css' href='http://visual.ly/embeder/style.css' />		<script type='text/javascript' src='http://visual.ly/embeder/embed.js' > </script></div>
<p>(<a href="http://www.autodeskresearch.com/projects/citeology" target="_blank">source</a>)</p>
<h2>3. Not Explaining the Interactivity</h2>
<p>Enabling users to use and interact with a visualization makes it more engaging and engrossing. However, without telling them how to use that interactivity you risk limiting them to the initial view. How you label the interactivity is just as important as doing it in the first place. Usually, informing the user at the top of the visualization (or the part they will see first) is good practice, as is calling out the interaction on or near the tools that utilize it. This visualization is actually very interesting, but without labeling the interactivity, it is easy to overlook the fact that you can click the words at the bottom of the screen to change the view. Even using a common design concept such as underlining the words to associate a hyperlink, would have been helpful.</p>
<p><iframe src="http://www.visualizing.org/embedded/39118" width="620" height="450" frameborder="0" scrolling="no" marginheight="0" marginwidth="0"></iframe><br />
(<a href="http://www.visualizing.org/full-screen/39118" target="_blank">source</a>)</p>
<h2>4. Failing to Experiment</h2>
<p>Often, your first idea is not the best idea. It is easy to get excited about a visualization and then stick to the first vision that came to your mind when you saw the data. However, it is always best to start a visualization with a blank slate of ideas. Then shift perspectives: try ten or twenty different configurations and types of chart before you settle on one. The best part about experimentation is that it often forces new findings out of the data. This chart is not ineffective, but it would be much better if it used bar or even area charts to display its information. It is actually difficult to compare the magnitude of the different parts of the “blob” with this type of view. </p>
<p><a href="http://blog.visual.ly/wp-content/uploads/2012/04/Screen-Shot-2012-04-10-at-3.13.23-PM1.png?547b7b"><img src="http://blog.visual.ly/wp-content/uploads/2012/04/Screen-Shot-2012-04-10-at-3.13.23-PM1-618x470.png?547b7b" alt="" title="worldshapin" width="618" height="470" class="alignnone size-large wp-image-3802" /></a><br />
(<a href="http://www.worldshap.in/#/PH/BZ/KE/" target="_blank">source</a>)</p>
<p>There is no perfect visualization, but if you can manage to stay away from these four mistakes, yours will have a much better chance of getting close to perfection.</p>
<p><em>Ross Perez is a Data Analyst with <a href="http://www.tableausoftware.com/public/" target="_blank">Tableau Public</a>, a free tool which allows people to put their data on the web in interactive charts and graphs. You can connect with him on <a href="https://twitter.com/#!/letsviz" target="_blank">Twitter</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.visual.ly/data-visualization-mistakes-to-avoid/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>From Data to Story: Dissecting a Well-Made Visualization</title>
		<link>http://blog.visual.ly/creating-successful-data-visualization/</link>
		<comments>http://blog.visual.ly/creating-successful-data-visualization/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 23:39:50 +0000</pubDate>
		<dc:creator>Ross Perez</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://blog.visual.ly/?p=2394</guid>
		<description><![CDATA[Last week, Visual.ly published a blog post by Drew Skau, containing a Code of Ethics for data visualization, and ending with this succinct “Hippocratic oath” for data visualization professionals, which deserves to be explored further: I shall not use visualization to intentionally hide or confuse the truth which it is intended to portray. I will respect the great power visualization has in garnering wisdom and misleading the uninformed. I accept this responsibility willfully and without reservation, and promise to defend this oath against all enemies, both domestic and foreign. It is doubtful many people use visualization to intentionally mislead, but there are countless examples of visualizations and information design going wrong, anyway. This oath seems to carry the underlying message that one must create visualizations that not only use accurate data and avoid 3D pie charts, but are purposefully designed to tell a clear story and convey information effectively. In... <a class="more-link" href="http://blog.visual.ly/creating-successful-data-visualization/">keep reading</a>]]></description>
			<content:encoded><![CDATA[<p>Last week, Visual.ly published a blog post by <a href="http://blog.visual.ly/author/drew/">Drew Skau</a>, containing <a href="http://blog.visual.ly/a-code-of-ethics-for-data-visualization-professionals/">a Code of Ethics</a> for data visualization, and ending with this succinct “Hippocratic oath” for data visualization professionals, which deserves to be explored further:</p>
<p><em>I shall not use visualization to intentionally hide or confuse the truth which it is intended to portray. I will respect the great power visualization has in garnering wisdom and misleading the uninformed. I accept this responsibility willfully and without reservation, and promise to defend this oath against all enemies, both domestic and foreign.</em> <span id="more-2394"></span></p>
<p>It is doubtful many people use visualization to intentionally mislead, but there are <a href="http://www.perceptualedge.com/blog/?p=774" target="_blank">countless examples</a> of visualizations and information design going wrong, anyway. This oath seems to carry the underlying message that one must create visualizations that not only use accurate data and <a href="http://blog.visual.ly/2ds-company-3ds-a-crowd/">avoid 3D pie charts</a>, but are purposefully designed to tell a clear story and convey information effectively. In other words, any old graph will <em>not</em> do &#8212; every dataset deserves its own canvas.</p>
<p>The easiest way to explain this is to look at a well-made visualization and describe why it is effective. Obviously, no viz is perfect, so take this as a “let’s point out what works and what doesn’t” discussion, rather than a dissection of the viz archetype. </p>
<p>This one was originally published on <a href="http://www.geekwire.com/2011/tech-ipos-start-strong-pop-promptly-tank" target="_blank">Geekwire</a> and shows the (rather disappointing) collective performance of last year’s tech IPOs.<br />
<script type="text/javascript" src="http://public.tableausoftware.com/javascripts/api/viz_v1.js"></script>
<div class="tableauPlaceholder" style="width:604px; height:919px;"><noscript><a href="#"><img alt="The Common Path of 2011 Tech IPOs " src="http:&#47;&#47;public.tableausoftware.com&#47;static&#47;images&#47;te&#47;techfalls&#47;Dashboard1&#47;1_rss.png" style="border: none" /></a></noscript><object class="tableauViz" width="604" height="919" style="display:none;"><param name="host_url" value="http%3A%2F%2Fpublic.tableausoftware.com%2F" /><param name="site_root" value="" /><param name="name" value="techfalls&#47;Dashboard1" /><param name="tabs" value="no" /><param name="toolbar" value="yes" /><param name="static_image" value="http:&#47;&#47;public.tableausoftware.com&#47;static&#47;images&#47;te&#47;techfalls&#47;Dashboard1&#47;1.png" /><param name="animate_transition" value="yes" /><param name="display_static_image" value="yes" /><param name="display_spinner" value="yes" /><param name="display_overlay" value="yes" /></object></div>
<div style="width:604px;height:22px;padding:0px 10px 0px 0px;color:black;font:normal 8pt verdana,helvetica,arial,sans-serif;">
<div style="float:right; padding-right:8px;"><a href="http://www.tableausoftware.com/public?ref=http://public.tableausoftware.com/views/techfalls/Dashboard1" target="_blank">Powered by Tableau</a></div>
</div>
<p>The visualization tells a story: 2011 tech IPOs are tanking. The moment anyone looks at it, the story is clear, and there are a couple of reasons for that. </p>
<p>•	There is a clear title;<br />
•	The annotation clearly tells the story “Start Strong and Then Fall”;<br />
•	You can see the story played out in the line chart itself;<br />
•	To confirm the finding, you can examine the individual results for each company right underneath the line chart;<br />
•	The color legend is clear and also displayed (a common problem with many graphics).</p>
<p>This piece is particularly interesting because it tells a very simple story, yet the data itself is complex. Imagine the myriad ways that one could show the aggregated percent change for twenty different companies. The author of this visualization experimented with different views and arrived on the two that told the story most completely, most effortlessly. </p>
<p>And they did not stop at just completing the visualization. They labeled the interactivity “Include These Companies:” and explained the complex pieces in the visualization (the slider that filters companies based on trading days). Perhaps most importantly, they told us how they got the data and when they last updated it, so should we want to, we can go check it for ourselves.</p>
<p>Great visualization is not simply a chart that shows the data; it is a chart that tells an accurate and interesting story. Creating great visualizations is not easy, but by examining well-made examples, it becomes a little easier.</p>
<p>If you would like to learn more, Tableau has compiled a <a href="http://www.tableausoftware.com/public/community/best-practices" target="_blank">series of videos</a> on the Tableau Public site that go into significantly more detail.</p>
<p><em>Ross Perez is a data analyst at <a href="http://www.tableausoftware.com/" target="_blank">Tableau Software</a>. You can connect with him on <a href="http://twitter.com/#!/letsviz">Twitter</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.visual.ly/creating-successful-data-visualization/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using apc
Object Caching 297/323 objects using apc

Served from: blog.visual.ly @ 2013-05-19 13:27:06 -->