<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Nobody Comes To Work To Make A Bad Design</title>
	<atom:link href="http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 18 May 2013 00:44:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Joe</title>
		<link>http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/comment-page-1/#comment-174281</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Fri, 04 Nov 2011 12:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=5455#comment-174281</guid>
		<description>This seems targeted at designers (and I agree with it), but also consider this...

Many designers do good design and &quot;the right thing&quot;... complete with preliminary research, user testing, iteration, more testing, etc... only to have that good design destroyed (or severely crippled) by some other part of the team.

I&#039;m specifically thinking of the developers at my company, but this could also be another part of the project team such as a Product Manager, Stakeholders, etc. (or a combination thereof). It&#039;s a frustration felt time and time again by many &quot;corporate&quot; or &quot;in house&quot; designers.

We want (and do) the right thing, only to have it ultimately pooped-on in development due to &quot;technical limitations.&quot; The only limitation I ever see here is a lack of passion for their craft and lack of knowledge. That crowd just wants to lay low for 30 years and secure their pension--not do anything &#039;insanely great.&quot;

Coming from a design agency background, this frustrates me to no end.

Thanks for letting me vent.</description>
		<content:encoded><![CDATA[<p>This seems targeted at designers (and I agree with it), but also consider this&#8230;</p>
<p>Many designers do good design and &#8220;the right thing&#8221;&#8230; complete with preliminary research, user testing, iteration, more testing, etc&#8230; only to have that good design destroyed (or severely crippled) by some other part of the team.</p>
<p>I&#8217;m specifically thinking of the developers at my company, but this could also be another part of the project team such as a Product Manager, Stakeholders, etc. (or a combination thereof). It&#8217;s a frustration felt time and time again by many &#8220;corporate&#8221; or &#8220;in house&#8221; designers.</p>
<p>We want (and do) the right thing, only to have it ultimately pooped-on in development due to &#8220;technical limitations.&#8221; The only limitation I ever see here is a lack of passion for their craft and lack of knowledge. That crowd just wants to lay low for 30 years and secure their pension&#8211;not do anything &#8216;insanely great.&#8221;</p>
<p>Coming from a design agency background, this frustrates me to no end.</p>
<p>Thanks for letting me vent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Definition of Design - Adam Mc</title>
		<link>http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/comment-page-1/#comment-168507</link>
		<dc:creator>The Definition of Design - Adam Mc</dc:creator>
		<pubDate>Fri, 07 Oct 2011 23:40:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=5455#comment-168507</guid>
		<description>[...] This post was inspired by Jared Spool&#8217;s honest and accurate assessment of design today: http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/ [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was inspired by Jared Spool&#8217;s honest and accurate assessment of design today: <a href="http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/" rel="nofollow">http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/comment-page-1/#comment-167910</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Tue, 04 Oct 2011 16:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=5455#comment-167910</guid>
		<description>It&#039;s a great question, Erik.

In my opinion, it starts with good mentorship and coaching, followed by continual, direct exposure to the users working with the designs. 

If you have someone who is a poor designer, they need to know what to see and how to see it. A good mentor and coach can help point them in the right directions, opening up their thinking about what design is and how it works.

Then, they need a feedback loop. They need to see how their design decisions manifest themselves in the resulting behaviors of the users. When the designs produce the right behaviors, they are now on the right track. Most designers work without any real feedback about how their designs get used. The result is they are designing in the dark -- difficult enough for great designers and impossible for poor ones.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a great question, Erik.</p>
<p>In my opinion, it starts with good mentorship and coaching, followed by continual, direct exposure to the users working with the designs. </p>
<p>If you have someone who is a poor designer, they need to know what to see and how to see it. A good mentor and coach can help point them in the right directions, opening up their thinking about what design is and how it works.</p>
<p>Then, they need a feedback loop. They need to see how their design decisions manifest themselves in the resulting behaviors of the users. When the designs produce the right behaviors, they are now on the right track. Most designers work without any real feedback about how their designs get used. The result is they are designing in the dark &#8212; difficult enough for great designers and impossible for poor ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nobody Comes To Work To Make A Bad Design » UIE Brain Sparks &#124; UXWeb.info</title>
		<link>http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/comment-page-1/#comment-167799</link>
		<dc:creator>Nobody Comes To Work To Make A Bad Design » UIE Brain Sparks &#124; UXWeb.info</dc:creator>
		<pubDate>Mon, 03 Oct 2011 20:09:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=5455#comment-167799</guid>
		<description>[...] a lot of folks. Good folks, interested in creating really great products, services, and designs. Link &#8211; Trackbacks   Posted in User experience (UX) &#124; Permalink.    &#8592; Adobe Proto app &#8211; [...]</description>
		<content:encoded><![CDATA[<p>[...] a lot of folks. Good folks, interested in creating really great products, services, and designs. Link &#8211; Trackbacks   Posted in User experience (UX) | Permalink.    &larr; Adobe Proto app &#8211; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What separates bad design from good? &#171; Andrea Ong Pietkiewicz</title>
		<link>http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/comment-page-1/#comment-167795</link>
		<dc:creator>What separates bad design from good? &#171; Andrea Ong Pietkiewicz</dc:creator>
		<pubDate>Mon, 03 Oct 2011 19:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=5455#comment-167795</guid>
		<description>[...] Spool&#8217;s post today on the UIE blog is titled &#8220;Nobody comes to work to make a bad design&#8221; suggests that the cause of crappy designs is that  &#8220;the folks creating bad designs [...]</description>
		<content:encoded><![CDATA[<p>[...] Spool&#8217;s post today on the UIE blog is titled &#8220;Nobody comes to work to make a bad design&#8221; suggests that the cause of crappy designs is that  &#8220;the folks creating bad designs [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Burns</title>
		<link>http://www.uie.com/brainsparks/2011/10/03/nobody-comes-to-work-to-make-a-bad-design/comment-page-1/#comment-167793</link>
		<dc:creator>Erik Burns</dc:creator>
		<pubDate>Mon, 03 Oct 2011 18:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=5455#comment-167793</guid>
		<description>Thanks for the thoughts, Jared.  I would love to know how to turn a poor designer into a good, then great designer.  If we could do that, we could solve the huge in UX/UI that exists in the industry right now.

Seems like UIE design is a difficult subject area to transfer, since it requires hybrid left / right brain thinking, subject area expertise, spirit, instinct, and lots of practice.  Any tips on how to do it...?</description>
		<content:encoded><![CDATA[<p>Thanks for the thoughts, Jared.  I would love to know how to turn a poor designer into a good, then great designer.  If we could do that, we could solve the huge in UX/UI that exists in the industry right now.</p>
<p>Seems like UIE design is a difficult subject area to transfer, since it requires hybrid left / right brain thinking, subject area expertise, spirit, instinct, and lots of practice.  Any tips on how to do it&#8230;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
