<?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: Designing for People</title>
	<atom:link href="http://designingforexperience.com/2008/07/11/designing-for-people/feed/" rel="self" type="application/rss+xml" />
	<link>http://designingforexperience.com/2008/07/11/designing-for-people/</link>
	<description>A Holistic Approach to Design for People, Interaction, &#38; Business</description>
	<lastBuildDate>Wed, 17 Mar 2010 04:43:36 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: aaronh</title>
		<link>http://designingforexperience.com/2008/07/11/designing-for-people/comment-page-1/#comment-178</link>
		<dc:creator>aaronh</dc:creator>
		<pubDate>Wed, 23 Jul 2008 15:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://designingforexperience.com/?p=54#comment-178</guid>
		<description>Good points Brandon, and I honestly would encourage smaller companies to run their own tests once they feel comfortable with it and bring in someone to help them interpret results (and to help them design the tests if they are pretty serious about it).  This springs from the ideas in Steve Krug&#039;s book Don&#039;t Make Me Think.  As a company grows, or as a large company grows more aware of the incredible value of designing for their customers wants and needs, and having a solid methodology and a change in mindset they will start creating UX groups or hiring UX people into their cross-disciplinary groups.

Overall it is the ability to take what you get from designing with your audience and turn that into actionable items that is the real strength that most UX professionals bring to the table.</description>
		<content:encoded><![CDATA[<p>Good points Brandon, and I honestly would encourage smaller companies to run their own tests once they feel comfortable with it and bring in someone to help them interpret results (and to help them design the tests if they are pretty serious about it).  This springs from the ideas in Steve Krug&#8217;s book Don&#8217;t Make Me Think.  As a company grows, or as a large company grows more aware of the incredible value of designing for their customers wants and needs, and having a solid methodology and a change in mindset they will start creating UX groups or hiring UX people into their cross-disciplinary groups.</p>
<p>Overall it is the ability to take what you get from designing with your audience and turn that into actionable items that is the real strength that most UX professionals bring to the table.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://designingforexperience.com/2008/07/11/designing-for-people/comment-page-1/#comment-174</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Tue, 22 Jul 2008 21:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://designingforexperience.com/?p=54#comment-174</guid>
		<description>I think that you should mention some information about distilling the data that you receive from the users into implementable results. The reason for this is that is where we, the designers, shine. Usability is quite simple to learn how to do. Most people can surely run a test or a card sort, but it is in the understanding the results where the difficulty appears and remains. 

By making it apparent to non-designers that they are looking for your help in understanding the results, I think you will gather more faith from them in your abilities. As they may think through the process, &quot;I can do this. Why are we paying him again?&quot; On that note, they probably could run a test, maybe not create it or catch important feedback during the test as well as we can, but finding the results will most definitely lose them.

Just a few thoughts :)</description>
		<content:encoded><![CDATA[<p>I think that you should mention some information about distilling the data that you receive from the users into implementable results. The reason for this is that is where we, the designers, shine. Usability is quite simple to learn how to do. Most people can surely run a test or a card sort, but it is in the understanding the results where the difficulty appears and remains. </p>
<p>By making it apparent to non-designers that they are looking for your help in understanding the results, I think you will gather more faith from them in your abilities. As they may think through the process, &#8220;I can do this. Why are we paying him again?&#8221; On that note, they probably could run a test, maybe not create it or catch important feedback during the test as well as we can, but finding the results will most definitely lose them.</p>
<p>Just a few thoughts <img src='http://designingforexperience.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
