<?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; usability</title>
	<atom:link href="http://rodmotta.com/blog/category/usability/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>An intuitive design is&#8230;</title>
		<link>http://rodmotta.com/blog/2011/09/29/an-intuitive-design-is/</link>
		<comments>http://rodmotta.com/blog/2011/09/29/an-intuitive-design-is/#comments</comments>
		<pubDate>Fri, 30 Sep 2011 00:28:44 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Simplicity]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[behavior]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[patterns]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=308</guid>
		<description><![CDATA[Recently, I had the opportunity to watch Jared Spool’s great talk on First Use Experience. In his talk, he argued that an intuitive design is: When the user is focused on their objective and not on the actual interface itself Invisible (user only pay attention to something intuitive when it&#8217;s actually not intuitive. What makes [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, I had the opportunity to watch Jared Spool’s great talk on First Use Experience. In his talk, he argued that an intuitive design is:</p>
<ul>
<li>When the user is focused on their objective and not on the actual interface itself</li>
<li>Invisible (user only pay attention to something intuitive when it&#8217;s actually not intuitive. What makes something intuitive is actually something personal. We have to know something about the people we are building for</li>
<li>When <a title="Current Knowledge and Target Knowledge are at the same place" href="http://www.uie.com/articles/design_intuitive/" target="_blank">Current Knowledge and Target Knowledge are at the same place</a>. There are two ways to accomplish this: Raise Current Knowledge to meet Target Knowledge (Training), or reduce Target Knowledge to meet Current Knowledge (Simplifying)</li>
<li>Is all about focuses on experience. Trend/ Pattern we see over and over again: Technology &gt; Features &gt; Experience</li>
<li>Is a result of constant team critique, and critiques are essential to creating intuitive designs.</li>
</ul>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2011/09/29/an-intuitive-design-is/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>Adding &#8220;beautiful&#8221; enhancements to our designs</title>
		<link>http://rodmotta.com/blog/2010/08/31/adding-beautiful-enhancements-to-our-designs/</link>
		<comments>http://rodmotta.com/blog/2010/08/31/adding-beautiful-enhancements-to-our-designs/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 05:35:08 +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[branding]]></category>
		<category><![CDATA[Simplicity]]></category>
		<category><![CDATA[visual design]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=243</guid>
		<description><![CDATA[We, designers, need to consider two things when adding “beautiful” enhancements to our designs. Responsive and intuitive page elements Branding and consistency of theme. Focusing on these two things will give every pixel in a design a purpose and will contribute to the website’s overall usability. Sure, eye candy is important, but it isn’t everything, [...]]]></description>
			<content:encoded><![CDATA[<p>We, designers, need to consider two things when adding “beautiful” enhancements to our  designs.</p>
<ol>
<li>Responsive and intuitive page elements</li>
<li>Branding  and consistency of theme.</li>
</ol>
<p>Focusing on these two things will  give every pixel in a design a purpose and will contribute to the  website’s overall usability. Sure, eye candy is important, but it isn’t everything, and  that for a design to be truly beautiful, it has to be functional, have  purpose and contribute in some way to the website’s intuitiveness,  usefulness and branding. All of these things contribute to the overall effect of a design.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2010/08/31/adding-beautiful-enhancements-to-our-designs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tufte is going to Washington!</title>
		<link>http://rodmotta.com/blog/2010/03/30/tufte-is-going-to-washington/</link>
		<comments>http://rodmotta.com/blog/2010/03/30/tufte-is-going-to-washington/#comments</comments>
		<pubDate>Tue, 30 Mar 2010 20:09:44 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[redesign]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[economic]]></category>
		<category><![CDATA[trends]]></category>
		<category><![CDATA[website evaluation]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=236</guid>
		<description><![CDATA[On March 5, Tufte was appointed by Obama to a panel to advise the Recovery Accountability and Transparency Board, which monitors the way the $787 billion in the stimulus package is being spent. Tufte’s initial work will be on the recovery.gov website, which is the primary way the board will conduct business transparently to the [...]]]></description>
			<content:encoded><![CDATA[<p>On March 5, Tufte was appointed by Obama to a panel to advise the Recovery Accountability and Transparency Board, which monitors the way the $787 billion in the stimulus package is being spent.</p>
<p>Tufte’s initial work will be on the <strong><a href="http://recovery.gov/" target="_">recovery.gov</a></strong> website, which is the primary way the board will conduct business transparently to the American public.</p>
<p>Wonder if he brought his own litter of kittens, or will be borrowing them from DC shelters…?</p>
<p><a href="http://rodmotta.com/blog/wp-content/uploads/2010/03/tufte_powerpoint.gif"><img class="alignnone size-full wp-image-237" title="tufte_powerpoint" src="http://rodmotta.com/blog/wp-content/uploads/2010/03/tufte_powerpoint.gif" alt="You make a Powerpoint, Edward Tufte kills a kitten" width="500" height="314" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2010/03/30/tufte-is-going-to-washington/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What designers need to keep in mind</title>
		<link>http://rodmotta.com/blog/2009/09/18/what-designers-need-to-keep-in-mind/</link>
		<comments>http://rodmotta.com/blog/2009/09/18/what-designers-need-to-keep-in-mind/#comments</comments>
		<pubDate>Fri, 18 Sep 2009 23:13:36 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[Quotes]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[industrial design]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=188</guid>
		<description><![CDATA[&#8220;Designing well is not easy. The manufacturer wants something that can be produced economically. The store wants something that will be attractive to its customers. The purchaser has several demands. In the store, the purchaser focuses on price and appearance, and perhaps on prestige value. At home, the same person will pay more attention to [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;Designing well is not easy. The manufacturer wants something that can be produced economically. The store wants something that will be attractive to its customers. The purchaser has several demands. In the store, the purchaser focuses on price and appearance, and perhaps on prestige value. At home, the same person will pay more attention to functionality and usability. The repair service cares about maintainability: How easy is the device to take apart, diagnose, and service:? The needs of those concerned are different and often conflict. Nonetheless, the designer may be able to<br />
satisfy everyone.&#8221;</p>
<p>From the book <strong><a href="http://www.amazon.com/Design-Everyday-Things-ebook/dp/B0018OZZM0/ref=dp_kinw_strp_1" target="_blank">The Design of Everyday Things</a></strong> by Don Norman.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/09/18/what-designers-need-to-keep-in-mind/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is breaking the rules okay when a design calls for it?</title>
		<link>http://rodmotta.com/blog/2009/06/17/breaking-the-rules-is-okay-when-a-design-calls-for-it/</link>
		<comments>http://rodmotta.com/blog/2009/06/17/breaking-the-rules-is-okay-when-a-design-calls-for-it/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 05:36:13 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[navigation]]></category>
		<category><![CDATA[patterns]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[visual design]]></category>
		<category><![CDATA[website evaluation]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=166</guid>
		<description><![CDATA[This 10 web design rules that you can break article, made me realize that “Rules you should break” or “Standards you shouldn’t follow” articles appeal to everyone rebel side. Some of you guys may wonder what Jakob Nielsen would say to “Breaking the rules is okay when a design calls for it”. I think rules [...]]]></description>
			<content:encoded><![CDATA[<p>This <strong><a href="http://www.webdesignerdepot.com/2009/06/10-web-design-rules-that-you-can-break/">10 web design rules that you can break</a></strong> article, made me realize that “Rules you should break” or “Standards you shouldn’t follow” articles appeal to everyone rebel side. Some of you guys may wonder what Jakob Nielsen would say to “Breaking the rules is okay when a design calls for it”.</p>
<p>I think rules #4 &#8220;Make your site&#8217;s goal obvious&#8221;, #5 &#8220;Navigation should be easy to figure out&#8221;, #7 &#8220;Don&#8217;t put animation in the way of your content&#8221; and #9 &#8220;Don&#8217;t have a splash/landing page&#8221; can be broken for personal portfolio or some entertainment sites, where a more creative approach might be appropriate, but not so much for e-commerce, news or corporate sites.</p>
<p>#6 &#8220;Use different colors for the text and background&#8221; should be &#8220;Use Contrast between Text and Background&#8221;, not different colors. Most of the examples here use variations of the base color, and use contrast to make the text readable, just like it supposed to be.</p>
<p>#8 &#8220;Stick to web-safe fonts&#8221;: I’m getting into using Cufon and Typeface.js (I used it for 2 projects), they offer a great solution in terms of progressive enhancement (better than sIFR), and think this is one area where the old rules no longer apply.</p>
<p>I also liked the tables joke and the tone it sets to encourage designers not to be so serious all the time!</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/06/17/breaking-the-rules-is-okay-when-a-design-calls-for-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The user experience from outside of the computer world</title>
		<link>http://rodmotta.com/blog/2009/05/22/the-user-experience-from-outside-of-the-computer-world/</link>
		<comments>http://rodmotta.com/blog/2009/05/22/the-user-experience-from-outside-of-the-computer-world/#comments</comments>
		<pubDate>Fri, 22 May 2009 22:50:47 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[redesign]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[industrial design]]></category>
		<category><![CDATA[ux]]></category>
		<category><![CDATA[visual]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=149</guid>
		<description><![CDATA[Checkout the story of redesign of the ubiquitous prescription bottle led by Deborah Adler I really enjoyed the article&#8217;s approach to guiding the reader through the process, and the result is stunning&#8230;Just far enough out of the box to be a real improvement, but not so unfamiliar as to make it un-marketable. I don’t see [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://nymag.com/nymetro/health/features/11700/"><img class="alignnone size-full wp-image-150" title="prescription_bottle" src="http://rodmotta.com/blog/wp-content/uploads/2009/05/prescription_bottle.jpg" alt="prescription_bottle" width="430" height="224" /></a></p>
<p>Checkout the <a href="http://nymag.com/nymetro/health/features/11700/"><strong>story of redesign of the ubiquitous prescription bottle</strong></a> led by Deborah Adler</p>
<p>I really enjoyed the article&#8217;s approach to guiding the reader through the process, and the result is stunning&#8230;Just far enough out of the box to be a real improvement, but not so unfamiliar as to make it un-marketable.</p>
<p>I don’t see a mention of this in the article, but judging from the bottles’ shape they can be packed more tightly to save shipping space and costs, as well.</p>
<p>You can see Debora Adler speak at <a href="http://videos.visitmix.com/MIX09/KEY02"><strong>Microsoft Mixx 09 Day 2 Keynote</strong></a>. (fast forward to 30:30)</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/05/22/the-user-experience-from-outside-of-the-computer-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Neat visual nav</title>
		<link>http://rodmotta.com/blog/2009/05/05/neat-visual-nav/</link>
		<comments>http://rodmotta.com/blog/2009/05/05/neat-visual-nav/#comments</comments>
		<pubDate>Wed, 06 May 2009 05:08:54 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[behavior]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[layout]]></category>
		<category><![CDATA[patterns]]></category>
		<category><![CDATA[visual]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=133</guid>
		<description><![CDATA[Neat visual nav at Stylous.com. Check it out in action to see how it works.]]></description>
			<content:encoded><![CDATA[<p><a href="http://stylous.com/#/"><img class="alignnone size-full wp-image-136" style="border: 0pt none;" title="Stylous" src="http://rodmotta.com/blog/wp-content/uploads/2009/05/stylous2.jpg" alt="stylous2" width="430" height="361" /></a></p>
<p>Neat visual nav at <strong><a href="http://stylous.com/#/" target="_blank">Stylous.com</a></strong>. Check it out in action to see how it works.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/05/05/neat-visual-nav/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User Interface Guidelines</title>
		<link>http://rodmotta.com/blog/2009/04/20/user-interface-guidelines/</link>
		<comments>http://rodmotta.com/blog/2009/04/20/user-interface-guidelines/#comments</comments>
		<pubDate>Tue, 21 Apr 2009 06:29:16 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Guidelines]]></category>
		<category><![CDATA[Quotes]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[nokia]]></category>
		<category><![CDATA[style guide]]></category>
		<category><![CDATA[visual]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=104</guid>
		<description><![CDATA[This is a great list of references for user interface design and usability guidelines: Apple Human Interface Guidelines iPhone Human Interface Guidelines Windows Vista UX Guidelines Windows XP Design Guidelines Nokia UI Style/Visual Guidelines GNOME Human Interface Guidelines 2.2 KDE 4.0 Visual Guide Java Look and Feel Design Guidelines Comcast Style Guide Usability.gov Research-Based Web [...]]]></description>
			<content:encoded><![CDATA[<p>This is a great list of references for user interface design and usability guidelines:</p>
<ul>
<li> <a href="http://developer.apple.com/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html">Apple Human Interface Guidelines</a></li>
<li> <a href="http://developer.apple.com/iphone/library/documentation/UserExperience/Conceptual/MobileHIG/Introduction/Introduction.html"> iPhone Human Interface Guidelines</a></li>
<li> <a href="http://msdn2.microsoft.com/en-us/library/aa511258.aspx">Windows Vista UX Guidelines</a></li>
<li> <a href="http://download.microsoft.com/download/whistler/xpv/1.0a/WXP/EN-US/WindowsXP_DesignGuidelines.exe">Windows XP Design Guidelines</a></li>
<li> <a href="http://www.forum.nokia.com/Resources_and_Information/Documentation/Usability/UI_Style_and_Visual_Guidelines.xhtml">Nokia UI Style/Visual Guidelines</a></li>
<li> <a href="http://library.gnome.org/devel/hig-book/stable">GNOME Human Interface Guidelines 2.2</a></li>
<li> <a href="http://www.kde.org/announcements/4.0/guide.php">KDE 4.0 Visual Guide</a></li>
<li> <a href="http://java.sun.com/products/jlf/ed2/book/">Java Look and Feel Design Guidelines</a></li>
<li> <a href="http://www.nulinegraphics.com/styleguide.html">Comcast Style Guide</a></li>
<li> <a href="http://www.usability.gov/pdfs/guidelines.html">Usability.gov Research-Based Web Design and Usability Guidelines</a></li>
<li> <a href="http://www.alistapart.com/articles/writingainterfacestyleguide">Writing an Interface Style Guide</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/04/20/user-interface-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quote: Usability isn&#8217;t enough</title>
		<link>http://rodmotta.com/blog/2009/04/01/quote-usability-isnt-enough/</link>
		<comments>http://rodmotta.com/blog/2009/04/01/quote-usability-isnt-enough/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 20:44:48 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[usability]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://rodmotta.wordpress.com/?p=62</guid>
		<description><![CDATA[&#8220;Usability is always secondary. It&#8217;s never the most important thing about an experience. I will accept poor usability if I get what I need, if the total experience is great. I will reject perfect usability if I am not rewarded with a useful, engaging experience.&#8221; - Donald Norman, author of &#8220;The Design of Everyday Things&#8221;]]></description>
			<content:encoded><![CDATA[<p><span class="bodysmall">&#8220;Usability is always secondary. It&#8217;s never the most important thing about an experience. I will accept poor usability if I get what I need, if the total experience is great. I will reject perfect usability if I am not rewarded with a useful, engaging experience.&#8221;</span></p>
<p><em><span class="bodysmall">- </span><span class="bodysmall">Donald Norman, author of &#8220;The Design of Everyday Things&#8221;</span></em></p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/04/01/quote-usability-isnt-enough/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

