<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Oversimplification is confusing (or, Don&#8217;t ask stupid questions)</title>
	<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/</link>
	<description>on programming, usability, and design; by Patrick Dubroy</description>
	<pubDate>Wed, 20 Aug 2008 13:35:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Michal T</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3752</link>
		<pubDate>Fri, 28 Sep 2007 19:12:19 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3752</guid>
					<description>&lt;p&gt;What I really don't understand is this: why the extra dialog? The setting has little impact - either adds a small performance penalty to loads and saves, or makes a few old apps not compatibile with the new files. &lt;/p&gt;

&lt;p&gt;If Photoshop asked that (and gave a short explanation) the first time I saved a file, I would consider it a thoughtful, professional move from Adobe. But a dialog on every save? Please. I blame lazy developers and/or lack of coherent vision from project management.&lt;/p&gt;

&lt;p&gt;This should be a standard Yes/No dialog with a "Don't ask again" checkbox.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What I really don&#8217;t understand is this: why the extra dialog? The setting has little impact - either adds a small performance penalty to loads and saves, or makes a few old apps not compatibile with the new files. </p>
<p>If Photoshop asked that (and gave a short explanation) the first time I saved a file, I would consider it a thoughtful, professional move from Adobe. But a dialog on every save? Please. I blame lazy developers and/or lack of coherent vision from project management.</p>
<p>This should be a standard Yes/No dialog with a &#8220;Don&#8217;t ask again&#8221; checkbox.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3741</link>
		<pubDate>Fri, 28 Sep 2007 15:05:08 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3741</guid>
					<description>&lt;p&gt;Michal:&lt;/p&gt;

&lt;p&gt;Thanks for the pointer. That's about what I figured. Although I never would have guessed that this compatibility stretched all the way back to Photoshop 2.5! 14 years of compatibility -- even Microsoft doesn't bother with that. Wow.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Michal:</p>
<p>Thanks for the pointer. That&#8217;s about what I figured. Although I never would have guessed that this compatibility stretched all the way back to Photoshop 2.5! 14 years of compatibility &#8212; even Microsoft doesn&#8217;t bother with that. Wow.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Michal T</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3733</link>
		<pubDate>Fri, 28 Sep 2007 08:40:09 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3733</guid>
					<description>&lt;p&gt;In case someone wants to know what that checkbox really does, here's a fragment of http://www.adobepress.com/articles/article.aspx?p=30163&#38;seqNum=8&#38;rl=1 (from Google's cache, since it's unavilable atm).&lt;/p&gt;

&lt;p&gt;Always Maximize Compatibility for Photoshop (PSD) Files. [..] Basically, when this checkbox is turned on, Photoshop saves a flattened version of your layered image along with the layered version. The result: if you give the file to someone who is using Photoshop 2.5 (we don't know anyone who does), they can open it. [..] The main problem is that this feature (which is on by default) makes your image sizes larger on disk (sometimes several times larger) than they would otherwise be. [..] leave it turned on if you're using some other program that claims to open native Photoshop files, like Macromedia FreeHand, but which requires this flattened version to work.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>In case someone wants to know what that checkbox really does, here&#8217;s a fragment of http://www.adobepress.com/articles/article.aspx?p=30163&amp;seqNum=8&amp;rl=1 (from Google&#8217;s cache, since it&#8217;s unavilable atm).</p>
<p>Always Maximize Compatibility for Photoshop (PSD) Files. [..] Basically, when this checkbox is turned on, Photoshop saves a flattened version of your layered image along with the layered version. The result: if you give the file to someone who is using Photoshop 2.5 (we don&#8217;t know anyone who does), they can open it. [..] The main problem is that this feature (which is on by default) makes your image sizes larger on disk (sometimes several times larger) than they would otherwise be. [..] leave it turned on if you&#8217;re using some other program that claims to open native Photoshop files, like Macromedia FreeHand, but which requires this flattened version to work.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3559</link>
		<pubDate>Mon, 24 Sep 2007 05:30:22 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3559</guid>
					<description>&lt;p&gt;Gerry: I think maybe that restaurant is operating on the 37 Signals "&lt;a href="http://gettingreal.37signals.com/toc.php" rel="nofollow"&gt;Getting Real&lt;/a&gt;" philosophy!&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;Do less than your competitors to beat them. Solve the simple problems and leave 
  the hairy, difficult, nasty problems to everyone else. Instead of oneupping, 
  try one-downing. Instead of outdoing, try underdoing.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Instead of making soup, just make broth -- let your customers tear up the bread into tiny chunks for the soup!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Gerry: I think maybe that restaurant is operating on the 37 Signals &#8220;<a href="http://gettingreal.37signals.com/toc.php" rel="nofollow">Getting Real</a>&#8221; philosophy!</p>
<blockquote>
<p>Do less than your competitors to beat them. Solve the simple problems and leave<br />
  the hairy, difficult, nasty problems to everyone else. Instead of oneupping,<br />
  try one-downing. Instead of outdoing, try underdoing.</p>
</blockquote>
<p>Instead of making soup, just make broth &#8212; let your customers tear up the bread into tiny chunks for the soup!</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Gerry</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3557</link>
		<pubDate>Mon, 24 Sep 2007 04:09:57 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3557</guid>
					<description>&lt;p&gt;I clicked here from Signal vs Noise, and was surprised to be brought to your blog! Even more surprising is that my experimentation in Chinese food is featured in your blog entry. Maybe there's another UI principle in the fact that the restaurant made me, the customer, assist in making the soup? Don't make users do stuff that the computer can do automatically? On the other hand, I did feel a little pride in the fact that my handiwork went into the soup.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I clicked here from Signal vs Noise, and was surprised to be brought to your blog! Even more surprising is that my experimentation in Chinese food is featured in your blog entry. Maybe there&#8217;s another UI principle in the fact that the restaurant made me, the customer, assist in making the soup? Don&#8217;t make users do stuff that the computer can do automatically? On the other hand, I did feel a little pride in the fact that my handiwork went into the soup.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3469</link>
		<pubDate>Fri, 21 Sep 2007 20:36:38 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3469</guid>
					<description>&lt;p&gt;e: Yep, you're right. As I wrote in &lt;a href="http://dubroy.com/blog/2007/09/21/making-up-my-mind-about-oversimplification/" rel="nofollow"&gt;my post today&lt;/a&gt;: in retrospect,  I don't think "oversimplification is confusing" was really the problem here. The problem was either (a) not enough simplification, or (b) the &lt;em&gt;wrong&lt;/em&gt; simplification.&lt;/p&gt;

&lt;p&gt;"Provide users with enough explanation to make an informed decision" is a good maxim, but I would add "or don't let them make the decision at all."&lt;/p&gt;

&lt;p&gt;Another way of describing what happened here is that by leaving information out (which is often done in pursuit of simplification) they actually made things more complicated.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>e: Yep, you&#8217;re right. As I wrote in <a href="http://dubroy.com/blog/2007/09/21/making-up-my-mind-about-oversimplification/" rel="nofollow">my post today</a>: in retrospect,  I don&#8217;t think &#8220;oversimplification is confusing&#8221; was really the problem here. The problem was either (a) not enough simplification, or (b) the <em>wrong</em> simplification.</p>
<p>&#8220;Provide users with enough explanation to make an informed decision&#8221; is a good maxim, but I would add &#8220;or don&#8217;t let them make the decision at all.&#8221;</p>
<p>Another way of describing what happened here is that by leaving information out (which is often done in pursuit of simplification) they actually made things more complicated.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: e</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3468</link>
		<pubDate>Fri, 21 Sep 2007 20:27:47 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3468</guid>
					<description>&lt;blockquote&gt;Keeping your dialogs simple is a good idea, but be careful — sometimes oversimplification can be confusing.&lt;/blockquote&gt;

&lt;p&gt;Isn't there a bigger UI commandment here? Instead of forbidding UI writers from oversimplifying (where simplifying == "hide information from the user"), which isn't very clear, wouldn't it make more sense to command them to "Provide users with enough explanation to make an informed decision"?&lt;/p&gt;

&lt;p&gt;e&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote><p>Keeping your dialogs simple is a good idea, but be careful — sometimes oversimplification can be confusing.</p></blockquote>
<p>Isn&#8217;t there a bigger UI commandment here? Instead of forbidding UI writers from oversimplifying (where simplifying == &#8220;hide information from the user&#8221;), which isn&#8217;t very clear, wouldn&#8217;t it make more sense to command them to &#8220;Provide users with enough explanation to make an informed decision&#8221;?</p>
<p>e</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3465</link>
		<pubDate>Fri, 21 Sep 2007 18:23:09 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3465</guid>
					<description>&lt;p&gt;Chance: Ah yes, the turbo button. Well, of course you should leave it off, and save it for when you really need to get something done fast. ;-)&lt;/p&gt;

&lt;p&gt;I actually remember that when I used to play F-15 Strike Eagle II on my mom's 486DX2, I had to turn the turbo off to make it playable. That's all I ever used it for.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Chance: Ah yes, the turbo button. Well, of course you should leave it off, and save it for when you really need to get something done fast. ;-)</p>
<p>I actually remember that when I used to play F-15 Strike Eagle II on my mom&#8217;s 486DX2, I had to turn the turbo off to make it playable. That&#8217;s all I ever used it for.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Chance</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3464</link>
		<pubDate>Fri, 21 Sep 2007 17:52:52 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3464</guid>
					<description>&lt;p&gt;This reminds of when PCs used to have "Turbo" buttons. Why wouldn't I want my computer to run at the maximum speed? Will more errors or overheating occur if I leave it on Turbo? Should I give my PC a break now and then? What's the alternative scenario?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This reminds of when PCs used to have &#8220;Turbo&#8221; buttons. Why wouldn&#8217;t I want my computer to run at the maximum speed? Will more errors or overheating occur if I leave it on Turbo? Should I give my PC a break now and then? What&#8217;s the alternative scenario?</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dubroy.com/blog &#187; Making up my mind about oversimplification</title>
		<link>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3463</link>
		<pubDate>Fri, 21 Sep 2007 17:47:40 +0000</pubDate>
		<guid>http://dubroy.com/blog/2007/08/30/oversimplification-is-confusing-or-dont-ask-stupid-questions/#comment-3463</guid>
					<description>&lt;p&gt;[...] I just saw that my post Oversimplification is Confusing from a few weeks ago got posted on Signal vs. Noise. Coincidentally, I posted yesterday that things should be as simple as possible, and then some. Well, well, well. Sounds a little contradictory, doesn&#8217;t it? [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[&#8230;] I just saw that my post Oversimplification is Confusing from a few weeks ago got posted on Signal vs. Noise. Coincidentally, I posted yesterday that things should be as simple as possible, and then some. Well, well, well. Sounds a little contradictory, doesn&#8217;t it? [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
