<?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; guidelines</title>
	<atom:link href="http://rodmotta.com/blog/tag/guidelines/feed/" rel="self" type="application/rss+xml" />
	<link>http://rodmotta.com/blog</link>
	<description>Design, Social Media, Business &#38; Everything in Between.</description>
	<lastBuildDate>Sun, 05 Sep 2010 04:23:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<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[user interface]]></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>1</slash:comments>
		</item>
		<item>
		<title>The four layers of design</title>
		<link>http://rodmotta.com/blog/2009/05/08/the-four-layers-of-design/</link>
		<comments>http://rodmotta.com/blog/2009/05/08/the-four-layers-of-design/#comments</comments>
		<pubDate>Sat, 09 May 2009 00:11:57 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Design Guidelines]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[motivation]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=145</guid>
		<description><![CDATA[According to Bill Buxton on the article On Engineering and Design: An Open Letter, it might be useful to think of design in terms of four layers, each demanding a progressively larger investment. Design awareness can and ideally should be something that every employee of a company makes their best effort to acquire. I would [...]]]></description>
			<content:encoded><![CDATA[<p>According to Bill Buxton on the article <strong><a title="On Engineering and Design: An Open Letter" href="http://www.businessweek.com/innovate/content/apr2009/id20090429_083139.htm?campaign_id=rss_innovate" target="_blank">On Engineering and Design: An Open Letter</a></strong>, it might be useful to think of design in terms of four layers, each demanding a progressively larger investment.</p>
<ol>
<li><strong>Design awareness</strong> can and ideally should be something that every employee of a company makes their best effort to acquire. I would say exactly the same thing about technology awareness. In the corporate culture I dream about, there would be a balance between the two—along with a healthy respect for best business practices—in every employee.</li>
<li><strong>Design literacy</strong> is also something that can be acquired with a bit more effort by any employee, regardless of background. If your company has employees who suffer from &#8220;Apple (AAPL) envy&#8221; in terms of the nature of the products that they produce, building such literacy is a very real and useful step in helping combat that particular affliction. Designers need technological literacy, too, and both need an equal dose of business acumen. Without this, none of us has any right to complain about not being understood by those in other disciplines. We all need to be able to handle multiple directions.</li>
<li><strong>Design thinking</strong> is something that takes even more of an investment, requiring a level of competence that—with dedication and practice—can be acquired by anyone, to a reasonable degree. Cognitive science makes it clear that the strategies designers use in approaching problems or questions are different (not &#8220;better&#8221;) than those employed by those trained in engineering disciplines. Both strategies are complementary. Given the complexity of the problems that confront us, it seems to me that expanding our collective arsenal of techniques is something we could all benefit from.</li>
<li><strong>Design practice</strong>, however, is not something available to everyone. This is a full-time job for highly trained professionals. It requires people who have invested just as much to acquire their set of skills as the computer scientists have put in for theirs. Yes, there are exceptions. There always are on both sides of the table. But it is risky, if not foolhardy, to generalize from the exception.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/05/08/the-four-layers-of-design/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>
	</channel>
</rss>
