<?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: BI FAIL #2</title>
	<atom:link href="http://timoelliott.com/blog/2009/09/bi-fail-2.html/feed" rel="self" type="application/rss+xml" />
	<link>http://timoelliott.com/blog/2009/09/bi-fail-2.html</link>
	<description>Timo Elliott&#039;s Business Analytics Blog</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:24:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andreas</title>
		<link>http://timoelliott.com/blog/2009/09/bi-fail-2.html/comment-page-1#comment-3855</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Tue, 22 Sep 2009 23:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://timoelliott.com/blog/?p=1250#comment-3855</guid>
		<description>I can only say, what a poor visualization, to repeat myself:

Not only are slices/angles in a pie chart hard to distinguish for the human eye (humans can distinguish very well length and position, that is why 2-d bar charts, 2-d line charts, and xy charts work so well), but the 3-d look makes it even harder as it obscures slices, and the angles of the slices are distorted. 
 
I can only stronlgy recommend to go with a 2-d plain horizontal bar chart, where the bars are sorted in descending order according to the measure (see http://www.perceptualedge.com/example12.php)
 
Stephen Few has an excellent website for &quot;information visualization&quot;: www.perceptualedge.com</description>
		<content:encoded><![CDATA[<p>I can only say, what a poor visualization, to repeat myself:</p>
<p>Not only are slices/angles in a pie chart hard to distinguish for the human eye (humans can distinguish very well length and position, that is why 2-d bar charts, 2-d line charts, and xy charts work so well), but the 3-d look makes it even harder as it obscures slices, and the angles of the slices are distorted. </p>
<p>I can only stronlgy recommend to go with a 2-d plain horizontal bar chart, where the bars are sorted in descending order according to the measure (see <a href="http://www.perceptualedge.com/example12.php" rel="nofollow">http://www.perceptualedge.com/example12.php</a>)</p>
<p>Stephen Few has an excellent website for &#8220;information visualization&#8221;: <a href="http://www.perceptualedge.com" rel="nofollow">http://www.perceptualedge.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth Grimes</title>
		<link>http://timoelliott.com/blog/2009/09/bi-fail-2.html/comment-page-1#comment-3851</link>
		<dc:creator>Seth Grimes</dc:creator>
		<pubDate>Mon, 21 Sep 2009 14:43:04 +0000</pubDate>
		<guid isPermaLink="false">http://timoelliott.com/blog/?p=1250#comment-3851</guid>
		<description>Timo, thanks for picking up on my blog article.  There are significant BI failures on the GSAspending.gov that are less visible than the graphics problem caused by the misuse of the Google Chart API but as important if not more.  

The biggest is incomplete and missing information.  It is clear that records that are supposed to be and that are claimed to be there are not, for instance, about the U.S. government&#039;s fiscal year 2009 contract spending on USAspending.gov itself.  That&#039;s an example of missing information where there&#039;s no hint that it&#039;s missing.  Incomplete information: the site doesn&#039;t include subcontract records.  My *guesstimate* is that double-digit-percentage U.S. federal government contracting revenue goes to subcontractors.  Without this information, the site is incomplete and gives a very misleading picture where federal money goes.  

Seth</description>
		<content:encoded><![CDATA[<p>Timo, thanks for picking up on my blog article.  There are significant BI failures on the GSAspending.gov that are less visible than the graphics problem caused by the misuse of the Google Chart API but as important if not more.  </p>
<p>The biggest is incomplete and missing information.  It is clear that records that are supposed to be and that are claimed to be there are not, for instance, about the U.S. government&#8217;s fiscal year 2009 contract spending on USAspending.gov itself.  That&#8217;s an example of missing information where there&#8217;s no hint that it&#8217;s missing.  Incomplete information: the site doesn&#8217;t include subcontract records.  My *guesstimate* is that double-digit-percentage U.S. federal government contracting revenue goes to subcontractors.  Without this information, the site is incomplete and gives a very misleading picture where federal money goes.  </p>
<p>Seth</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 282/285 objects using disk: basic

Served from: timoelliott.com @ 2012-02-11 07:34:18 -->
