<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rod Motta - User Experience Visual Designer &#187; feedback</title>
	<atom:link href="http://rodmotta.com/blog/tag/feedback/feed/" rel="self" type="application/rss+xml" />
	<link>http://rodmotta.com/blog</link>
	<description>Design, Social Media, Business &#38; Everything in Between.</description>
	<lastBuildDate>Mon, 07 May 2012 23:14:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Identifying Users&#8217; Trigger Words</title>
		<link>http://rodmotta.com/blog/2011/06/19/identifying-users-trigger-words/</link>
		<comments>http://rodmotta.com/blog/2011/06/19/identifying-users-trigger-words/#comments</comments>
		<pubDate>Sun, 19 Jun 2011 20:57:42 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Guidelines]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[redesign]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[feedback]]></category>
		<category><![CDATA[personas]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=298</guid>
		<description><![CDATA[Jarred Spool wrote an interesting article, back in 2004, about the right trigger words for your user. Do you want to find out what those words are? Start by asking them. Visiting your users in their natural environments is probably the best way to start. Jarred&#8217;s team found that personas are a great way to [...]]]></description>
			<content:encoded><![CDATA[<p>Jarred Spool wrote an interesting article, back in 2004, about <a title="The Right Trigger Words" href="http://www.uie.com/articles/trigger_words/" target="_blank">the right trigger words for your user</a>.</p>
<p>Do you want to find out what those words are? Start by asking them. Visiting your users in their natural environments is probably the best way to start.</p>
<p>Jarred&#8217;s team found that personas are a great way to communicate trigger words to   everyone on the design team. A <a title="Death to Personas and Long Live Personas" href="http://www.slideshare.net/ebacon/death-to-personas-long-live-personas-presentation" target="_blank">persona</a> is a detailed description of a user   the team wants to ensure is successful on the site. Listing, within the persona,   the trigger words that person would use helps us, the designers, understand how   the users&#8217; own language will impact the final design.</p>
<p>According to Jarred, his team never conducted a usability test that didn&#8217;t yield tremendous   insight into how users react to the links the team is using. It becomes obvious   immediately when links are missing the clues the users need to go forward.</p>
<p>This powerful trio &#8212; field studies, personas, and usability testing &#8212; are   a great way to start identifying the trigger words that work for your users.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2011/06/19/identifying-users-trigger-words/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The pleasing paradox phenomenon</title>
		<link>http://rodmotta.com/blog/2009/08/07/the-pleasing-paradox-phenomenon/</link>
		<comments>http://rodmotta.com/blog/2009/08/07/the-pleasing-paradox-phenomenon/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 21:32:18 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[feedback]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=181</guid>
		<description><![CDATA[We try so hard to please our client(s) that we fail to do what would be truly pleasing. That includes also giving our client critical feedback. The challenge is to be of service without becoming servile. We shouldn’t elevate any customer to the role of superior being, but treat each with human respect. The key [...]]]></description>
			<content:encoded><![CDATA[<p>We try so hard to please our client(s) that we fail to do what would be truly pleasing. That includes also giving our client critical feedback.</p>
<p><span>The challenge is to be of service without becoming servile. We shouldn’t elevate any customer to the role of superior being, but treat each with human respect.</span></p>
<p><span>The key to becoming a stellar service provider lies in making only responsible commitments. This requires not simply being knowledgeable about what must be done but “no-legible” about how preferences resolve into satisfying results. We must know how and when to say, “No,” because no one can know what will finally emerge as best. Client and designer will have to discover what constitutes best, and this always means stumbling through some uncomfortable territory together.</span></p>
<p>It’s crazy how much more satisfying to it is when you are able to present an even better solution to the problem they were really hoping for when they were offering suggestions or ideas.</p>
<p>Of course you’ve heard this Henry Ford quote a hundred times:<br />
&#8220;If I had asked my customers what they wanted, they would have said a faster horse.”</p>
<p>Or Tom Kelley&#8217;s (IDEO&#8217;s general manager) translation of that:<br />
&#8220;Customers don’t envision the future, they inform the present.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/08/07/the-pleasing-paradox-phenomenon/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design feedback</title>
		<link>http://rodmotta.com/blog/2009/06/29/design-feedback/</link>
		<comments>http://rodmotta.com/blog/2009/06/29/design-feedback/#comments</comments>
		<pubDate>Tue, 30 Jun 2009 05:42:55 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[feedback]]></category>
		<category><![CDATA[website evaluation]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=173</guid>
		<description><![CDATA[After reading the &#8220;Feedback. The creative killer&#8221; article I came to 4 conclusions: When ignoring an experienced and talented designer, your organization will only waste more dollars &#8220;trying out&#8221; everyone&#8217;s ideas, testing what&#8217;s been tested, ad nauseum, etc.  As far as handling feedback, I don&#8217;t think it&#8217;s the designer&#8217;s responsibility to manage feedback process. Typically, [...]]]></description>
			<content:encoded><![CDATA[<p>After reading the &#8220;<a title="Feedback. The Creative Killer" href="http://sixrevisions.com/project-management/feedback-the-creativity-killer/" target="_blank"><strong>Feedback. The creative killer</strong></a>&#8221; article I came to 4 conclusions:</p>
<ol>
<li>When ignoring an experienced and talented designer, your organization will only waste more dollars &#8220;trying out&#8221; everyone&#8217;s ideas, testing what&#8217;s been tested, ad nauseum, etc. </li>
<li>As far as handling feedback, I don&#8217;t think it&#8217;s the designer&#8217;s responsibility to manage feedback process. Typically, a designer is hit with competing and often conflicting feedback from every direction&#8211; an overwhelming experience that often includes a healthy dosage of office politicking. The design team manager (or any manager) should set rules for unsolicited feedback. I think designers should not be forced to balance conflicting executive feedback. </li>
<li>Design input is always valuable and fresh eyes often can see overlooked design weaknesses, but a business/client should understand years of design experience is worth something. </li>
<li>Being a good designer is not only a matter of creating great work, but being able to work with various stakeholders to successfully deliver the project.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/06/29/design-feedback/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

