<?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: Photoshop &amp; &#8220;The Paradox of Choice&#8221;</title>
	<atom:link href="http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 19:45:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Louis</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-38483</link>
		<dc:creator>Louis</dc:creator>
		<pubDate>Wed, 09 Nov 2011 11:02:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-38483</guid>
		<description><![CDATA[If you are not happy using the product CS5 PS then there are a stack of others on the market. But it think the main point of it has to be that once you get your head around the complexity or choice photoshop has every tool you could ever need! Not to mention its update-ability!]]></description>
		<content:encoded><![CDATA[<p>If you are not happy using the product CS5 PS then there are a stack of others on the market. But it think the main point of it has to be that once you get your head around the complexity or choice photoshop has every tool you could ever need! Not to mention its update-ability!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dusty from numerica</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-32575</link>
		<dc:creator>dusty from numerica</dc:creator>
		<pubDate>Mon, 07 Feb 2011 17:09:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-32575</guid>
		<description><![CDATA[I hear what you saying and there are personality types that I think fit the situation where your assertions would be a virtual bullseye. Where I think you could expand on your theory/practice so that you are still &quot;hitting the target&quot; at near the same level of accuracy, but for a significantly larger size group, would be to add that knowledge (in the context of being aware) can be viewed as a difference set of knowledge as compared to knowing a more realistic set of what your options for each situation wherein a user takes any amount of time thinking before choosing doing (doing=carrying a task through to completion)

I realize what I am trying to add to this topic is coming out very clear, but basically, I think with whatever set of choices a user is presented with to complete the desired function, IMO it helps to include a &quot;You Are Here&quot; type of pictorial representation as to how many other options may be available to complete similar tasks that result in a different end product that require possibly just as many different &quot;paths&quot; or physical and mental investment from the user to complete the desired task.

As far as the example using image editing software and having a premium program available that may be so user friendly that a first time user of the program (but one who is moderately familiar with computers in general) would rate a companies such as CS as easy to use of PSelements, if it could be pulled off I think you could keep as a company total number of all editing programs/bundles nearly the same BUT have a greater number of those sales as purchases of the significantly higher priced CS if the CS had a simply addition to the custom options tab which corresponded to 3 different defaults 1)1st time user    2) I had last years elements programs but all I did was crop or block out my face and tattoos for risque dating site  3) I had last years elements and used it to put my face on somebody elses body and the images could pass for not manipulated, to put on my risque dating site profile.

If you could market it as totally new CS now more intuitive and 1st time user friendly it is simpler than elements.

Because elements is a very user friendly program and of course the wording that I threw out there is slightly misleading, but I think the PC market would love to have CS with some preset default options that would hide all the more advanced options and essentially run elements for a 1st time user. 

Would it sell any more CS bundles in the same amount of time as just simply offering upgrade from element to same year version CS for the difference in the retail price? 

who knows? but I can say I would buy CS over elements if I had the funds available but instead I bought elements at the advice of someone who is CS savy and the advise was not given based on cost efficiency for what I wanted to do, but rather she thought I would not be happy with CS due to it being more complicated.]]></description>
		<content:encoded><![CDATA[<p>I hear what you saying and there are personality types that I think fit the situation where your assertions would be a virtual bullseye. Where I think you could expand on your theory/practice so that you are still &#8220;hitting the target&#8221; at near the same level of accuracy, but for a significantly larger size group, would be to add that knowledge (in the context of being aware) can be viewed as a difference set of knowledge as compared to knowing a more realistic set of what your options for each situation wherein a user takes any amount of time thinking before choosing doing (doing=carrying a task through to completion)</p>
<p>I realize what I am trying to add to this topic is coming out very clear, but basically, I think with whatever set of choices a user is presented with to complete the desired function, IMO it helps to include a &#8220;You Are Here&#8221; type of pictorial representation as to how many other options may be available to complete similar tasks that result in a different end product that require possibly just as many different &#8220;paths&#8221; or physical and mental investment from the user to complete the desired task.</p>
<p>As far as the example using image editing software and having a premium program available that may be so user friendly that a first time user of the program (but one who is moderately familiar with computers in general) would rate a companies such as CS as easy to use of PSelements, if it could be pulled off I think you could keep as a company total number of all editing programs/bundles nearly the same BUT have a greater number of those sales as purchases of the significantly higher priced CS if the CS had a simply addition to the custom options tab which corresponded to 3 different defaults 1)1st time user    2) I had last years elements programs but all I did was crop or block out my face and tattoos for risque dating site  3) I had last years elements and used it to put my face on somebody elses body and the images could pass for not manipulated, to put on my risque dating site profile.</p>
<p>If you could market it as totally new CS now more intuitive and 1st time user friendly it is simpler than elements.</p>
<p>Because elements is a very user friendly program and of course the wording that I threw out there is slightly misleading, but I think the PC market would love to have CS with some preset default options that would hide all the more advanced options and essentially run elements for a 1st time user. </p>
<p>Would it sell any more CS bundles in the same amount of time as just simply offering upgrade from element to same year version CS for the difference in the retail price? </p>
<p>who knows? but I can say I would buy CS over elements if I had the funds available but instead I bought elements at the advice of someone who is CS savy and the advise was not given based on cost efficiency for what I wanted to do, but rather she thought I would not be happy with CS due to it being more complicated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6476</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Thu, 26 Jun 2008 02:39:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6476</guid>
		<description><![CDATA[I know I&#039;m late to this particular party, but let me just say:
1) I *like* choices, and in fact the greater number of choices in customizability is, so far, the major improvement I notice in CS3 (for instance, I&#039;ve never understood why Adobe doesn&#039;t think &quot;crop&quot; deserves a shortcut; but now Adobe&#039;s choice on that doesn&#039;t matter to me since I can just give it one!).  Having too many choices is bad when the choices aren&#039;t significantly different (50 kinds of jeans, when, really, they&#039;re all just jeans), but when the choices significantly affect how you use the program, I&#039;m all for them; and I have enough self-control to simply ignore all the ones that *don&#039;t* affect my work (hell, now I can just remove them from the menus!).
2) The &quot;old&quot; brightness/contrast was not useless (I use it on every image I take, probably), you just have to know what they do.  Fortunately, what they do is extremely simple. On a histogram, increasing brightness moves values to the right, decreasing brightness moves them to the left; increasing contrast spreads values out, decreasing contrast moves them together.  OTOH, I can&#039;t figure out what the &quot;new&quot; brightness and contrast do.  I&#039;ve already found, for instance, that under some situations large increases in contrast actually move values closer together--precisely the opposite of my intended effect  and clearly *not* an increase in contrast!  The &quot;new&quot; controls are of no use to me since I don&#039;t know what they do and thus can&#039;t use them to achieve any particular goal.  Now, new users often have difficulty figuring out how to use the &quot;old&quot; brightness/contrast effectively, and apparently these new users like the &quot;new&quot; one.  Anyways... the solution to all this?  Well, Adobe got partway there by adding the &quot;use legacy&quot; button, but they didn&#039;t get all the way there, since anyone who wants to use the &quot;old&quot; brightness/contrast has to check that button every single time.  The full solution would, of course, be to offer more choices.  Let me choose to just have &quot;use legacy&quot; be the default under all situations and I&#039;ll be happy.  Similarly, let those who love the &quot;new&quot; one just have that be their default in all cases and get rid of the &quot;use legacy&quot; button which, by being right next to &quot;preview&quot;, is apt to be pressed accidentally.
Give me more choices, I say.  And don&#039;t force an organization by task on me, since I&#039;m sure Adobe and I will disagree with what&#039;s relevant to the tasks I want to do.  If I can customize the interface, Adobe&#039;s choices don&#039;t need to be right since I can make my own.
]]></description>
		<content:encoded><![CDATA[<p>I know I&#8217;m late to this particular party, but let me just say:<br />
1) I *like* choices, and in fact the greater number of choices in customizability is, so far, the major improvement I notice in CS3 (for instance, I&#8217;ve never understood why Adobe doesn&#8217;t think &#8220;crop&#8221; deserves a shortcut; but now Adobe&#8217;s choice on that doesn&#8217;t matter to me since I can just give it one!).  Having too many choices is bad when the choices aren&#8217;t significantly different (50 kinds of jeans, when, really, they&#8217;re all just jeans), but when the choices significantly affect how you use the program, I&#8217;m all for them; and I have enough self-control to simply ignore all the ones that *don&#8217;t* affect my work (hell, now I can just remove them from the menus!).<br />
2) The &#8220;old&#8221; brightness/contrast was not useless (I use it on every image I take, probably), you just have to know what they do.  Fortunately, what they do is extremely simple. On a histogram, increasing brightness moves values to the right, decreasing brightness moves them to the left; increasing contrast spreads values out, decreasing contrast moves them together.  OTOH, I can&#8217;t figure out what the &#8220;new&#8221; brightness and contrast do.  I&#8217;ve already found, for instance, that under some situations large increases in contrast actually move values closer together&#8211;precisely the opposite of my intended effect  and clearly *not* an increase in contrast!  The &#8220;new&#8221; controls are of no use to me since I don&#8217;t know what they do and thus can&#8217;t use them to achieve any particular goal.  Now, new users often have difficulty figuring out how to use the &#8220;old&#8221; brightness/contrast effectively, and apparently these new users like the &#8220;new&#8221; one.  Anyways&#8230; the solution to all this?  Well, Adobe got partway there by adding the &#8220;use legacy&#8221; button, but they didn&#8217;t get all the way there, since anyone who wants to use the &#8220;old&#8221; brightness/contrast has to check that button every single time.  The full solution would, of course, be to offer more choices.  Let me choose to just have &#8220;use legacy&#8221; be the default under all situations and I&#8217;ll be happy.  Similarly, let those who love the &#8220;new&#8221; one just have that be their default in all cases and get rid of the &#8220;use legacy&#8221; button which, by being right next to &#8220;preview&#8221;, is apt to be pressed accidentally.<br />
Give me more choices, I say.  And don&#8217;t force an organization by task on me, since I&#8217;m sure Adobe and I will disagree with what&#8217;s relevant to the tasks I want to do.  If I can customize the interface, Adobe&#8217;s choices don&#8217;t need to be right since I can make my own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: imajes</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6475</link>
		<dc:creator>imajes</dc:creator>
		<pubDate>Thu, 03 Jan 2008 17:46:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6475</guid>
		<description><![CDATA[As for the tyranny of choice, Apple go way too far the other way and you have the Tyranny of Jobs instead. &#039;Think Different&#039; was Apple&#039;s slogan ,but it should have been subtitled as long as it&#039;s exactly the same way we think.
Time Machine - brilliant idea, but how simplistic is it? I use Windows Home Server [unlike Vista this is really good and works with Macs too]to back up and it&#039;s also very easy to back up, but I can easily elect to back up only what I want and not what Apple think I want backing up.
]]></description>
		<content:encoded><![CDATA[<p>As for the tyranny of choice, Apple go way too far the other way and you have the Tyranny of Jobs instead. &#8216;Think Different&#8217; was Apple&#8217;s slogan ,but it should have been subtitled as long as it&#8217;s exactly the same way we think.<br />
Time Machine &#8211; brilliant idea, but how simplistic is it? I use Windows Home Server [unlike Vista this is really good and works with Macs too]to back up and it&#8217;s also very easy to back up, but I can easily elect to back up only what I want and not what Apple think I want backing up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: imajes</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6474</link>
		<dc:creator>imajes</dc:creator>
		<pubDate>Thu, 03 Jan 2008 16:54:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6474</guid>
		<description><![CDATA[&quot;A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away&quot;
Replace designer with sculptor or photographer. Both also reduce to perfection [a photographer when capturing image that is].
As for the Creative Suites selling well, well duh, it&#039;s cheaper than buying individual Apps, but I certainly don&#039;t want to buy the Master Suite to get a load of apps I don&#039;t need to get the ones I do want.
There needs to be a Master Design, where you get everything but video/sound stuff. BTW I recently went to an Adobe promo event extolling the virtues of the CS3 suite and its integration. Thought I&#039;d look into this very important aspect and opened a PS file in Fireworks and no PS produced slices to be seen!?
Glad to see I&#039;m not the only one who thinks LR&#039;s interface is a bit messed up. Yeah, what&#039;s with having Scroll bars on the left on some panels, whereas every other app [including Bridge] has them on the right even for scrolling things in the panels left of screen. And why does this app use [in Windows] Cnrl+, instead of Cnrtl+k like other PS family members. Imagine how confusing it is trying to remember if your programme does things the Mac way or the PC way when using a PC. If I&#039;m using a Mac I want the progerammes to obey Mac conventions and the same when using a PC. Is it my imagination or do the Windows versions of recent Adobe apps seem rougher round the edges than the Mac versions. Anyone would think they were designed for the Mac and hurriedly finished off for the PC.
And having to go back to Library to get a grid view of images is a complete PITA. Esp in Develop Module. Film strip is a weedy and clunky replacement.
And I have still have to figure out why user order works only some of the time in Grid or Filmstrip. And it not working at all when including photos from subfolders, duh-uh! Smack head on desk. Speaking of sort order, why isn&#039;t the menu offset when you click on the button, like normal options. As you all too often click on the option that appears over the button you&#039;ve just clicked. Again an untypical behaviour. Select toolbar content does the same thing too, but if you click on the filmstrip folder line it&#039;s correctly offset.
A bit off the tyranny of choice but a comment above reminded me of LR&#039;s oddities/inconsistencies and wilful differences from the programmes you&#039;d use with it.
]]></description>
		<content:encoded><![CDATA[<p>&#8220;A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away&#8221;<br />
Replace designer with sculptor or photographer. Both also reduce to perfection [a photographer when capturing image that is].<br />
As for the Creative Suites selling well, well duh, it&#8217;s cheaper than buying individual Apps, but I certainly don&#8217;t want to buy the Master Suite to get a load of apps I don&#8217;t need to get the ones I do want.<br />
There needs to be a Master Design, where you get everything but video/sound stuff. BTW I recently went to an Adobe promo event extolling the virtues of the CS3 suite and its integration. Thought I&#8217;d look into this very important aspect and opened a PS file in Fireworks and no PS produced slices to be seen!?<br />
Glad to see I&#8217;m not the only one who thinks LR&#8217;s interface is a bit messed up. Yeah, what&#8217;s with having Scroll bars on the left on some panels, whereas every other app [including Bridge] has them on the right even for scrolling things in the panels left of screen. And why does this app use [in Windows] Cnrl+, instead of Cnrtl+k like other PS family members. Imagine how confusing it is trying to remember if your programme does things the Mac way or the PC way when using a PC. If I&#8217;m using a Mac I want the progerammes to obey Mac conventions and the same when using a PC. Is it my imagination or do the Windows versions of recent Adobe apps seem rougher round the edges than the Mac versions. Anyone would think they were designed for the Mac and hurriedly finished off for the PC.<br />
And having to go back to Library to get a grid view of images is a complete PITA. Esp in Develop Module. Film strip is a weedy and clunky replacement.<br />
And I have still have to figure out why user order works only some of the time in Grid or Filmstrip. And it not working at all when including photos from subfolders, duh-uh! Smack head on desk. Speaking of sort order, why isn&#8217;t the menu offset when you click on the button, like normal options. As you all too often click on the option that appears over the button you&#8217;ve just clicked. Again an untypical behaviour. Select toolbar content does the same thing too, but if you click on the filmstrip folder line it&#8217;s correctly offset.<br />
A bit off the tyranny of choice but a comment above reminded me of LR&#8217;s oddities/inconsistencies and wilful differences from the programmes you&#8217;d use with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor Morris</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6473</link>
		<dc:creator>Trevor Morris</dc:creator>
		<pubDate>Wed, 02 Jan 2008 16:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6473</guid>
		<description><![CDATA[Happy New Year!
Conrgats to Mom &amp; Dad (to be)!
Great read as always, John.
&lt;i&gt;[Thanks on all counts, Trevor.  Happy New Year to you as well.  (Let&#039;s hear it for non-denominational, unambiguously wishable holidays! :-))  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>Happy New Year!<br />
Conrgats to Mom &amp; Dad (to be)!<br />
Great read as always, John.<br />
<i>[Thanks on all counts, Trevor.  Happy New Year to you as well.  (Let's hear it for non-denominational, unambiguously wishable holidays! :-))  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6472</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 02 Jan 2008 11:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6472</guid>
		<description><![CDATA[Lynn re Ribbon Presuming that you use Word on a regular basis than changing the arrangement of the tools might be a negative.  I don&#039;t use Word regularly beyond the basic word processing features.  Having a more task oriented arrangement helps me to know what tools apply to the work I&#039;m doing and the result I&#039;m looking for.
Which brings me back to LR.  It is task oriented to just Photography.  If I don&#039;t use it daily reacquainting myself with its controls isn&#039;t time consuming.  The same can&#039;t be said of PS.  That leads me to Scott Kelby&#039;s latest book &quot;The 7 point system&quot;. Scott found there were seven steps he did in PS to correct a photo. Rearranging the GUI to show just those tools would be similar to the Ribbon in Word.
]]></description>
		<content:encoded><![CDATA[<p>Lynn re Ribbon Presuming that you use Word on a regular basis than changing the arrangement of the tools might be a negative.  I don&#8217;t use Word regularly beyond the basic word processing features.  Having a more task oriented arrangement helps me to know what tools apply to the work I&#8217;m doing and the result I&#8217;m looking for.<br />
Which brings me back to LR.  It is task oriented to just Photography.  If I don&#8217;t use it daily reacquainting myself with its controls isn&#8217;t time consuming.  The same can&#8217;t be said of PS.  That leads me to Scott Kelby&#8217;s latest book &#8220;The 7 point system&#8221;. Scott found there were seven steps he did in PS to correct a photo. Rearranging the GUI to show just those tools would be similar to the Ribbon in Word.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art Swalwell</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6471</link>
		<dc:creator>Art Swalwell</dc:creator>
		<pubDate>Wed, 02 Jan 2008 07:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6471</guid>
		<description><![CDATA[The problem isn&#039;t the complexity, it&#039;s figuring out what all the new stuff does and how it works. Thank God for Russell Brown, I hope we can find someone, or several someones, to fill Bruce Fraser&#039;s shoes. (Sorry Mr. Kelby, I like a little substance with my sophomoric jokes.)
Art Swalwell
]]></description>
		<content:encoded><![CDATA[<p>The problem isn&#8217;t the complexity, it&#8217;s figuring out what all the new stuff does and how it works. Thank God for Russell Brown, I hope we can find someone, or several someones, to fill Bruce Fraser&#8217;s shoes. (Sorry Mr. Kelby, I like a little substance with my sophomoric jokes.)<br />
Art Swalwell</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Nelson</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6470</link>
		<dc:creator>Doug Nelson</dc:creator>
		<pubDate>Wed, 02 Jan 2008 02:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6470</guid>
		<description><![CDATA[There&#039;s only a seeming paradox of choice when the choices lack delineation. It&#039;s the cliche of trying to be too many things for too many people.
IMO, PS should embrace the &quot;pro&quot; and be infinitely extensible and powerful. Don&#039;t conflate &quot;accessible&quot; with &quot;intuitive&quot;. PS should work intuitively for those that know how imaging works. Let Elements be accessible for those who don&#039;t.
Don&#039;t worry about helping users understand the difference between clone and heal, they should be the same tool (along with all the other brushed tools). And if it&#039;s not the exact right tool, it should be straightforward for a 3rd-party to develop the exact right tool.
PS is going schizoid, trying to be both floor wax and dessert topping, lamborghini and big wheel, Leica and Polaroid.
The only criterion for future PS development should be providing the optimum workspace and framework for knowledgeable users to do their best possible imaging work. Let Elements, Fireworks, and Lightroom be there for the LOLcatters, giffers, and production photographers.
]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s only a seeming paradox of choice when the choices lack delineation. It&#8217;s the cliche of trying to be too many things for too many people.<br />
IMO, PS should embrace the &#8220;pro&#8221; and be infinitely extensible and powerful. Don&#8217;t conflate &#8220;accessible&#8221; with &#8220;intuitive&#8221;. PS should work intuitively for those that know how imaging works. Let Elements be accessible for those who don&#8217;t.<br />
Don&#8217;t worry about helping users understand the difference between clone and heal, they should be the same tool (along with all the other brushed tools). And if it&#8217;s not the exact right tool, it should be straightforward for a 3rd-party to develop the exact right tool.<br />
PS is going schizoid, trying to be both floor wax and dessert topping, lamborghini and big wheel, Leica and Polaroid.<br />
The only criterion for future PS development should be providing the optimum workspace and framework for knowledgeable users to do their best possible imaging work. Let Elements, Fireworks, and Lightroom be there for the LOLcatters, giffers, and production photographers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Valentine</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6469</link>
		<dc:creator>Scott Valentine</dc:creator>
		<pubDate>Tue, 01 Jan 2008 20:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6469</guid>
		<description><![CDATA[For a while now, I&#039;ve fantasized about PS reducing the number of built-in filters in favor of a few core kernel operation UIs. I&#039;d love to slap on a stripped-down GUI that lets me choose a matrix filter rather than distributing sharpening, blurring and edge finding into a dozen or more specialized dialogs.
But I realize this is not for everyone, nor even a modest percentage of users. Still, it would be nice to have an option to let me get at the kernels without having to write custom filters in a compiled language.
Talk about reducing the number of choices ;)
]]></description>
		<content:encoded><![CDATA[<p>For a while now, I&#8217;ve fantasized about PS reducing the number of built-in filters in favor of a few core kernel operation UIs. I&#8217;d love to slap on a stripped-down GUI that lets me choose a matrix filter rather than distributing sharpening, blurring and edge finding into a dozen or more specialized dialogs.<br />
But I realize this is not for everyone, nor even a modest percentage of users. Still, it would be nice to have an option to let me get at the kernels without having to write custom filters in a compiled language.<br />
Talk about reducing the number of choices ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vanderhellen</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6468</link>
		<dc:creator>Vanderhellen</dc:creator>
		<pubDate>Tue, 01 Jan 2008 17:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6468</guid>
		<description><![CDATA[The trick is to make things &quot;as simple as possible, but no simpler.&quot;
If so, please unify the &quot;alignment&quot; (for instance) in Adobes CS applications. Why are the results in ID and AI different? There is a different strategy to align 2 items if I don&#039;t want tp move both. Try!
And this is only ONE example for the need to streamline the usability of Adobes applications. They should do their homeworks first. :-)
]]></description>
		<content:encoded><![CDATA[<p>The trick is to make things &#8220;as simple as possible, but no simpler.&#8221;<br />
If so, please unify the &#8220;alignment&#8221; (for instance) in Adobes CS applications. Why are the results in ID and AI different? There is a different strategy to align 2 items if I don&#8217;t want tp move both. Try!<br />
And this is only ONE example for the need to streamline the usability of Adobes applications. They should do their homeworks first. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6467</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Tue, 01 Jan 2008 14:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6467</guid>
		<description><![CDATA[I started writing this before Mordy&#039;s post and I don&#039;t have time right now to go over it again, so sorry if I&#039;m repeating some of the things he mentioned in his post.
However, I don&#039;t agree with the Brightness/Contrast thing. I only use it for situations when i really &lt;i&gt;want&lt;/i&gt; to blow out stuff, for example when dealing with masks and channels or smoothing upsampled low-res b/w logos by blurring them and then increasing the contrast. Now I have to tick the &quot;Use Legacy&quot; check box every single time, which is quite annoying. The change is just preventing beginners from getting fooled by the name and doing something stupid, it&#039;s not very valuable for a pro since it does not offer enough control for most cases, so pros will continue to use curves.
But to the point: I prefer to really learn a complex feature or how to use multiple features together to achieve a certain result and thus have all the power I need. I&#039;m not really a fan of &quot;Instant Results&quot; sliders and magic buttons. For example, whenever I have to use Microsoft products, I always feel like the software is somehow imposing its idea of what I &lt;em&gt;should&lt;/em&gt; want to do on me and treats me, well, like an idiot (Visual Studio is a very nice exception though).
In contrast, Photoshop does not perform &lt;em&gt;Tasks&lt;/em&gt; for me, it offers the &lt;em&gt;Tools&lt;/em&gt; to complete them myself, making it extremely versatile and infinitely more powerful.
It&#039;s one of the things I love most about Photoshop that it lets me do things in lots of different ways by offering the building blocks. If I want to remove a color cast, I don&#039;t use an option that says &quot;Remove Color Cast&quot;, but I can use Color Balance, Curves, Levels, Solid color layers with blend modes, Apply Image, Hue/Saturation and so on. I have all these &quot;lego bricks&quot; that I can use to build my own version of &quot;Remove Color Cast&quot; that better suits my image than any pre-built tool would, or I can use them for something entirely different.
Just as an example for the opposite: Refine Edge is nice, but it&#039;s something I did not really need since I could build it more or less myself by using filters such as Gaussian Blur or Minimum in Quick Mask Mode or on a Channel/Layer Mask. That even gives me a live preview. The same goes for Shadow/Highlight, it can be easily replicated (at least to some degree) using existing tools.
Such things make certain operations quicker, but they have very limited use in other contexts, and for me, it&#039;s those things that ultimately &quot;bloat&quot; the application on the long term, rather than improving user experience sice the don&#039;t really add much valuable additional functionality.
Let&#039;s take a real-world example: Imagine you couldn&#039;t wash the color out of a paintbrush. You&#039;d have to buy one brush for each color you intend to paint with. For the beginner, that&#039;s good, since he/she does not have to know how to properly clean the brush, nor would he/she have to be concerned with color harmonies. But the advanced painter would prefer one brush that can be used for all colors since it takes up less space on the desk while providing more flexibility. Plus he/she can now mix colors to achieve results that would be impossible otherwise.
By the way, I think your strollers example is somewhat inaccurate. Photoshop is a professional product aimed at professional users. You&#039;d have to be a professional stroller buyer (I know that sounds stupid) if you wanted the comparison to be accurate, and I think if you actually were a professional stroller buyer, you would &lt;em&gt;want&lt;/em&gt; to have so many choices with different strengths.
By the way, there is quite a big problem with &quot;Show more Options&quot; or &quot;Advanced&quot; buttons that don&#039;t remember their state and are always collapsed when the dialog opens: If the inputs it hides value fields that automatically use the last settings used, they hide non-default values, giving the user undesirable results. The &quot;New Document&quot; dialog box in InDesign is such a case that really bugs me. The bleed setting always defaults to my last choice. But I don&#039;t see which values are in there if the options are hidden. If I had some unusual value in there and I forgot to click the &quot;More Options&quot; button, that can be simply annoying or even a big problem when outputting for professional print.
I think you should make Photoshop Elements task-based and the full Photoshop primarily tool-based and add only those task-based operations that take very long to do manually, or are used extremely often, or are hard to do by hand. The Red Eye tool and Auto-Align/Blend Layers are examples of such task-based features that are very valuable additions to the application.
If you want to make the UI more usable/less complex, you should take a look at making the UI even more context sensitive if you ask me. It already works great for the tool options bar, which only shows the options for the current tool instead of having a separate settings panel for ever single tool. But you don&#039;t really need the swatches when you are working on a layer mask for instance.
Even though it hides features you don&#039;t need, a context-sensitive UI is very different from a task-based UI in that it shows you only the options that make sense in the current &lt;i&gt;context&lt;/i&gt; as opposed to showing the options the application things I need for the current &lt;i&gt;task&lt;/i&gt;. It may be the current selection that determines the current context, or a user action (such as opening the Preferences, or selecting a tool from the toolbar).
A really nice example of such a context-sensitive UI is Autodesk Toxik -- they only show you the options for things you are currently working (you can see their UI in action here: &lt;a href=&quot;http://download.autodesk.com/us/toxik/tutorial2007/),&quot; rel=&quot;nofollow&quot;&gt;http://download.autodesk.com/us/toxik/tutorial2007/),&lt;/a&gt; and it looks rather intuitive to me once you know the basics. Don&#039;t get me wrong, I&#039;m not suggesting you copy that paradigm for Photoshop, I just think they did a great job at keeping the non-relevant stuff out of the way without dumbing-down the software. Their Gate-UI thing looks pretty cool as well by the way.
Lightroom on the other hand is strictly task-oriented. It&#039;s a great software and it&#039;s extremely intuitive, but the price you pay is that it&#039;s use is pretty much limited to digital photography, whereas Photoshop for example is useful for a wide variety of target audiences.
]]></description>
		<content:encoded><![CDATA[<p>I started writing this before Mordy&#8217;s post and I don&#8217;t have time right now to go over it again, so sorry if I&#8217;m repeating some of the things he mentioned in his post.<br />
However, I don&#8217;t agree with the Brightness/Contrast thing. I only use it for situations when i really <i>want</i> to blow out stuff, for example when dealing with masks and channels or smoothing upsampled low-res b/w logos by blurring them and then increasing the contrast. Now I have to tick the &#8220;Use Legacy&#8221; check box every single time, which is quite annoying. The change is just preventing beginners from getting fooled by the name and doing something stupid, it&#8217;s not very valuable for a pro since it does not offer enough control for most cases, so pros will continue to use curves.<br />
But to the point: I prefer to really learn a complex feature or how to use multiple features together to achieve a certain result and thus have all the power I need. I&#8217;m not really a fan of &#8220;Instant Results&#8221; sliders and magic buttons. For example, whenever I have to use Microsoft products, I always feel like the software is somehow imposing its idea of what I <em>should</em> want to do on me and treats me, well, like an idiot (Visual Studio is a very nice exception though).<br />
In contrast, Photoshop does not perform <em>Tasks</em> for me, it offers the <em>Tools</em> to complete them myself, making it extremely versatile and infinitely more powerful.<br />
It&#8217;s one of the things I love most about Photoshop that it lets me do things in lots of different ways by offering the building blocks. If I want to remove a color cast, I don&#8217;t use an option that says &#8220;Remove Color Cast&#8221;, but I can use Color Balance, Curves, Levels, Solid color layers with blend modes, Apply Image, Hue/Saturation and so on. I have all these &#8220;lego bricks&#8221; that I can use to build my own version of &#8220;Remove Color Cast&#8221; that better suits my image than any pre-built tool would, or I can use them for something entirely different.<br />
Just as an example for the opposite: Refine Edge is nice, but it&#8217;s something I did not really need since I could build it more or less myself by using filters such as Gaussian Blur or Minimum in Quick Mask Mode or on a Channel/Layer Mask. That even gives me a live preview. The same goes for Shadow/Highlight, it can be easily replicated (at least to some degree) using existing tools.<br />
Such things make certain operations quicker, but they have very limited use in other contexts, and for me, it&#8217;s those things that ultimately &#8220;bloat&#8221; the application on the long term, rather than improving user experience sice the don&#8217;t really add much valuable additional functionality.<br />
Let&#8217;s take a real-world example: Imagine you couldn&#8217;t wash the color out of a paintbrush. You&#8217;d have to buy one brush for each color you intend to paint with. For the beginner, that&#8217;s good, since he/she does not have to know how to properly clean the brush, nor would he/she have to be concerned with color harmonies. But the advanced painter would prefer one brush that can be used for all colors since it takes up less space on the desk while providing more flexibility. Plus he/she can now mix colors to achieve results that would be impossible otherwise.<br />
By the way, I think your strollers example is somewhat inaccurate. Photoshop is a professional product aimed at professional users. You&#8217;d have to be a professional stroller buyer (I know that sounds stupid) if you wanted the comparison to be accurate, and I think if you actually were a professional stroller buyer, you would <em>want</em> to have so many choices with different strengths.<br />
By the way, there is quite a big problem with &#8220;Show more Options&#8221; or &#8220;Advanced&#8221; buttons that don&#8217;t remember their state and are always collapsed when the dialog opens: If the inputs it hides value fields that automatically use the last settings used, they hide non-default values, giving the user undesirable results. The &#8220;New Document&#8221; dialog box in InDesign is such a case that really bugs me. The bleed setting always defaults to my last choice. But I don&#8217;t see which values are in there if the options are hidden. If I had some unusual value in there and I forgot to click the &#8220;More Options&#8221; button, that can be simply annoying or even a big problem when outputting for professional print.<br />
I think you should make Photoshop Elements task-based and the full Photoshop primarily tool-based and add only those task-based operations that take very long to do manually, or are used extremely often, or are hard to do by hand. The Red Eye tool and Auto-Align/Blend Layers are examples of such task-based features that are very valuable additions to the application.<br />
If you want to make the UI more usable/less complex, you should take a look at making the UI even more context sensitive if you ask me. It already works great for the tool options bar, which only shows the options for the current tool instead of having a separate settings panel for ever single tool. But you don&#8217;t really need the swatches when you are working on a layer mask for instance.<br />
Even though it hides features you don&#8217;t need, a context-sensitive UI is very different from a task-based UI in that it shows you only the options that make sense in the current <i>context</i> as opposed to showing the options the application things I need for the current <i>task</i>. It may be the current selection that determines the current context, or a user action (such as opening the Preferences, or selecting a tool from the toolbar).<br />
A really nice example of such a context-sensitive UI is Autodesk Toxik &#8212; they only show you the options for things you are currently working (you can see their UI in action here: <a href="http://download.autodesk.com/us/toxik/tutorial2007/)," rel="nofollow"></a><a href="http://download.autodesk.com/us/toxik/tutorial2007/" rel="nofollow">http://download.autodesk.com/us/toxik/tutorial2007/</a>), and it looks rather intuitive to me once you know the basics. Don&#8217;t get me wrong, I&#8217;m not suggesting you copy that paradigm for Photoshop, I just think they did a great job at keeping the non-relevant stuff out of the way without dumbing-down the software. Their Gate-UI thing looks pretty cool as well by the way.<br />
Lightroom on the other hand is strictly task-oriented. It&#8217;s a great software and it&#8217;s extremely intuitive, but the price you pay is that it&#8217;s use is pretty much limited to digital photography, whereas Photoshop for example is useful for a wide variety of target audiences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimhere</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6466</link>
		<dc:creator>jimhere</dc:creator>
		<pubDate>Tue, 01 Jan 2008 11:56:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6466</guid>
		<description><![CDATA[&lt;i&gt;Mordy: ...&quot;The problem in my mind is marketing, not engineering. Adobe is stuck in a mode of thinking that they have to add new tools in order to excite people to upgrade each version. We don&#039;t need new tools. We need the current toolset made better&quot;...&lt;/i&gt;
Correct. I think as of PS5 or 6, absolutely &lt;i&gt;anything&lt;/i&gt; could be visualized in Photoshop. The healing brush is amazing, but please don&#039;t feel like you have to try for the Nobel prize in Task Bars with each version. Mordy&#039;s hero, Illustrator, proves this with its new color machines, something that makes aiCS3 so much more, er, &lt;i&gt;exciting&lt;/i&gt; than psCS3 (even though I&#039;ll always pay you for both).
&lt;i&gt;JN: ...&quot;It *does* sell. Each release needs to contain both sizzle and steak. It&#039;s not an either/or thing&quot;...&lt;/i&gt;
Or could it be &quot;it&#039;s the latest version&quot;, and &quot;this is what&#039;s currently available&quot;? I buy every 18 months. Didn&#039;t you?
&lt;i&gt;JN: &quot;So, should Adobe offer fewer Suite configurations? We already get dinged for not offering even more flexibility (e.g. a way to get InDesign and Fireworks in a suite without going all the way to the Master Collection). There&#039;s no way to please everyone.&quot;&lt;/i&gt;
That&#039;s exactly what I did, You should be thankful for my Master Collection money instead of worrying about the &quot;people&quot;. Pro apps should be pro apps. I&#039;ve never seen this &quot;Elements&quot; you speak of and I&#039;m sure the kids love it, but PS is a pro app.
]]></description>
		<content:encoded><![CDATA[<p><i>Mordy: &#8230;&#8221;The problem in my mind is marketing, not engineering. Adobe is stuck in a mode of thinking that they have to add new tools in order to excite people to upgrade each version. We don&#8217;t need new tools. We need the current toolset made better&#8221;&#8230;</i><br />
Correct. I think as of PS5 or 6, absolutely <i>anything</i> could be visualized in Photoshop. The healing brush is amazing, but please don&#8217;t feel like you have to try for the Nobel prize in Task Bars with each version. Mordy&#8217;s hero, Illustrator, proves this with its new color machines, something that makes aiCS3 so much more, er, <i>exciting</i> than psCS3 (even though I&#8217;ll always pay you for both).<br />
<i>JN: &#8230;&#8221;It *does* sell. Each release needs to contain both sizzle and steak. It&#8217;s not an either/or thing&#8221;&#8230;</i><br />
Or could it be &#8220;it&#8217;s the latest version&#8221;, and &#8220;this is what&#8217;s currently available&#8221;? I buy every 18 months. Didn&#8217;t you?<br />
<i>JN: &#8220;So, should Adobe offer fewer Suite configurations? We already get dinged for not offering even more flexibility (e.g. a way to get InDesign and Fireworks in a suite without going all the way to the Master Collection). There&#8217;s no way to please everyone.&#8221;</i><br />
That&#8217;s exactly what I did, You should be thankful for my Master Collection money instead of worrying about the &#8220;people&#8221;. Pro apps should be pro apps. I&#8217;ve never seen this &#8220;Elements&#8221; you speak of and I&#8217;m sure the kids love it, but PS is a pro app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lynn Grillo</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6465</link>
		<dc:creator>Lynn Grillo</dc:creator>
		<pubDate>Tue, 01 Jan 2008 10:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6465</guid>
		<description><![CDATA[@Tim and Boris re: the Office 2007 Ribbon. I immensely dislike that bad boy. Stuff that used to be one easy click away is buried one or two levels down now. For me it&#039;s the perfect example of what NOT to do. On the other hand, I think Acrobat 8&#039;s task based approach works well.
As for Photoshop, Mordy gets closest to how I feel. I&#039;d like to use the tools I&#039;m already familiar with to get more done more easily.
]]></description>
		<content:encoded><![CDATA[<p>@Tim and Boris re: the Office 2007 Ribbon. I immensely dislike that bad boy. Stuff that used to be one easy click away is buried one or two levels down now. For me it&#8217;s the perfect example of what NOT to do. On the other hand, I think Acrobat 8&#8242;s task based approach works well.<br />
As for Photoshop, Mordy gets closest to how I feel. I&#8217;d like to use the tools I&#8217;m already familiar with to get more done more easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Watson</title>
		<link>http://blogs.adobe.com/jnack/2007/12/photoshop_the_paradox_of_choice.html#comment-6464</link>
		<dc:creator>Bruce Watson</dc:creator>
		<pubDate>Tue, 01 Jan 2008 08:42:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2007/12/photoshop-the-paradox-of-choice.html#comment-6464</guid>
		<description><![CDATA[&quot;A better solution, I think, is to make Photoshop more task-oriented.  We need to help people bring forward what&#039;s needed, when it&#039;s needed, and put it away when it isn&#039;t.  We need to emphasize best practices--showing the constellations among the stars.&quot;
I think you hit the nail squarely on the head.
&lt;i&gt;[Cool--thanks for saying so.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>&#8220;A better solution, I think, is to make Photoshop more task-oriented.  We need to help people bring forward what&#8217;s needed, when it&#8217;s needed, and put it away when it isn&#8217;t.  We need to emphasize best practices&#8211;showing the constellations among the stars.&#8221;<br />
I think you hit the nail squarely on the head.<br />
<i>[Cool--thanks for saying so.  --J.]</i></p>
]]></content:encoded>
	</item>
</channel>
</rss>
