<?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: May you chop axes? No&#8230;you must!</title>
	<atom:link href="http://blog.bissantz.com/index.php/you-must-chop-axes/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.bissantz.com/you-must-chop-axes</link>
	<description>Bissantz ponders</description>
	<lastBuildDate>Mon, 05 Jul 2010 13:53:30 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nicolas Bissantz</title>
		<link>http://blog.bissantz.com/you-must-chop-axes/comment-page-1#comment-8749</link>
		<dc:creator>Nicolas Bissantz</dc:creator>
		<pubDate>Fri, 27 Feb 2009 18:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bissantz.com/?p=384#comment-8749</guid>
		<description>Our dog-matic &lt;a href=&quot;http://www.bella-consults.com/&quot; rel=&quot;nofollow&quot;&gt;Bella&lt;/a&gt; would say: Always consider your design first, before daring to &lt;a href=&quot;http://www.bella-consults.com/chopping&quot; rel=&quot;nofollow&quot;&gt;bend &lt;/a&gt;my &lt;a href=&quot;http://www.bella-consults.com/my-law-of-proportions&quot; rel=&quot;nofollow&quot;&gt;Bella Reporting Standards&lt;/a&gt;. Paresh, I don&#039;t know your data, but it seems high delivery accuracy percentages is what you would expect. So, maybe you better show deviations from average or expected values and everything will be fine. Maybe this &lt;a href=&quot;http://blog.bissantz.com/rough-cut-bars&quot; rel=&quot;nofollow&quot;&gt;example&lt;/a&gt; is clarifying how this could be done.</description>
		<content:encoded><![CDATA[<p>Our dog-matic <a href="http://www.bella-consults.com/" rel="nofollow">Bella</a> would say: Always consider your design first, before daring to <a href="http://www.bella-consults.com/chopping" rel="nofollow">bend </a>my <a href="http://www.bella-consults.com/my-law-of-proportions" rel="nofollow">Bella Reporting Standards</a>. Paresh, I don&#8217;t know your data, but it seems high delivery accuracy percentages is what you would expect. So, maybe you better show deviations from average or expected values and everything will be fine. Maybe this <a href="http://blog.bissantz.com/rough-cut-bars" rel="nofollow">example</a> is clarifying how this could be done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paresh</title>
		<link>http://blog.bissantz.com/you-must-chop-axes/comment-page-1#comment-8745</link>
		<dc:creator>paresh</dc:creator>
		<pubDate>Fri, 27 Feb 2009 15:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bissantz.com/?p=384#comment-8745</guid>
		<description>Hi Nicolas,

I recently was doing a bar chart for delivery accuracy percentage for a number of stores where the percentages vary very marginally, between 95% to 99.99%. When the bar chart is part of the dashboard, the differences almost disappear. In this situation would it not be advisable to start from say 70. yes the rule of proportionality will be broken but the differences would clearly stand out.</description>
		<content:encoded><![CDATA[<p>Hi Nicolas,</p>
<p>I recently was doing a bar chart for delivery accuracy percentage for a number of stores where the percentages vary very marginally, between 95&#160;% to 99.99&#160;%. When the bar chart is part of the dashboard, the differences almost disappear. In this situation would it not be advisable to start from say 70. yes the rule of proportionality will be broken but the differences would clearly stand out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Hampshire</title>
		<link>http://blog.bissantz.com/you-must-chop-axes/comment-page-1#comment-8707</link>
		<dc:creator>Stephen Hampshire</dc:creator>
		<pubDate>Thu, 26 Feb 2009 12:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bissantz.com/?p=384#comment-8707</guid>
		<description>I like Tufte&#039;s advice to aim for an average angle of 45 degrees (bumpy, not spiky, not flat). That tends to give a picture that lets us read the true story most accurately.

That said, I think Chad&#039;s point is very important - we must be consistent when the audience may be comparing between charts.</description>
		<content:encoded><![CDATA[<p>I like Tufte&#8217;s advice to aim for an average angle of 45 degrees (bumpy, not spiky, not flat). That tends to give a picture that lets us read the true story most accurately.</p>
<p>That said, I think Chad&#8217;s point is very important&#160;&#8211; we must be consistent when the audience may be comparing between charts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://blog.bissantz.com/you-must-chop-axes/comment-page-1#comment-8657</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Tue, 24 Feb 2009 15:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bissantz.com/?p=384#comment-8657</guid>
		<description>Very valid points.

Personally I first determine who my audience is...as you mention managing directors should be capable of reading the axis and not (pardon the pun) between the lines.

Another point, is that should you want to actually illustrate significant movements/difference etc. then I may chop the axes, and vice versa.

I would argue it wholly as it depends on the situation at the time. Unfortunately in this case, there&#039;s no golden rule.</description>
		<content:encoded><![CDATA[<p>Very valid points.</p>
<p>Personally I first determine who my audience is&#8230;as you mention managing directors should be capable of reading the axis and not (pardon the pun) between the lines.</p>
<p>Another point, is that should you want to actually illustrate significant movements/difference etc. then I may chop the axes, and vice versa.</p>
<p>I would argue it wholly as it depends on the situation at the time. Unfortunately in this case, there&#8217;s no golden rule.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Bissantz</title>
		<link>http://blog.bissantz.com/you-must-chop-axes/comment-page-1#comment-8648</link>
		<dc:creator>Nicolas Bissantz</dc:creator>
		<pubDate>Tue, 24 Feb 2009 11:00:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bissantz.com/?p=384#comment-8648</guid>
		<description>You are absolutely right, but the &quot;always include zero&quot; commandment often enough makes it even worse. Why not &lt;a href=&quot;/rabid-tigers-part-2&quot; rel=&quot;nofollow&quot;&gt;use logarithms&lt;/a&gt;?</description>
		<content:encoded><![CDATA[<p>You are absolutely right, but the &#8220;always include zero&#8221; commandment often enough makes it even worse. Why not <a href="/rabid-tigers-part-2" rel="nofollow">use logarithms</a>?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://blog.bissantz.com/you-must-chop-axes/comment-page-1#comment-8628</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Mon, 23 Feb 2009 21:23:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bissantz.com/?p=384#comment-8628</guid>
		<description>Where this (chopping axes) really goes wrong is when multiple graphs are presented -- for example, if there&#039;s one graph per category, or separate graphs showing different metrics (say, sales and costs). Not including the zero point is quite dangerous in this case because readers can&#039;t tell how the changes in categories or metrics compare to each other.</description>
		<content:encoded><![CDATA[<p>Where this (chopping axes) really goes wrong is when multiple graphs are presented &#8212; for example, if there&#8217;s one graph per category, or separate graphs showing different metrics (say, sales and costs). Not including the zero point is quite dangerous in this case because readers can&#8217;t tell how the changes in categories or metrics compare to each other.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

