1988-norman-design-of-everyday-things.html

<h1><a href="https://www.amazon.com/Design-Everyday-Things-Revised-Expanded/dp/0465050654">Design of Everyday Things</a> - Don Norman</h1>
<hr/>
<link href="styles.css" rel="stylesheet"/>
<h2>tldr</h2>
<p>How to make products enjoyable to use.</p>
<h2>why bother reading this book?</h2>
<p>It is the gold-standard of the field, the UX version of <a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898">Lean Startup</a>.</p>
<p>Its ideas are widespread, and yet we make dumb UX mistakes all the time. Like statistics or moral philosophy, we probably need repeated exposure to Norman for the lessons to stick.</p>
<h2>the idea is simple</h2>
<p>The premise is that many products are designed poorly <em>for the end-user</em>.</p>
<p>This bit, 'for the end-user', is important. A poorly designed product could also be:</p>
<ul>
<li>finely wrought</li>
<li>expensive</li>
<li>fashionable</li>
</ul>
<p>And so, what should be obvious (the product sucks to use) can be masked if you never actually use the product.</p>
<p>Enter Don Norman. His antidote to the looks-nice-but-actually-sucks-to-use problem is 'human-centered design', which amounts to "do not make your product suck to use". </p>
<h2>practical advice</h2>
<p>Norman offers some rules of thumb for designers:</p>
<ul>
<li>controls should be proximate to what they control [page 136]</li>
<li>give feedback to the user [page 156]</li>
<li>avoid adding too many features [page 261]</li>
</ul>
<h2>the writing is bad</h2>
<p>Design of Everyday Things is not well written and is unenjoyable to read. </p>
<p>DoET falls into the category of a <a href="https://www.blinkist.com/en/">Blinkist</a> book. That is, 15 minutes of ideas spread across 200 pages.</p>
<p>Norman invents his own vocabulary:</p>
<blockquote>
<p>I call the signalling component of affordances 'signifiers' [page 13] </p>
<p>I call the combined information available to us the 'system image' [page 31]</p>
</blockquote>