<?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: 3 Rules for Effective Report Design</title>
	<atom:link href="http://blog.instantcognition.com/visualization/2006/07/11/3-rules-for-effective-report-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.instantcognition.com/visualization/2006/07/11/3-rules-for-effective-report-design/</link>
	<description>a discussion of visual report design &#038; web analytics</description>
	<pubDate>Tue, 06 Jan 2009 22:24:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: A Gauge Chart That Works? &#187; Instant Cognition</title>
		<link>http://blog.instantcognition.com/visualization/2006/07/11/3-rules-for-effective-report-design/comment-page-1/#comment-22776</link>
		<dc:creator>A Gauge Chart That Works? &#187; Instant Cognition</dc:creator>
		<pubDate>Fri, 18 Jul 2008 06:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.instantcognition.com/?p=45#comment-22776</guid>
		<description>[...] I&#8217;ve said before that bullet charts faced a tough road. Basically, they are different enough to require end-user training which violates my the rules for effective chart design. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve said before that bullet charts faced a tough road. Basically, they are different enough to require end-user training which violates my the rules for effective chart design. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://blog.instantcognition.com/visualization/2006/07/11/3-rules-for-effective-report-design/comment-page-1/#comment-40</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Fri, 14 Jul 2006 16:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.instantcognition.com/?p=45#comment-40</guid>
		<description>Dylan,
Thanks for the question!
I actually disagree about the 'death and taxes' chart feeling that it also fails the undersanting rule, but that's for a different discussion.

As far as designing for efficiency goes - especially for a chart...

This tends to be a tool specific strategy, but in general the basic rules I discussed in the presentation are effective:

1. Abstract the data from the presentation. I tend to use Excel for reporting because of its ubiquity in the business world, so for Excel this means that I keep the data in a seperate worksheet from the report presentation layer (including charts) and leverage tools like named ranges, offset, vlookup, etc. so that once the data has been refreshed in the data sheet, the rest of the report is automatically updated (i.e. I don't have to update each component that uses the underlying data). 

2. Behind that, in the data sheet itself, I use various ways (web queries, pivot tables, etc) to make the data itself a refreshable query.

Again, there are numerous tactics that you can use, many of which are dependent on the platform you are working from, but for efficiency (and your sanity) if you can design the report in such a way that updated data can be pulled/queried through some more or less automated procedure, you've won the battle.

It's important to note that I generally have the luxury (as many of us do) where the data collection is more or less automated and then all we're doing is querying against a data warehouse, data mart, whatever. In the case of the Death and Taxes chart, I would bet that the author has to compile A LOT of data manually, in which case it's just going to take a serious manual effort to reproduce/update.

Not all charts are meant to be reproduced on a regular basis (Minard's is another example, could you imagine if he [somehow - go with me here] had the availability to try and update that chart week-by-week during the campaign? How impossible would that be?)

Ok, long story short...
1. Abstract the data from the presentation
2. Use refreshable queries for updating data
3. Make sure the data is easily available via an automated process - if it's not weigh the cost/benefit of making it so.
4. If it's too costly to make the data easily refreshable, weigh the cost/benefit of manual updates
5. If it's not worth it to manually collect/update the data consider alternative ways (that include points 2 and 3) to approach the same answer. If you can't do that, then you either have to make the chart a one-off or consider lengthening the lead time (cycle) to each update.

That probably doesn't answer your question fully, but as I stated at the beginning, the tactics used for efficiency, more than anything else tend to be platform-specific.

-Clint</description>
		<content:encoded><![CDATA[<p>Dylan,<br />
Thanks for the question!<br />
I actually disagree about the &#8216;death and taxes&#8217; chart feeling that it also fails the undersanting rule, but that&#8217;s for a different discussion.</p>
<p>As far as designing for efficiency goes - especially for a chart&#8230;</p>
<p>This tends to be a tool specific strategy, but in general the basic rules I discussed in the presentation are effective:</p>
<p>1. Abstract the data from the presentation. I tend to use Excel for reporting because of its ubiquity in the business world, so for Excel this means that I keep the data in a seperate worksheet from the report presentation layer (including charts) and leverage tools like named ranges, offset, vlookup, etc. so that once the data has been refreshed in the data sheet, the rest of the report is automatically updated (i.e. I don&#8217;t have to update each component that uses the underlying data). </p>
<p>2. Behind that, in the data sheet itself, I use various ways (web queries, pivot tables, etc) to make the data itself a refreshable query.</p>
<p>Again, there are numerous tactics that you can use, many of which are dependent on the platform you are working from, but for efficiency (and your sanity) if you can design the report in such a way that updated data can be pulled/queried through some more or less automated procedure, you&#8217;ve won the battle.</p>
<p>It&#8217;s important to note that I generally have the luxury (as many of us do) where the data collection is more or less automated and then all we&#8217;re doing is querying against a data warehouse, data mart, whatever. In the case of the Death and Taxes chart, I would bet that the author has to compile A LOT of data manually, in which case it&#8217;s just going to take a serious manual effort to reproduce/update.</p>
<p>Not all charts are meant to be reproduced on a regular basis (Minard&#8217;s is another example, could you imagine if he [somehow - go with me here] had the availability to try and update that chart week-by-week during the campaign? How impossible would that be?)</p>
<p>Ok, long story short&#8230;<br />
1. Abstract the data from the presentation<br />
2. Use refreshable queries for updating data<br />
3. Make sure the data is easily available via an automated process - if it&#8217;s not weigh the cost/benefit of making it so.<br />
4. If it&#8217;s too costly to make the data easily refreshable, weigh the cost/benefit of manual updates<br />
5. If it&#8217;s not worth it to manually collect/update the data consider alternative ways (that include points 2 and 3) to approach the same answer. If you can&#8217;t do that, then you either have to make the chart a one-off or consider lengthening the lead time (cycle) to each update.</p>
<p>That probably doesn&#8217;t answer your question fully, but as I stated at the beginning, the tactics used for efficiency, more than anything else tend to be platform-specific.</p>
<p>-Clint</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan Lewis</title>
		<link>http://blog.instantcognition.com/visualization/2006/07/11/3-rules-for-effective-report-design/comment-page-1/#comment-39</link>
		<dc:creator>Dylan Lewis</dc:creator>
		<pubDate>Fri, 14 Jul 2006 07:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.instantcognition.com/?p=45#comment-39</guid>
		<description>Hi Clint,

The death and taxes chart seems to  meet the first two principles easily.  However, it looks like the efficiency principle isn't met (the author is working on the 2007 version now.)

In your presentation you had many slides on Understanding and Action, but only 1 on efficiency.

How do you build efficiency into each chart you create?

Another way of asking this is, what are the top 10 techniques you abuse when building an efficient chart?

Thanks,
Dylan</description>
		<content:encoded><![CDATA[<p>Hi Clint,</p>
<p>The death and taxes chart seems to  meet the first two principles easily.  However, it looks like the efficiency principle isn&#8217;t met (the author is working on the 2007 version now.)</p>
<p>In your presentation you had many slides on Understanding and Action, but only 1 on efficiency.</p>
<p>How do you build efficiency into each chart you create?</p>
<p>Another way of asking this is, what are the top 10 techniques you abuse when building an efficient chart?</p>
<p>Thanks,<br />
Dylan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
