<?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>Solid State UX &#187; taxonomy &amp; nomenclature</title>
	<atom:link href="http://www.solidstateux.com/tag/taxonomy-nomenclature/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.solidstateux.com</link>
	<description>The art and science of interaction design.</description>
	<lastBuildDate>Wed, 07 Jul 2010 16:08:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<image>
  <link>http://www.solidstateux.com</link>
  <url>http://www.solidstateux.com//wp-includes/favicon.ico</url>
  <title>Solid State UX</title>
</image>
		<item>
		<title>Anti-Pattern:  Competing Meanings in Website Nomenclature</title>
		<link>http://www.solidstateux.com/interaction-design/anti-pattern-competing-meanings-in-website-nomenclature/</link>
		<comments>http://www.solidstateux.com/interaction-design/anti-pattern-competing-meanings-in-website-nomenclature/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 14:01:04 +0000</pubDate>
		<dc:creator>Todd Toler</dc:creator>
				<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[antipatterns]]></category>
		<category><![CDATA[taxonomy & nomenclature]]></category>

		<guid isPermaLink="false">http://www.solidstateux.com/?p=967</guid>
		<description><![CDATA[Yes, a love of words makes you a better IA.]]></description>
			<content:encoded><![CDATA[<div id="attachment_997" class="wp-caption alignleft" style="width: 383px"><img class="size-full wp-image-997" title="fake_nav" src="http://www.solidstateux.com/wp-content/uploads/2009/10/fake_nav2.png" alt="fake_nav" width="373" height="95" /><p class="wp-caption-text">Yes.  A love of words makes you a better IA.</p></div>
<p><a href="http://www.wordnik.com">Wordnik.com</a> doesn&#8217;t jump to mind as an obvious resource for an interaction designer.  For a dedicated Sunday puzzle solver?  You bet. Or if you have a <em>grandiloquent</em> and <em>sesquipedalian</em> consulting style (pompous and prone to long words), then this is your place &#8211; btw, remind me not to hire you.  I read Wordnik fairly regularly  and am now a self-diagnosed <em>cremnophobic</em> (one who has a morbid fear of being near the edge of a cliff, precipice, or abyss)  and I also know the difference between an <em>acronym</em>, like ACORN, and an <em>initialism</em>, like NAACP (one spells out a word and one doesn&#8217;t).  But geeking out on words sharpens an important instinct for anybody who trades in the design of screens-  a fetish for precision in language.   Obsessing over language will keep you from repeatedly stumbling into what  is perhaps the most common antipattern of all &#8211; vagueness and ambiguity.    Here&#8217;s three main themes to keep in mind when choosing words for your wireframes or designs:</p>
<p><span id="more-967"></span></p>
<p><span style="color: #000000;"><strong>1. The best choice for a word is the one with the fewest competing meanings.</strong></span></p>
<p><span style="color: #000000;">I used to phrase this point differently.  Avoid <em>ambiguous</em> words, I&#8217;d advise, which lays the ground for debate on which words are ambiguous and which are not.   Entirely subjective.   But flip the phrase around so that you are identifying words with <em>competing meanings</em> and you have a powerful tool for analyzing language.   Name all the competing meanings for a word or phrase and the winning selection will generally have the fewest.  Period.  I learned this strategy by hearing a Wordnik.com editor discuss how new words for the English language are evaluated and selected.  Geico uses the term &#8220;Claims Center&#8221; in their global nav, whereas competitors Farmers and Allstate use the term &#8220;Claims.&#8221;  Which is better?  I&#8217;d argue Geico made the wrong choice here.  By adding the word <em>center</em>, they&#8217;ve introduced a competing meaning &#8211; a &#8220;Claims Center&#8221; may or may not be a physical building.  Perhaps this link leads to a listing of where the Claims Centers are located, and is not a place to file or manage a claim online.</span></p>
<div id="attachment_1003" class="wp-caption alignleft" style="width: 634px"><img class="size-full wp-image-1003" title="insurance" src="http://www.solidstateux.com/wp-content/uploads/2009/10/insurance.png" alt="insurance" width="624" height="212" /><p class="wp-caption-text">Geico adds competing meanings by using two words (&quot;Claims Center&quot;) instead of one (Claims).</p></div>
<p style="text-align: center;"><span style="color: #000000;"><strong> </strong></span></p>
<div id="attachment_1037" class="wp-caption aligncenter" style="width: 579px"><strong><strong><img class="size-full wp-image-1037   " title="ibm" src="http://www.solidstateux.com/wp-content/uploads/2009/10/ibm.png" alt="Bad writing is bad writing.  This page menus is written in such bland corporate-speak that's it is almost impossible to decide where to click." width="569" height="205" /></strong></strong><p class="wp-caption-text">Bad writing is bad writing.  This page menu is written in such bland corporate-speak that it is almost impossible to decide where to click.</p></div>
<p><strong>2. Interfaces often divorce words from their context, especially in global navigation.<br />
</strong></p>
<p><span style="color: #000000;"><strong> </strong></span><span style="color: #000000;">Interface design is all about managing transitions between various contexts.  Persistent elements, such as global navigation, ride between multiple contexts.  Typically they are stripped down to their essence for this very reason.  For instance, in a book&#8217;s Table of Contents, you can contextualize each and every chapter name with a sub-heading, but a global nav on a website does not have that luxury.  With most websites, you don&#8217;t know where a user will enter into the experience, and you can&#8217;t assume anything was contextualized on a previous screen.     Navigation words therefore need to be mostly self-explanatory, since they can rely only on the context provided by the other global elements on the site &#8211; such as the name and tagline in the header.  When you remove a word from its context, it introduces <em>more</em> competing meanings.  The use of <em>branded</em> words in navigation elements is a very common usability problem.  Sports Illustrated (SI.com) has a disastrous top nav, with links like &#8220;fannation,&#8221; &#8220;swimsuit,&#8221;  &#8220;extra mustard,&#8221; and &#8220;maxpreps&#8221; that assume a lot of context which is just not present on most of the site&#8217;s pages (such as the home page.) Lumber Liquidators is almost aided by the fact that they have a very non-obvious name for a specialist in flooring.  They&#8217;re forced to add global context to their top nav (lest consumers mistake them for a discount lumberyard) but it&#8217;s one way to relieve pressure from the difficult game of finding the right words.</span></p>
<div id="attachment_1010" class="wp-caption aligncenter" style="width: 623px"><img class="size-full wp-image-1010 " title="si_com" src="http://www.solidstateux.com/wp-content/uploads/2009/10/si_com.png" alt="si_com" width="613" height="97" /><p class="wp-caption-text">SI.com assumes a lot of prior knowledge about their internal content branding on the part of users.  The result is a poor choice of nomenclature.</p></div>
<div id="attachment_1026" class="wp-caption aligncenter" style="width: 503px"><img class="size-full wp-image-1026 " title="ll" src="http://www.solidstateux.com/wp-content/uploads/2009/10/ll.png" alt="ll" width="493" height="121" /><p class="wp-caption-text">Notice how Lumber Liquidators takes an unusual step of adding context to a global nav with the label &quot;Flooring:&quot;</p></div>
<p style="text-align: center;">
<div id="attachment_1033" class="wp-caption aligncenter" style="width: 176px"><img class="size-full wp-image-1033  " title="starbucks" src="http://www.solidstateux.com/wp-content/uploads/2009/10/starbucks.png" alt="An oldie but a goodie: Starbucks global nav was once an ocean of competing meaning.  Since Improved." width="166" height="319" /><p class="wp-caption-text">An oldie but a goodie: Starbucks global nav was once an ocean of competing meaning.  Since Improved.</p></div>
<p><span style="color: #000000;"><strong>3. An interface inherits the context of its medium, not just its subject matter.</strong></span></p>
<p>Sometimes, competing meanings are generated by the very medium in which a word is being used.  I am consistently thrown for a loop when using my company&#8217;s travel and expense (T&amp;E) reporting system when given the choice of <em>inquiry</em> or <em>maintenance</em> of my reports.   These words have loads of competing meanings on a website.  Does inquiry mean just open and look at the reports, or does it imply that I am opening some sort of trouble-ticket with a customer service rep?  <em>Maintenance </em>implies seldom used utility features on a computer, like running a batch program to clean up a fragmented hard drive,  not a user making a routine change through a web form. Certainly <em>view or edit</em> would have been better choices. While not the lingo used in the world of corporate accounting circles, they are the words with the fewest competing meanings on a website.</p>
<div id="attachment_1015" class="wp-caption aligncenter" style="width: 427px"><img class="size-full wp-image-1015   " title="tne" src="http://www.solidstateux.com/wp-content/uploads/2009/10/tne.png" alt="tne" width="417" height="121" /><p class="wp-caption-text">I&#39;ve used this homegrown system a dozen times, yet always have to guess where to click here.</p></div>
<h4 style="font-size: 1em;">What are Anti-Patterns?</h4>
<p>(Definition taken from <a href="http://looksgoodworkswell.blogspot.com/search/label/antipatterns">Looks Good Works Well</a>)<em> Anti-patterns, also called pitfalls, are classes of commonly-reinvented bad solutions to problems. They are studied as a category so they can be avoided in the future, and so instances of them may be recognized when investigating non-working systems. The term originates in computer science, apparently inspired by the Gang of Four&#8217;s book Design Patterns, which displayed examples of high-quality programming methods.</em> - <a id="aptureLink_E4CkA4Xf8v" href="http://en.wikipedia.org/wiki/Anti-pattern">Wikipedia Anti-pattern</a></p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" />
]]></content:encoded>
			<wfw:commentRss>http://www.solidstateux.com/interaction-design/anti-pattern-competing-meanings-in-website-nomenclature/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
