<?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: Why you (and I) are not designers</title>
	<atom:link href="http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/feed/" rel="self" type="application/rss+xml" />
	<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/</link>
	<description>photographer, entrepreneur, software engineer, musician, skier</description>
	<lastBuildDate>Mon, 14 May 2012 16:09:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nathan</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-21292</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Fri, 13 Feb 2009 10:06:48 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-21292</guid>
		<description>I think part of the problem is that when we discuss design, we usually don&#039;t spend enough time emphasizing the difference between good and bad design.

IMO, everyone designs.  In other words, your app will be designed by someone -- no doubt about it.  But there are those who are more educated, more practiced, more gifted, and sometimes more intelligent, and therefor more apt to hit upon the right combination of things that make a product successful.

It would be nice if people with &quot;designer&quot; in their title were more likely to fall into the above category, but unfortunately two issues tend to muddle up this reality:

1. Some &quot;non-designers&quot; are also able to arrive at good design; either by accident (as you point out) or by advanced skill/intuition.

2. MANY &quot;designers&quot; are not good designers.  In fact, many are extremely BAD designers.

These issues have a way of skewing our general understanding of the designer and their market.  As a designer myself, I can tell you it&#039;s both pleasant (when I find a non-designer with a good knack for it) and frustrating (when I come across people who claim to be designers but have no business saying so).</description>
		<content:encoded><![CDATA[<p>I think part of the problem is that when we discuss design, we usually don&#8217;t spend enough time emphasizing the difference between good and bad design.</p>
<p>IMO, everyone designs.  In other words, your app will be designed by someone &#8212; no doubt about it.  But there are those who are more educated, more practiced, more gifted, and sometimes more intelligent, and therefor more apt to hit upon the right combination of things that make a product successful.</p>
<p>It would be nice if people with &#8220;designer&#8221; in their title were more likely to fall into the above category, but unfortunately two issues tend to muddle up this reality:</p>
<p>1. Some &#8220;non-designers&#8221; are also able to arrive at good design; either by accident (as you point out) or by advanced skill/intuition.</p>
<p>2. MANY &#8220;designers&#8221; are not good designers.  In fact, many are extremely BAD designers.</p>
<p>These issues have a way of skewing our general understanding of the designer and their market.  As a designer myself, I can tell you it&#8217;s both pleasant (when I find a non-designer with a good knack for it) and frustrating (when I come across people who claim to be designers but have no business saying so).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yan</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-18279</link>
		<dc:creator>yan</dc:creator>
		<pubDate>Thu, 18 Dec 2008 17:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-18279</guid>
		<description>Neil, you&#039;ve hit the nail on the head with your last sentence. It&#039;s the designer&#039;s job to understand the psyche of the end user. Design is not about making things pretty. It&#039;s about communication, usability, etc. 

Google is an example of great design. One textbox, one button, easy to use and deliver&#039;s google&#039;s brand message: &#039;we are search&#039;. It doesn&#039;t have to have rounded corners to be well designed. Same thing with facebook (well up until fb 2.0 I would say), an app designed to deliver information to users and stimulate communication. It succeeds at both. Of course there is room for improvement, but they&#039;ve done a pretty good job.

I could have written a post that said &#039;well in some cases it&#039;s ok not to use a designer&#039; but it wouldn&#039;t have had the power of &#039;you are not a designer&#039;. The point I am making is that while in some cases programmers or other non-designers can come up with a good solution by accident or luck, designers are trained in understanding users and solving communication and usability problems. And that most people don&#039;t realize how bad they are at design because they don&#039;t respect that designing blind (without understanding the principles of what makes things work), is just the same as writing code without ever reading a book on programming foundations. You might get lucky and have something that works, but that doesn&#039;t mean that having an education doesn&#039;t greatly improve your chances of creating something that works well.

Compare the few lucky standout products you mentioned with the tens (hundreds?) of thousands of terrible ones and you&#039;ll see what I mean when I say people don&#039;t realize how bad they are when they create them.</description>
		<content:encoded><![CDATA[<p>Neil, you&#8217;ve hit the nail on the head with your last sentence. It&#8217;s the designer&#8217;s job to understand the psyche of the end user. Design is not about making things pretty. It&#8217;s about communication, usability, etc. </p>
<p>Google is an example of great design. One textbox, one button, easy to use and deliver&#8217;s google&#8217;s brand message: &#8216;we are search&#8217;. It doesn&#8217;t have to have rounded corners to be well designed. Same thing with facebook (well up until fb 2.0 I would say), an app designed to deliver information to users and stimulate communication. It succeeds at both. Of course there is room for improvement, but they&#8217;ve done a pretty good job.</p>
<p>I could have written a post that said &#8216;well in some cases it&#8217;s ok not to use a designer&#8217; but it wouldn&#8217;t have had the power of &#8216;you are not a designer&#8217;. The point I am making is that while in some cases programmers or other non-designers can come up with a good solution by accident or luck, designers are trained in understanding users and solving communication and usability problems. And that most people don&#8217;t realize how bad they are at design because they don&#8217;t respect that designing blind (without understanding the principles of what makes things work), is just the same as writing code without ever reading a book on programming foundations. You might get lucky and have something that works, but that doesn&#8217;t mean that having an education doesn&#8217;t greatly improve your chances of creating something that works well.</p>
<p>Compare the few lucky standout products you mentioned with the tens (hundreds?) of thousands of terrible ones and you&#8217;ll see what I mean when I say people don&#8217;t realize how bad they are when they create them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Cauldwell</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-18254</link>
		<dc:creator>Neil Cauldwell</dc:creator>
		<pubDate>Thu, 18 Dec 2008 07:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-18254</guid>
		<description>Judge this on a case-by-case basis, perhaps only if the project at hand is being designed, or led by, someone who isn&#039;t the target customer. There&#039;s many examples of successful products which have been &#039;designed&#039; by a programmer who simply wanted to build something that fixed a problem, or improved existing solutions (Napster, Facebook, Google?). On the other hand, I could also dig up examples of applications that would fit perfectly to grid design principles, but wouldn&#039;t be solving a problem particularly well because the designer didn&#039;t grasp the psyche of the end user.</description>
		<content:encoded><![CDATA[<p>Judge this on a case-by-case basis, perhaps only if the project at hand is being designed, or led by, someone who isn&#8217;t the target customer. There&#8217;s many examples of successful products which have been &#8216;designed&#8217; by a programmer who simply wanted to build something that fixed a problem, or improved existing solutions (Napster, Facebook, Google?). On the other hand, I could also dig up examples of applications that would fit perfectly to grid design principles, but wouldn&#8217;t be solving a problem particularly well because the designer didn&#8217;t grasp the psyche of the end user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raymond T. Hightower</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-18241</link>
		<dc:creator>Raymond T. Hightower</dc:creator>
		<pubDate>Thu, 18 Dec 2008 00:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-18241</guid>
		<description>Yan, this post is right on target and I thank you for publishing it. Greatness is largely a matter of knowing your strengths &amp; weaknesses. If you think you have aptitude in a certain field, got to school, read books, get a mentor/coach... do anything you can to learn it well.

If you&#039;re not willing to take the time to be great in a particular area, partner with someone who has that expertise. 

Michael Jordan, Michael Phelps, and Muhammad Ali are all masters in their fields. And each one needed a coach to get there!</description>
		<content:encoded><![CDATA[<p>Yan, this post is right on target and I thank you for publishing it. Greatness is largely a matter of knowing your strengths &amp; weaknesses. If you think you have aptitude in a certain field, got to school, read books, get a mentor/coach&#8230; do anything you can to learn it well.</p>
<p>If you&#8217;re not willing to take the time to be great in a particular area, partner with someone who has that expertise. </p>
<p>Michael Jordan, Michael Phelps, and Muhammad Ali are all masters in their fields. And each one needed a coach to get there!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yan</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-18232</link>
		<dc:creator>yan</dc:creator>
		<pubDate>Wed, 17 Dec 2008 18:47:28 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-18232</guid>
		<description>And yes, I agree, it&#039;s all about direction and guidance, this is why as the manager of a project, I make it a point to be educated about design so that I can not only hire the right talent but also guide the design in the right direction, and prevent it from being derailed by well intentioned people with an opinion, but no background or basis for making design decisions.</description>
		<content:encoded><![CDATA[<p>And yes, I agree, it&#8217;s all about direction and guidance, this is why as the manager of a project, I make it a point to be educated about design so that I can not only hire the right talent but also guide the design in the right direction, and prevent it from being derailed by well intentioned people with an opinion, but no background or basis for making design decisions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yan</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-18231</link>
		<dc:creator>yan</dc:creator>
		<pubDate>Wed, 17 Dec 2008 18:37:53 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-18231</guid>
		<description>What I was really pointing at with MS is that it&#039;s an engineering culture, a company founded by and run by engineering minded people. 

One of the interesting things you&#039;ll find in Steve Jobs&#039;s biography is how he points to a typography class he happened to take in directing the idea that the Mac should have good typography and font selection. This is not something Bill Gates would come up with. He&#039;s a great businessman and probably a pretty damn good engineer, but a designer he&#039;s not, so his company was not run in the same way as Steve ran his.

I also think it has to do with the design dictatorship at Apple vs design by committee at MS. It&#039;s always hard to tell people that they don&#039;t know what they&#039;re talking about when it comes to design, because everyone has an opinion, and as my post points out, everyone thinks their opinion is valid. I think at Apple it&#039;s been made clear that your opinion doesn&#039;t matter.

As far as MS creating &#039;far more successful&#039; products, while it&#039;s true they dominated and still dominate the market for most of their niches, a lot of that is attributed to early mover advantage and sheer money pumped into marketing and exploiting distribution channels set up early in the game (OEM Windows shipped with PC&#039;s). How many people do you know that truly _love_ their microsoft products in the way that apple users love theirs. 

Myspace is a terribly designed site that happened to be in the right place at the right time and had a large enough spam list that they could acquire users rapidly. Anyway, I wasn&#039;t suggesting that good design alone is responsible for Apple&#039;s success, or that badly designed products can&#039;t be successful (clearly they are), just trying to make people recognize that design is not an intuitive discipline that anyone can do, but requires knowledge and practice like anything else.</description>
		<content:encoded><![CDATA[<p>What I was really pointing at with MS is that it&#8217;s an engineering culture, a company founded by and run by engineering minded people. </p>
<p>One of the interesting things you&#8217;ll find in Steve Jobs&#8217;s biography is how he points to a typography class he happened to take in directing the idea that the Mac should have good typography and font selection. This is not something Bill Gates would come up with. He&#8217;s a great businessman and probably a pretty damn good engineer, but a designer he&#8217;s not, so his company was not run in the same way as Steve ran his.</p>
<p>I also think it has to do with the design dictatorship at Apple vs design by committee at MS. It&#8217;s always hard to tell people that they don&#8217;t know what they&#8217;re talking about when it comes to design, because everyone has an opinion, and as my post points out, everyone thinks their opinion is valid. I think at Apple it&#8217;s been made clear that your opinion doesn&#8217;t matter.</p>
<p>As far as MS creating &#8216;far more successful&#8217; products, while it&#8217;s true they dominated and still dominate the market for most of their niches, a lot of that is attributed to early mover advantage and sheer money pumped into marketing and exploiting distribution channels set up early in the game (OEM Windows shipped with PC&#8217;s). How many people do you know that truly _love_ their microsoft products in the way that apple users love theirs. </p>
<p>Myspace is a terribly designed site that happened to be in the right place at the right time and had a large enough spam list that they could acquire users rapidly. Anyway, I wasn&#8217;t suggesting that good design alone is responsible for Apple&#8217;s success, or that badly designed products can&#8217;t be successful (clearly they are), just trying to make people recognize that design is not an intuitive discipline that anyone can do, but requires knowledge and practice like anything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul birman</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-18229</link>
		<dc:creator>paul birman</dc:creator>
		<pubDate>Wed, 17 Dec 2008 18:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-18229</guid>
		<description>*were.  damn.. no edit button?</description>
		<content:encoded><![CDATA[<p>*were.  damn.. no edit button?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paul birman</title>
		<link>http://yanpritzker.com/2008/12/17/why-you-are-not-a-designer/comment-page-1/#comment-18228</link>
		<dc:creator>paul birman</dc:creator>
		<pubDate>Wed, 17 Dec 2008 18:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://skwpspace.com/2008/12/17/why-you-are-not-a-designer/#comment-18228</guid>
		<description>I&#039;m sure you&#039;re not suggesting that Zune and Vista was designed by Microsoft engineers.  People that worked on these projects are at the top of their industry... exactly the rare talent that you mention.

I think it&#039;s more about guidance, dedication and timing.  Clearly, MS created far more successful products for years.  Apple was struggling in terms of the mainstream market until the ipod came out.  But through all those years, they stayed true to the overall concept and when the time came, they were able to capitalize on its success.  Microsoft on the other hand panicked and completely overhauled their platform at first signs of serious competition.  So instead of innovation came imitation.  I think the talent was there, it was just guided in the wrong direction.

I completely agree with you that it&#039;s important to work with professionals and understand your own limitations.  But hiring the right talent and guiding them in the right direction is a far greater challenge.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure you&#8217;re not suggesting that Zune and Vista was designed by Microsoft engineers.  People that worked on these projects are at the top of their industry&#8230; exactly the rare talent that you mention.</p>
<p>I think it&#8217;s more about guidance, dedication and timing.  Clearly, MS created far more successful products for years.  Apple was struggling in terms of the mainstream market until the ipod came out.  But through all those years, they stayed true to the overall concept and when the time came, they were able to capitalize on its success.  Microsoft on the other hand panicked and completely overhauled their platform at first signs of serious competition.  So instead of innovation came imitation.  I think the talent was there, it was just guided in the wrong direction.</p>
<p>I completely agree with you that it&#8217;s important to work with professionals and understand your own limitations.  But hiring the right talent and guiding them in the right direction is a far greater challenge.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

