<?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 Good and Bad of Bullet Graphs</title>
	<atom:link href="http://datapigtechnologies.com/blog/index.php/the-good-and-bad-of-bullet-graphs/feed/" rel="self" type="application/rss+xml" />
	<link>http://datapigtechnologies.com/blog/index.php/the-good-and-bad-of-bullet-graphs/</link>
	<description>A DataPig Technologies Blog</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:53:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Datapig</title>
		<link>http://datapigtechnologies.com/blog/index.php/the-good-and-bad-of-bullet-graphs/comment-page-1/#comment-2293</link>
		<dc:creator>Datapig</dc:creator>
		<pubDate>Fri, 09 Oct 2009 18:35:22 +0000</pubDate>
		<guid isPermaLink="false">http://datapigtechnologies.com/blog/?p=1081#comment-2293</guid>
		<description>Stephen:  Damn you and your clear and well-thought-out remarks!  You have an uncanny way of changing minds.  

I do agree that merits of a graph should not be judged by the audience&#039;s ability to understand it without instruction.  

My only feeble push-back is that the corporate environment doesn&#039;t allow for luxuries such as traing and think-time.  

As I ponder your remarks, it occurs to me that in 5 years, this conversation will be moot.  With the adoption of bullet graphs in a myriad of software (future versions of Xcelsius and Excel being the big ones in my world) , a large majority of business users will have enough exposure as to make them second nature.  

