<?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>John Bullard &#187; Don Norman</title>
	<atom:link href="http://johnbullard.net/tag/don-norman/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnbullard.net</link>
	<description>Loose Thinking, Tight Analysis</description>
	<lastBuildDate>Tue, 12 Jan 2010 14:32:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Design of Everday Things</title>
		<link>http://johnbullard.net/2009/03/13/the-design-of-everday-things/</link>
		<comments>http://johnbullard.net/2009/03/13/the-design-of-everday-things/#comments</comments>
		<pubDate>Fri, 13 Mar 2009 21:37:17 +0000</pubDate>
		<dc:creator>John</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Don Norman]]></category>

		<guid isPermaLink="false">http://johnbullard.net/?p=154</guid>
		<description><![CDATA[
The seminal work on design philosophy. In just over 200 pages Don Norman details the psychological principles of design. The book was written in 1988, so  the examples may be a little dated, but the principles remain the same. 

Visibility
Feedback
Affordances
Natural Mappings
Constraints

I feel like a switch has been turned. I&#8217;m constantly evaluating the design of [...]]]></description>
			<content:encoded><![CDATA[<p><center><img src="http://i21.photobucket.com/albums/b271/kangaegoto/b8fa733296094eeea6393cc675ecebe3.jpg"/></center></p>
<p>The seminal work on design philosophy. In just over 200 pages Don Norman details the psychological principles of design. The book was written in 1988, so  the examples may be a little dated, but the principles remain the same. </p>
<ul>
<li>Visibility</li>
<li>Feedback</li>
<li>Affordances</li>
<li>Natural Mappings</li>
<li>Constraints</li>
</ul>
<p>I feel like a switch has been turned. I&#8217;m constantly evaluating the design of various objects. I&#8217;ve always noticed poor design (everyone does, it&#8217;s annoying) but now I&#8217;m excited by fantastic design. When something is designed such that I can accomplish my task without breaking my train of thought, that&#8217;s great design. It should &#8220;win a prize.&#8221; Doors are of constant scrutiny after finishing this book. I cringe when confronted with a vertical handle that needs to be pushed or a horizontal bar with &#8220;PULL&#8221; on it. An amusing example: <a href="http://jonoscript.wordpress.com/2009/02/12/whats-wrong-with-this-door/" target="_blank">What&#8217;s Wrong with this Door << Not the User's Fault</a>.</p>
<p>The book concentrates on physical objects (ie the &#8216;Norman Door&#8217;), but there is no reason the idea&#8217;s can&#8217;t translate to UX. The chapter on poor design and user error was especially interesting.</p>
<blockquote><p>I point out that the design is faulty and that others make the same errors. Still, if the task appears simple or trivial, then <em>people blame themselves</em></p></blockquote>
<p>I encounter this all the time with technology. Poorly designed software can turn people off from computers completely. Developers have gotten quite a bit better at this over time. Microsoft Office 2007 and it&#8217;s ribbon menu was a bold redesign, which payed off well. </p>
<p>Great design flows without interruption. It is modeled with human interaction in mind, requiring no instructions or labels.</p>
<blockquote><p>Wherever labels seem necessary, consider another design.</p></blockquote>
<p>It&#8217;s a great point. By utilizing constraints, natural mappings, and visiblity a designer can communicate with the user. No instructions needed. </p>
<p>Sometimes designers utilize these principles incorrectly or by accident. Users are then communicated bad information and errors result. </p>
<blockquote><p>When someone makes an error, there usually is good reason for it</p></blockquote>
<p><b>A few other tidbits I found interesting:</b></p>
<blockquote><p>Whenever the number of functions and required operations exceeds the number of controls, the design becomes arbitrary.</p></blockquote>
<p>ie, the digital watch my Dad can never program. </p>
<p>And just how important design is:</p>
<blockquote><p>Suppose that each everyday thing takes only a minute to learn; learning 20,00 of them occupies 20,000 minutes &#8211; 33 hours or about 8 forty hour work weeks.</p>
<p>How do people cope?</p>
<p>Part of the answer lies in the <b>information available from the appearance of the objects</b> and part comes from the <b>ability of the designer to make the operation clear</b>. </p></blockquote>
<p>All things considered the book was a fantastic read. It delivers a foundation for my interest in UX. I&#8217;m looking forward to reading more of Norman&#8217;s work. </p>
<p class="fbconnect_share"><fb:share-button class="url" href="http://johnbullard.net/2009/03/13/the-design-of-everday-things/" /></p>]]></content:encoded>
			<wfw:commentRss>http://johnbullard.net/2009/03/13/the-design-of-everday-things/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

