<?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; Design Guidelines</title>
	<atom:link href="http://rodmotta.com/blog/category/design-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>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>The power of personas &#8211; a fun cartoon explanation</title>
		<link>http://rodmotta.com/blog/2010/02/25/the-power-of-personas-a-fun-cartoon-explanation/</link>
		<comments>http://rodmotta.com/blog/2010/02/25/the-power-of-personas-a-fun-cartoon-explanation/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 22:10:59 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Guidelines]]></category>
		<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[behaviour]]></category>
		<category><![CDATA[motivation]]></category>
		<category><![CDATA[personas]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=229</guid>
		<description><![CDATA[Check out this awesome job of explaining user personas through a fun comic created by Brad Colbow. Some topics are more easily understood when presented this way. (at least for me). The comic style brings what is essentially a “slightly” dry subject to life. A list of more resources about user personas and mental models [...]]]></description>
			<content:encoded><![CDATA[<p>Check out this awesome job of explaining <a title="User Personas through a fun comic created by Brad Colbow" href="http://carsonified.com/blog/design/how-to-understand-your-users-with-personas/" target="_blank">user personas through a fun comic created by Brad Colbow</a>. Some topics are more easily understood when presented this way. (at least for me). The comic style brings what is essentially a “slightly” dry subject to life.</p>
<p>A list of more resources about user personas and mental models are listed at the end of the post.</p>
<p>But seriously, we need more ponies on our websites ;-P</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2010/02/25/the-power-of-personas-a-fun-cartoon-explanation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick thought on Web vs Desktop design process</title>
		<link>http://rodmotta.com/blog/2009/11/07/web-vs-desktop-design-process/</link>
		<comments>http://rodmotta.com/blog/2009/11/07/web-vs-desktop-design-process/#comments</comments>
		<pubDate>Sun, 08 Nov 2009 02:39:32 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Guidelines]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[behaviour]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[patterns]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[user experience]]></category>
		<category><![CDATA[user interface]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=207</guid>
		<description><![CDATA[There is a world of differences to consider when designing for web or designing for desktop applications: From fundamental interactions to keyboard driven navigational paradigms to accessibility issues to screen layout to basic behavior and reaction of buttons, links, etc&#8230;we have to consider that a product with a rich client and a web client are [...]]]></description>
			<content:encoded><![CDATA[<p>There is a world of differences to consider when designing for web or designing for desktop applications:<br/><br />
From fundamental interactions to keyboard driven navigational paradigms to accessibility issues to screen layout to basic behavior and reaction of buttons, links, etc&#8230;we have to consider that a product with a rich client and a web client are two completely separate applications striving to assist the user in meeting the same goals. Of course, it is a little more complicated than that but perhaps it get us going in the right direction.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/11/07/web-vs-desktop-design-process/feed/</wfw:commentRss>
		<slash:comments>0</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>The importance of User Personas</title>
		<link>http://rodmotta.com/blog/2009/04/28/the-importance-of-user-personas/</link>
		<comments>http://rodmotta.com/blog/2009/04/28/the-importance-of-user-personas/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 06:10:28 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Design Guidelines]]></category>
		<category><![CDATA[personas]]></category>
		<category><![CDATA[psychological]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[user interface]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=129</guid>
		<description><![CDATA[According to Alan Cooper, author of About Face 3.0 with Robert Riemann and David Cronin, “The persona is a powerful, multipurpose design tool that helps overcome several problems that currently plague the development of digital products. Personas help designers: Determine what a product should do and how it should behave. Communicate with stakeholders, developers, and [...]]]></description>
			<content:encoded><![CDATA[<p>According to Alan Cooper, author of About Face 3.0 with Robert Riemann and David Cronin, “The persona is a powerful, multipurpose design tool that helps overcome several problems that currently plague the development of digital products. Personas help designers:</p>
<ul>
<li>Determine what a product should do and how it should behave.</li>
<li>Communicate with stakeholders, developers, and other designers.</li>
<li>Build consensus and commitment to the design.</li>
<li>Measure the design’s effectiveness.</li>
<li>Contribute to other product-related efforts such as marketing and sales plans.”</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/04/28/the-importance-of-user-personas/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>
