<?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; usability</title>
	<atom:link href="http://www.solidstateux.com/tag/usability/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:  Dead Zones</title>
		<link>http://www.solidstateux.com/visual-design/anti-pattern-dead-zones/</link>
		<comments>http://www.solidstateux.com/visual-design/anti-pattern-dead-zones/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 22:09:54 +0000</pubDate>
		<dc:creator>Todd Toler</dc:creator>
				<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Visual Design]]></category>
		<category><![CDATA[antipatterns]]></category>
		<category><![CDATA[eye tracking]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.solidstateux.com/?p=644</guid>
		<description><![CDATA[Ad placements are, by definition, dead zones.   These are specific, predictable sections of a website’s screen real-estate that are subconsciously tuned out by the user as unrelated to the page’s main content and functionality.  But designers unintentionally create dead zones of their own all the time.    A classic and well understood example of a [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_727" class="wp-caption alignleft" style="width: 310px"><a href="http://www.solidstateux.com/wp-content/uploads/2009/09/old_new_IFC.png"><img class="size-medium wp-image-727 " title="old_new_IFC" src="http://www.solidstateux.com/wp-content/uploads/2009/09/old_new_IFC-300x168.png" alt="old_new_IFC" width="300" height="168" /></a><p class="wp-caption-text">The Independent Film Channel&#39;s home page used to be one big &quot;Dead Zone&quot; before they redesigned it.</p></div>
<p>Ad placements are, by definition, dead zones.   These are specific, predictable sections of a website’s screen real-estate that are subconsciously tuned out by the user as unrelated to the page’s main content and functionality.  But designers unintentionally create dead zones of their own all the time.    A classic and well understood example of a dead zone is &#8220;right-rail&#8221; blindness.  Content and features below an ad &#8211; such as in the right-hand column of a typical two or three column layout &#8211; are tuned out as ads on the assumption that everything from an ad down is also an ad.   According to <a href="http://www.catalystnyc.com/cofactors">Nick Gould</a>, CEO of the design and research firm Catalyst Group, the evidence of this phenomenon goes well beyond the anecdotal.   &#8220;There is no question that right-rail blindness is a phenomenon we&#8217;ve observed in both eye-tracking and usability testing.  This is of course mainly due to the ingrained expectation that ads live there.&#8221;   And it&#8217;s not just a matter of positioning elements in a layout.  The manner in which a page element itself  is designed can greatly amplify or lessen the dead zone effect, in the worse case scenario unintentionally deactivating important content areas and features from the user&#8217;s attention.   Often this comes from trying so hard to make an element &#8220;pop&#8221; visually, that the reverse effect occurs.   &#8220;The dead zone effect is obviously exacerbated if elements below ads are ad-like in their design,&#8221; Gould says.  &#8221;Furthermore, promotional elements that have standard ad dimensions and contain images are frequently mistaken for ads.&#8221;<span id="more-644"></span></p>
<div id="attachment_726" class="wp-caption alignright" style="width: 310px"><a href="http://www.solidstateux.com/wp-content/uploads/2009/09/heat_map.png"><img class="size-medium wp-image-726 " title="heat_map" src="http://www.solidstateux.com/wp-content/uploads/2009/09/heat_map-300x242.png" alt="Eye-tracking data shows that the &quot;right rail&quot; has little visual salience with users." width="300" height="242" /></a><p class="wp-caption-text">Eye-tracking data shows that the &quot;right rail&quot; has little visual salience with users.</p></div>
<p>There is strong evidence now that users have specific expectations about where to find the most relevant information on a web page <em>before having seen the page</em>.  In a recently published eye-tracking study observing  usage of a broad range of web sites for both page recognition and information foraging tasks, the right-rail blindness phenomenon was dramatically confirmed.  (see Bushcer, Cutrell, &amp; Morris 2009) &#8220;It is striking that the entire right side above the fold is neglected for both information foraging and page recognition tasks.&#8221;    The eye tracking data reveals that users are looking at the right rail, but the &#8220;fixation impact value&#8221; (a computation that correlates fixation length with the amount of visual information processed) approaches zero.  According to Gould, &#8220;This all relates to visual salience &#8211; which is more about an unconscious assessment of what&#8217;s relevant and what&#8217;s not that occurs pre-cognition.  A variety of design, placement, and relative size/shape issues can contribute to items on the page not being deemed salient.&#8221;</p>
<div id="attachment_723" class="wp-caption alignright" style="width: 310px"><img class="size-medium wp-image-723  " title="netflix" src="http://www.solidstateux.com/wp-content/uploads/2009/09/netflix-300x205.png" alt="Netflix consistently avoides &quot;Dead Zones&quot; with careful use of white space and &quot;Functional&quot; looking design cues." width="300" height="205" /><p class="wp-caption-text">Netflix consistently avoids &quot;Dead Zones&quot; with careful use of white space and &quot;Functional&quot; looking design cues.</p></div>
<p>As a predominantly qualitative researcher, these eye-tracking findings do not surprise me.  I&#8217;ve frequently observed that small differences in visual design and placement can have a dramatic effect on a user&#8217;s perception of whether they should pay attention- not to mention interact- with a page element.  Most of us who work on commercial websites have to balance a colorful, branded look while simultaneously creating a usable interface.   I&#8217;ve observed a few tricks over the years.  For instance, promotional elements that have an interactive &#8220;call to action&#8221;, such as a blank zip-code field in a registration opt-in promo, will outperform a straight image &amp; copy version of the same message.  Netflix.com are masters of working with a heavily branded design full of bold, contrasty elements, yet systematically avoiding the creation of dead zones with careful use of white space and  “functional looking” design cues.</p>
<div id="attachment_722" class="wp-caption alignright" style="width: 310px"><a href="http://www.solidstateux.com/wp-content/uploads/2009/09/Cliffs_cram_original.png"><img class="size-medium wp-image-722  " title="Cliffs_cram_original" src="http://www.solidstateux.com/wp-content/uploads/2009/09/Cliffs_cram_original-300x191.png" alt="Original Page Layout (with CramCast ad) on Cliffsnotes.com" width="300" height="191" /></a><p class="wp-caption-text">Original page layout (with CramCast ad) on cliffsnotes.com</p></div>
<p>I find myself conflicted (not to mention <em>confronted</em> by other stakeholders) with a desire to make something &#8220;pop&#8221; and the counter-intuitive, opposite notion that an integrated look is the key to discoverability.   We recently ran a multi-variate test on <a href="http://www.cliffsnotes.com">www.cliffsnotes.com</a> to test the hypothesis that elements with a more &#8220;integrated&#8221; versus &#8220;ad-like&#8221; design perform better in right rail placements.  It was my first dabbling with the free tool Google Website Optimizer (GWO) &#8211; which turned out to be one of those &#8220;Where have you been all my life?&#8221; moments.   In the Cliff&#8217;s Notes test, we took an existing internal promo on the site for a podcasting series called &#8220;CramCast,&#8221; which was designed as a standard 300 by 250 ad, and redesigned it in a style more consistent with the existing functional right-rail modules on the site.   We made no changes to the copy or the photo between variants.  The positioning on the page was exactly the same.  The only difference was the look and feel.  Then we ran both versions in a split-traffic test on the live site.</p>
<div id="attachment_721" class="wp-caption alignleft" style="width: 241px"><a href="http://www.solidstateux.com/wp-content/uploads/2009/09/variants.png"><img class="size-medium wp-image-721  " title="variants" src="http://www.solidstateux.com/wp-content/uploads/2009/09/variants-231x300.png" alt="The Integrated Look Outperformed the Original &quot;Ad-Like&quot; Look by a Narrow Margin" width="231" height="300" /></a><p class="wp-caption-text">The integrated look outperformed the original &quot;Ad-Like&quot; look by a narrow margin of 6%.</p></div>
<p>The integrated version did outperform the ad-like version, but not by a huge margin &#8211; only a 6% improvement.  (We got about 30 more clicks per 200,000 visitors with the Integrated look.)  It was not worth our time to redesign the creative material for that campaign, but certainly good counter-evidence the next time someone says something doesn&#8217;t <em>pop </em>enough.   What we couldn&#8217;t get at with GWO was whether the integrated look, since it replaced the traditional ad placement and cast less of a shadow on the user&#8217;s salient zone,  helped to activate the entire right rail.  This is the more interesting question.  After all, the worst dead zone problems are when multiple ad-like elements conspire to deactivate entire regions of a page &#8211; such as the old homepage design on IFC.com (pictured above.) In this design,  multiple ad-like features are interpreted sub-consciously by the user as one big ad area, and important content features (such as the programming schedule) are overlooked.  In our  next A/B test here, we&#8217;ll have to monitor the clicks outside our variants as well, perhaps with the advice of someone who is an expert with these tools &#8211; like <a href="http://www.kaushik.net/avinash/">Avinash Kaushik </a>or <a href="http://www.markohurst.com/">Marko Hurst</a>.    If anyone has done any research on this issue, or can point me towards soemthing else to share here &#8211; please comment on this post!</p>
<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" />
]]></content:encoded>
			<wfw:commentRss>http://www.solidstateux.com/visual-design/anti-pattern-dead-zones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Validity and Think-Aloud Protocols</title>
		<link>http://www.solidstateux.com/user-design-research/validity-and-think-aloud-protocols/</link>
		<comments>http://www.solidstateux.com/user-design-research/validity-and-think-aloud-protocols/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 17:46:32 +0000</pubDate>
		<dc:creator>Todd Toler</dc:creator>
				<category><![CDATA[User & Design Research]]></category>
		<category><![CDATA[cognitive science]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.solidstateux.com/?p=579</guid>
		<description><![CDATA[When usability research counts, and when it doesn't...]]></description>
			<content:encoded><![CDATA[<p><a rel="attachment wp-att-582" href="http://www.solidstateux.com/user-design-research/validity-and-think-aloud-protocols/attachment/protocol_analysis/"><img class="alignleft size-full wp-image-582" title="protocol_analysis" src="http://www.solidstateux.com/wp-content/uploads/2009/08/protocol_analysis.JPG" alt="protocol_analysis" width="185" height="270" /></a>First adapted from the work of experimental psychologists &#8211; most notably, Ericsson and Simon&#8217;s landmark 1993 work <a id="aptureLink_muCr8YhAHH" href="http://search.barnesandnoble.com/Protocol-Analysis-Revised-Edition/K-Anders-Ericsson/e/9780262550239">Protocol Analysis</a>, &#8211; think-aloud protocols are the de-facto standard for usability research in both the lab and field settings.  If you&#8217;ve seen or given a usability test before then you know what this is, it&#8217;s when the moderator tells the respondent to use a website or other application and then says &#8220;Hey, tell me what you are thinking.&#8221;   Jakob Nielsen and other HCI researchers were quick to trump the merits of this technique for uncovering usability problems with sample sizes as small as four people.  Why is the technique so effective?  Well, it&#8217;s validity stems largely from the fact that it&#8217;s a <em>direct measure</em> of what&#8217;s happening in a subject&#8217;s short-term memory.   Other examples of direct measures of human cognition are hard to find&#8230; in fact, the two others that are primarily used are response tests (e.g. reaction time indicators) and MRI brain scans!   So to have a direct measure that is cheap and easy to administer and also provides qualitative insights into the user experience is powerful indeed!  But if the interview is poorly moderated, or descends into a Q &amp; A session between moderator and respondent, then this validity flies out the window&#8230; so let&#8217;s look at the issue more closely.</p>
<p><span id="more-579"></span></p>
<input id="gwProxy" type="hidden" />
<p>If a subject is steadily verbalizing while performing a task (e.g. concurrent verbalization), they are assumed to be speaking from short term memory.  Dumas &amp; Redish (1993) conveniently summarize three levels of think-aloud protocols commonly referred to by HCI researchers:  Level 1 verbalizations:  where the emphasis is on pure thoughts with no or minimal explanations; Level 2 verbalizations:  same, but when the participant is dealing with non-verbal information, like shapes, which must be internally “coded” in order to be articulated verbally, and Level 3 verbalizations:  or “thinking plus explanations.”  The latter are also referred to as <em>retrospective reports</em>, because the respondent is recapping and opining about what they actually <em>did</em> earlier.  Dumas summarizes the distinction between Level 3 and the other levels as the stage where the researchers are “no longer getting a read out of short-term memory&#8230; rather it is the interpretation of the process they are using or the reasons they have selected a strategy.”  Retrospective reports are not useless to the user researcher, in fact they are necessary to clarify a respondent&#8217;s statements and actions, but they are far less valid.</p>
<p>This leads us to the question of active vs. inactive moderation.  In an inactive moderation scenario, the emphasis is on experimental control and creating a unified experience for all test subjects.  This is the old-school style, where the researchers stand behind the glass and the respondent sits in the room by themselves talking out loud like a crazy person.  Participants, faced with the unnatural task of constant verbalization, are typically “coached” on how to deliver a think-aloud protocol.  This often takes the form of a warm-up exercise where the participant and experimenter practice thinking aloud with non-related stimuli, preferably a simple game such as tic-tac-toe (in order to place emphasis on cognitive strategy.)  During the actual experiment, the moderator prompts only when the participant ceases to verbalize: “Please keep talking,&#8221; they say.  And that&#8217;s all they say!</p>
<p>In a high moderator intervention scenario, the experimenter employs <em>probing questions</em> to focus the participant’s attention on particular features or to elicit and clarify subjective explanations of their behavior.  Moderators are skilled in asking neutral, non-leading questions to minimize bias.  In addition, active listening techniques are employed to emulate the clinician’s <em>empathic stance</em>. This implies paraphrasing of a speaker’s comments to ensure them that they have been listened to, noted, and understood as well as other verbal and non-verbal forms of caring, non-judgmental acceptance.  Mike Kuniavsky, whose <a id="aptureLink_YeS3N8KBkx" href="http://www.amazon.com/gp/product/B0028085GQ">work</a> is mentioned frequently in these pages,  lays out the guidelines for “non-directed” interviewing:  <em>questions should be concentrated on immediate experience, nonjudgmental, focused on a single topic, open-ended, and non-binary (e.g. yes-no, true-false)</em>.</p>
<p>In a quick look at the literature, you&#8217;ll see that Taylor and Dionne (2000) suggest that probes are best deployed for collection and verification of data in retrospective reports, and that they have a detrimental impact on validity if used during concurrent think-aloud protocols.  Preece (1994) suggests that the role of the moderator on the participant is both interruptive and imposes additional cognitive load.  Nielsen (1993) is pragmatic on the subject, suggesting the moderator intervenes as little as possible, yet directing the flow and direction of the interview to maximize the number of usability issues found.   Nielsen is the spiritual father of the commercial usability field, so it&#8217;s no surprise that most usability is performed with this degree of pragmatism.  I think it was Jared Spool who once commented that you can only watch participants avoiding clicking on the red button so many times before you are compelled to intervene and ask <em>why</em>.   Plus, most clients of usability research do not share the academic&#8217;s interest in validity.  They want enough validity to feel good about the process and the results, but ultimately they want their specific questions answered for a reasonable amount of time and expense.  In Nielsen et. al.’s (2002) interpretation, <em>The human is a psychological being engaged in a psychological interaction, which cannot be reduced to that which is concurrently verbalized.</em></p>
<p>Some usability researchers, characterized by Whiteside, et. al. (1993), have also posited that observing a user’s behavior is not enough to understand what is happening in terms of higher order thinking and cognitive strategy.  If you set up <em>a priori</em> conditions then you are bounding yourself to learning only what falls within those conditions.  In this view, subjective experience is the most comprehensive criterion for understanding usability.  Concerns of generalizability are side-stepped: the goal is to obtain rich, experiential data.  Since specific questions are the only effective way to elicit and clarify mental models, the researcher must come to terms with at least a partially subjectivist stance. (Tamler, 2001)  This approach values reflexivity:  the subject is full participant in the study, leading the research into relevant areas for exploration as well giving the subject the ability to respond to the researchers interpretations. It is not a search for “truth,” per se, as a philosophical underpinning of this method of inquiry.  The assumption is that an expansion of perspectives leads to the exposure of more aspects of learning.</p>
<p>Here&#8217;s some References (I know, for a blog post, it&#8217;s over the top&#8230; but this stuff&#8217;s important!)</p>
<p>DUMAS, J.S. (2001) “Usability Testing Methods:  Think-Aloud Protocols,” in <em>Design by People For People:  Essays on Usability</em>, UPA,  pp 119-129</p>
<p>DUMAS, J.S. &amp; REDISH, J.C., (1993)  <em>A Practical Guide to Usability Testing</em>.  Norwood, NJ, Ablex Publishing Corp.</p>
<p>ERICSSON, K.A. &amp; SIMON, H.A. (1984, 1993) <em>Protocol analysis:  Verbal reports as data</em> (Rev. ed).  Cambridge, MA:  MIT Press</p>
<p>KUNIAVSKY, M. (2003)  <em>Observing the User Experience: A Practitioner’s Guide to User Research</em>,  San Francisco: Morgan Kaufmann Publishers, Inc.</p>
<p>NIELSEN, J., (1993) <em>Usability Engineering</em>.  Chestnut Hill, MA:  Academic Press, Inc.</p>
<p>NIELSEN, J., CLEMMENSEN, T., &amp; YSSING, C., (2002)  “Getting access to what goes on in people’s heads? – Reflections on the think-aloud technique”, paper presented to NordiCHI, Arhus, Denmark, October 19-23</p>
<p>PREECE, J. (1994), <em>Human-Computer Interaction</em>, Addison-Wesley, England</p>
<p>TAMLER, H. (2001) “How (Much) to Intervene in a Usability Testing Session,”  in <em>Design by People For People:  Essays on Usability</em>, UPA,  pp 165-171</p>
<p>WHITESIDE, J., BENNETT., J.L., &amp; HOLTZBLATT, K., (1988)  “Usability Engineering: Our Experience and Evolution,” in <em>Handbook of Human Computer Interaction</em>; edited by Helander, M.  New York, NY:  Elsevier Science Publishers</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" />
]]></content:encoded>
			<wfw:commentRss>http://www.solidstateux.com/user-design-research/validity-and-think-aloud-protocols/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
