<?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: When Data Details Matter</title>
	<atom:link href="http://pharma-bi.com/2009/11/when-data-details-matter/feed/" rel="self" type="application/rss+xml" />
	<link>http://pharma-bi.com/2009/11/when-data-details-matter/</link>
	<description>Business Intelligence Blog</description>
	<lastBuildDate>Thu, 28 Apr 2011 14:44:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: admin</title>
		<link>http://pharma-bi.com/2009/11/when-data-details-matter/comment-page-1/#comment-526</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 24 Nov 2009 19:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://pharma-bi.com/?p=482#comment-526</guid>
		<description>Thanks, Joe.

This is a good example to show why knowing more details about the data definitely helps.  One would especially want to find out what could skew these results.  Here are a few thoughts:

* how are &quot;failure&quot; and &quot;malfunction&quot; defined?  I&#039;m no hardware technician, but I have to believe that some &quot;malfunctions&quot; are minor glitches while others are major issues that render the machine unusable.

* not everyone fesses up to &quot;accidental&quot; damage or damage that results from operator error - especially during a warranty period.  How did their study account for that?

* is the data based on computers that this company services?  If so, then the previous point is even more important.  Often it&#039;s easier just to send the machine in and get a replacement over night than to figure out whether software or other non-hardware issues created the problem. 

Yes, data details can be messy :)</description>
		<content:encoded><![CDATA[<p>Thanks, Joe.</p>
<p>This is a good example to show why knowing more details about the data definitely helps.  One would especially want to find out what could skew these results.  Here are a few thoughts:</p>
<p>* how are &#8220;failure&#8221; and &#8220;malfunction&#8221; defined?  I&#8217;m no hardware technician, but I have to believe that some &#8220;malfunctions&#8221; are minor glitches while others are major issues that render the machine unusable.</p>
<p>* not everyone fesses up to &#8220;accidental&#8221; damage or damage that results from operator error &#8211; especially during a warranty period.  How did their study account for that?</p>
<p>* is the data based on computers that this company services?  If so, then the previous point is even more important.  Often it&#8217;s easier just to send the machine in and get a replacement over night than to figure out whether software or other non-hardware issues created the problem. </p>
<p>Yes, data details can be messy <img src='http://pharma-bi.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Mako</title>
		<link>http://pharma-bi.com/2009/11/when-data-details-matter/comment-page-1/#comment-525</link>
		<dc:creator>Joe Mako</dc:creator>
		<pubDate>Tue, 24 Nov 2009 18:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://pharma-bi.com/?p=482#comment-525</guid>
		<description>Just saw this today: http://tumbledry.org/2009/11/20/when_information_overwhelms

Same situation you are describing. Representing lots of data as only a few data points makes the chart look simpler, but it can be deceiving.</description>
		<content:encoded><![CDATA[<p>Just saw this today: <a href="http://tumbledry.org/2009/11/20/when_information_overwhelms" rel="nofollow">http://tumbledry.org/2009/11/20/when_information_overwhelms</a></p>
<p>Same situation you are describing. Representing lots of data as only a few data points makes the chart look simpler, but it can be deceiving.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