Think of all the money you could have made if you had not given the design away.  I guess the joke&#039;s on you Mr. &quot;well-thought-out remarks&quot; ;-)</description>
		<content:encoded><![CDATA[<p>Stephen:  Damn you and your clear and well-thought-out remarks!  You have an uncanny way of changing minds.  </p>
<p>I do agree that merits of a graph should not be judged by the audience&#8217;s ability to understand it without instruction.  </p>
<p>My only feeble push-back is that the corporate environment doesn&#8217;t allow for luxuries such as traing and think-time.  </p>
<p>As I ponder your remarks, it occurs to me that in 5 years, this conversation will be moot.  With the adoption of bullet graphs in a myriad of software (future versions of Xcelsius and Excel being the big ones in my world) , a large majority of business users will have enough exposure as to make them second nature.  </p>
<p>Think of all the money you could have made if you had not given the design away.  I guess the joke&#8217;s on you Mr. &#8220;well-thought-out remarks&#8221; <img src='http://datapigtechnologies.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Few</title>
		<link>http://datapigtechnologies.com/blog/index.php/the-good-and-bad-of-bullet-graphs/comment-page-1/#comment-2292</link>
		<dc:creator>Stephen Few</dc:creator>
		<pubDate>Fri, 09 Oct 2009 17:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://datapigtechnologies.com/blog/?p=1081#comment-2292</guid>
		<description>DataPig, et. al.,

I&#039;ve introduced the bullet graph to many individuals and groups over the last few years. What I&#039;ve found is that it takes less than a minute to teach people how to read it. It takes a great deal more time to teach people how to read other useful forms of data display, such as box plots and scatter plots, but it&#039;s worth the time when the graph can tell powerful stories. When Hans Rosling of GapMinder presents information to audiences throughout the world using an animated bubble chart, even people who might ordinarily run from scatter plots or bubble charts in horror become captivated because Rosling introduces the chart in a way that they can easily understand. The point that I&#039;m trying to make is that the merits of a graph should not be judged by the audience&#039;s ability to understand it without instruction. The first time William Playfair used a bar graph, he had to tell people how to read it. Merit ought to be judged by the graph&#039;s ability to tell the story it is meant to tell--clearly, accurately, efficiently, and without undue effort by the viewer. 

A series of background colors that vary by intensity from dark to light is an intuitive use of color for representing a quantitative or ordinal scale, such as poor, satisfactory, and good performance. People in countries that use red, yellow, and green traffic lights to convey these meanings don&#039;t understand them because they are intuitive, but because they have learned these meanings. This took more effort to learn originally (although no one remembers the effort) than it takes to learn that the lighter the color is, the better the performance is.

The bullet graph was designed for a very specific purpose: to present a single measure of what&#039;s going on, compared to something such as a target, within the context of qualitative states (for example, poor, satisfactory, and good performance). It was developed to present this information in a manner that allows people to scan a great deal of information on a dashboard to quickly get a sense of how things are going. The bullet graph is only one of many effective ways to display information on a dashboard. When other forms of display are better suited to the task, they should be used. 

It&#039;s been fun to observe the ways that the humble bullet graph has been successfully used to solve real problems and how it has evolved to solve additional problems that I hadn&#039;t anticipated when I first introduced it. Discussions like the one we&#039;re having here on this blog will help to make this happen. Discussions like this might also plant the seeds of entirely new forms of display that have yet to be developed.

Steve</description>
		<content:encoded><![CDATA[<p>DataPig, et. al.,</p>
<p>I&#8217;ve introduced the bullet graph to many individuals and groups over the last few years. What I&#8217;ve found is that it takes less than a minute to teach people how to read it. It takes a great deal more time to teach people how to read other useful forms of data display, such as box plots and scatter plots, but it&#8217;s worth the time when the graph can tell powerful stories. When Hans Rosling of GapMinder presents information to audiences throughout the world using an animated bubble chart, even people who might ordinarily run from scatter plots or bubble charts in horror become captivated because Rosling introduces the chart in a way that they can easily understand. The point that I&#8217;m trying to make is that the merits of a graph should not be judged by the audience&#8217;s ability to understand it without instruction. The first time William Playfair used a bar graph, he had to tell people how to read it. Merit ought to be judged by the graph&#8217;s ability to tell the story it is meant to tell&#8211;clearly, accurately, efficiently, and without undue effort by the viewer. </p>
<p>A series of background colors that vary by intensity from dark to light is an intuitive use of color for representing a quantitative or ordinal scale, such as poor, satisfactory, and good performance. People in countries that use red, yellow, and green traffic lights to convey these meanings don&#8217;t understand them because they are intuitive, but because they have learned these meanings. This took more effort to learn originally (although no one remembers the effort) than it takes to learn that the lighter the color is, the better the performance is.</p>
<p>The bullet graph was designed for a very specific purpose: to present a single measure of what&#8217;s going on, compared to something such as a target, within the context of qualitative states (for example, poor, satisfactory, and good performance). It was developed to present this information in a manner that allows people to scan a great deal of information on a dashboard to quickly get a sense of how things are going. The bullet graph is only one of many effective ways to display information on a dashboard. When other forms of display are better suited to the task, they should be used. </p>
<p>It&#8217;s been fun to observe the ways that the humble bullet graph has been successfully used to solve real problems and how it has evolved to solve additional problems that I hadn&#8217;t anticipated when I first introduced it. Discussions like the one we&#8217;re having here on this blog will help to make this happen. Discussions like this might also plant the seeds of entirely new forms of display that have yet to be developed.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oakhome</title>
		<link>http://datapigtechnologies.com/blog/index.php/the-good-and-bad-of-bullet-graphs/comment-page-1/#comment-2291</link>
		<dc:creator>Oakhome</dc:creator>
		<pubDate>Fri, 09 Oct 2009 16:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://datapigtechnologies.com/blog/?p=1081#comment-2291</guid>
		<description>There must be something wrong with me. I had no problems understanding what the bullet graph was showing. Then again, I&#039;m not a Manager.</description>
		<content:encoded><![CDATA[<p>There must be something wrong with me. I had no problems understanding what the bullet graph was showing. Then again, I&#8217;m not a Manager.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: datapig</title>
		<link>http://datapigtechnologies.com/blog/index.php/the-good-and-bad-of-bullet-graphs/comment-page-1/#comment-2288</link>
		<dc:creator>datapig</dc:creator>
		<pubDate>Fri, 09 Oct 2009 05:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://datapigtechnologies.com/blog/?p=1081#comment-2288</guid>
		<description>Liu:  Thanks for the link.  Thank god for screenshots, especially on this site.  

This has definately opened up a few ideas for me.</description>
		<content:encoded><![CDATA[<p>Liu:  Thanks for the link.  Thank god for screenshots, especially on this site.  </p>
<p>This has definately opened up a few ideas for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Weir</title>
		<link>http://datapigtechnologies.com/blog/index.php/the-good-and-bad-of-bullet-graphs/comment-page-1/#comment-2286</link>
		<dc:creator>Jeff Weir</dc:creator>
		<pubDate>Fri, 09 Oct 2009 02:59:35 +0000</pubDate>
		<guid isPermaLink="false">http://datapigtechnologies.com/blog/?p=1081#comment-2286</guid>
		<description>If I had to choose between a bullet  graph and a sparkline with a quantitative band (i.e. a sparkline with a horizontal band denoting some kind of &#039;acceptable range&#039;), I&#039;d probably pick the sparkline. This is because then you get to see how the thing you are tracking has changed over time. Bullet graphs only show what&#039;s happenning right now. 

That said, bullet graphs have a cooler name than sparklines.Try saying  &quot;I&#039;m gonna pop a bullet graph in your ass&quot; and you&#039;ll hear what I mean. 

If I had to choose between a big dial, and a bullet graph, then I&#039;d choose the bullet graph.

On using multiple bullet graphs on one chart, when I asked Stephen Few about it he said &quot;When all of the measures share the same quantitative scale and the same qualitative ranges (for example, the same ranges of good, satisfactory, and poor performance), there is no real reason to use bullet graphs. I think it would usually work best to use a single bar graph with continuous qualitative fill colors in the background. This would make it obvious that the measures belong together and can be compared in all respects.&quot;

However, if the quantitive scales differ, then bullet graphs might be a good way to report.  For example, in Few&#039;s bullet graph design spec at http://www.perceptualedge.com/articles/misc/Bullet_Graph_Design_Spec.pdf you can see at the top of page 2, there&#039;s 5 bullet graphs per example and each one has a different quantative scale (i.e. different target bands). 

So using a solid band option wouldn&#039;t work here.</description>
		<content:encoded><![CDATA[<p>If I had to choose between a bullet  graph and a sparkline with a quantitative band (i.e. a sparkline with a horizontal band denoting some kind of &#8216;acceptable range&#8217;), I&#8217;d probably pick the sparkline. This is because then you get to see how the thing you are tracking has changed over time. Bullet graphs only show what&#8217;s happenning right now. </p>
<p>That said, bullet graphs have a cooler name than sparklines.Try saying  &#8220;I&#8217;m gonna pop a bullet graph in your ass&#8221; and you&#8217;ll hear what I mean. </p>
<p>If I had to choose between a big dial, and a bullet graph, then I&#8217;d choose the bullet graph.</p>
<p>On using multiple bullet graphs on one chart, when I asked Stephen Few about it he said &#8220;When all of the measures share the same quantitative scale and the same qualitative ranges (for example, the same ranges of good, satisfactory, and poor performance), there is no real reason to use bullet graphs. I think it would usually work best to use a single bar graph with continuous qualitative fill colors in the background. This would make it obvious that the measures belong together and can be compared in all respects.&#8221;</p>
<p>However, if the quantitive scales differ, then bullet graphs might be a good way to report.  For example, in Few&#8217;s bullet graph design spec at <a href="http://www.perceptualedge.com/articles/misc/Bullet_Graph_Design_Spec.pdf" rel="nofollow">http://www.perceptualedge.com/articles/misc/Bullet_Graph_Design_Spec.pdf</a> you can see at the top of page 2, there&#8217;s 5 bullet graphs per example and each one has a different quantative scale (i.e. different target bands). </p>
<p>So using a solid band option wouldn&#8217;t work here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

