<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Spreadsheet Design?</title>
	<link>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/</link>
	<description></description>
	<pubDate>Fri, 29 Aug 2008 00:45:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.1</generator>

	<item>
		<title>by: AdamV</title>
		<link>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-49500</link>
		<pubDate>Thu, 19 Jun 2008 21:11:29 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-49500</guid>
					<description>Looks like the spammers got here before me...

I like this approach, I tend to do similar things, particularly marking cells to be filled in, and I also tend to choose pastel yellow for this. If there are different users / departments then I use some kind of colour code to indicate who puts what where (a bit like the &quot;office use only&quot; bit at the bottom of a paper form). Cells for data entry I would usually put validation on as well, if a simple ruleset exists.

I also use simple error indicators, such as a ! next to invalid cells and then a check cell at the top which looks for any errors and puts a big red banner across the whole screen screaming &quot;something is wrong! check your data entry&quot; (actually usually wording a bit more helpful than that). I have used conditional formatting to make the shading of entry cells clear once all cells have a valid (and hopefully correct) entry in them. This makes much cleaner printed versions if needed.

I have had couple of cases where one cell's entry makes a big difference to the whole of the rest of a sheet, for example choosing a currency for an expenses claim form. In this case I used conditional formatting to colour the entry cells differently depending on what units they were in to make it really obvious. I changed the labels as well of course to give the right prompt.

Keep up the great blog!</description>
		<content:encoded><![CDATA[<p>Looks like the spammers got here before me&#8230;</p>
<p>I like this approach, I tend to do similar things, particularly marking cells to be filled in, and I also tend to choose pastel yellow for this. If there are different users / departments then I use some kind of colour code to indicate who puts what where (a bit like the &#8220;office use only&#8221; bit at the bottom of a paper form). Cells for data entry I would usually put validation on as well, if a simple ruleset exists.</p>
<p>I also use simple error indicators, such as a ! next to invalid cells and then a check cell at the top which looks for any errors and puts a big red banner across the whole screen screaming &#8220;something is wrong! check your data entry&#8221; (actually usually wording a bit more helpful than that). I have used conditional formatting to make the shading of entry cells clear once all cells have a valid (and hopefully correct) entry in them. This makes much cleaner printed versions if needed.</p>
<p>I have had couple of cases where one cell&#8217;s entry makes a big difference to the whole of the rest of a sheet, for example choosing a currency for an expenses claim form. In this case I used conditional formatting to colour the entry cells differently depending on what units they were in to make it really obvious. I changed the labels as well of course to give the right prompt.</p>
<p>Keep up the great blog!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: TJ McCue</title>
		<link>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-45473</link>
		<pubDate>Fri, 09 May 2008 22:29:14 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-45473</guid>
					<description>Oops! Sorry, added a comma.  http://www.tableausoftware.com/fast-analytics</description>
		<content:encoded><![CDATA[<p>Oops! Sorry, added a comma.  <a href='http://www.tableausoftware.com/fast-analytics' rel='nofollow'>http://www.tableausoftware.com/fast-analytics</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: TJ McCue</title>
		<link>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-45363</link>
		<pubDate>Thu, 08 May 2008 19:08:51 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-45363</guid>
					<description>Hi, I just found your site, while researching Excel Data Experts.    I really liked your post about spreadsheet design.  Are you familiar with other excel data visualization sites?  I'd enjoy connecting by email if you do.  My client's site is http://www.tableausoftware.com/fast-analytics, if you're interested.  Keep up the blog posts -- good stuff!</description>
		<content:encoded><![CDATA[<p>Hi, I just found your site, while researching Excel Data Experts.    I really liked your post about spreadsheet design.  Are you familiar with other excel data visualization sites?  I&#8217;d enjoy connecting by email if you do.  My client&#8217;s site is <a href='http://www.tableausoftware.com/fast-analytics' rel='nofollow'>http://www.tableausoftware.com/fast-analytics</a>, if you&#8217;re interested.  Keep up the blog posts &#8212; good stuff!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jayson</title>
		<link>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-43664</link>
		<pubDate>Mon, 21 Apr 2008 17:16:54 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2008/04/21/spreadsheet-design/#comment-43664</guid>
					<description>These are great ideas, but clients sometimes have different ideas.  And clients are the ones paying the bills.

I actually prefer (sometimes) having summary formulas at the top of a sheet with the heavy duty calculation further down for reference if needed.

For one client, one sheet would never work (SpreadsheetStyle suggestion).  4 pages of detailed input, with 35+ pages of calculations, and 10 summary views.  Complicated problems require a lot of detail for clients that want to be able to follow the entire calculation process.  The challenge then becomes one of making it easy for calculations to be followed.

I agree with the suggests you list here and on the links, but alas, clients have much different ideas.</description>
		<content:encoded><![CDATA[<p>These are great ideas, but clients sometimes have different ideas.  And clients are the ones paying the bills.</p>
<p>I actually prefer (sometimes) having summary formulas at the top of a sheet with the heavy duty calculation further down for reference if needed.</p>
<p>For one client, one sheet would never work (SpreadsheetStyle suggestion).  4 pages of detailed input, with 35+ pages of calculations, and 10 summary views.  Complicated problems require a lot of detail for clients that want to be able to follow the entire calculation process.  The challenge then becomes one of making it easy for calculations to be followed.</p>
<p>I agree with the suggests you list here and on the links, but alas, clients have much different ideas.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
