<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.2" -->
<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/"
	>

<channel>
	<title>che Usability?</title>
	<link>http://www.cheusability.com</link>
	<description>Practical usability advice — without the stronzata!</description>
	<pubDate>Fri, 16 May 2008 18:49:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
	<language>en</language>
			<item>
		<title>Homepage Usability — Gone in 30 Seconds</title>
		<link>http://www.cheusability.com/homepage-usability-%e2%80%94-gone-in-30-seconds/</link>
		<comments>http://www.cheusability.com/homepage-usability-%e2%80%94-gone-in-30-seconds/#comments</comments>
		<pubDate>Fri, 16 May 2008 18:49:22 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[Usability]]></category>

		<category><![CDATA[Usability design]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[GUI]]></category>

		<category><![CDATA[look and feel]]></category>

		<category><![CDATA[web usability]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/homepage-usability-%e2%80%94-gone-in-30-seconds/</guid>
		<description><![CDATA[Way back in 2000, Nicolas Cage starred in a movie called Gone in Sixty Seconds. In the movie Cage and his crew needed to steal 50 exotic cars in just one night.
Think of web surfers as Nicolas Cage and his crew, breezing through homepages looking for the exotic cars to steal — except instead of [...]]]></description>
			<content:encoded><![CDATA[<p>Way back in 2000, <a href="http://en.wikipedia.org/wiki/Nicolas_cage">Nicolas Cage</a> starred in a movie called <a href="http://www.imdb.com/title/tt0187078/">Gone in Sixty Seconds</a>. In the movie Cage and his crew needed to steal 50 exotic cars in just one night.</p>
<p>Think of web surfers as Nicolas Cage and his crew, breezing through homepages looking for the exotic cars to steal — except instead of 60 seconds your homepage only has 30 seconds to catch their interest.</p>
<p>It’s estimated that users with low web experience spend just 35 seconds on a homepage, while savvy web users spend as little as 25 seconds.</p>
<p>With only 30 seconds to capture a visitor’s attention, your messages need to be lean and to the point. You can’t afford to take up space with long, puffed up paragraphs. Realistically, you have to make your point with approximately 20 words. As users spend their time trying to figure out where to go next, they’re certainly not reading your content word-for-word.</p>
<p>The four most important things your homepage must communicate to your visitors are:</p>
<ul>
<li>What site is the person on</li>
<li>What benefits your site offers</li>
<li>Information about your company, latest products, or developments</li>
<li>How to get to the most relevant sections.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/homepage-usability-%e2%80%94-gone-in-30-seconds/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Book review: Information Architecture for the World Wide Web, Third Edition</title>
		<link>http://www.cheusability.com/book-review-information-architecture-for-the-world-wide-web-third-edition/</link>
		<comments>http://www.cheusability.com/book-review-information-architecture-for-the-world-wide-web-third-edition/#comments</comments>
		<pubDate>Wed, 12 Mar 2008 14:33:33 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[Book reviews]]></category>

		<category><![CDATA[Usability design]]></category>

		<category><![CDATA[book review]]></category>

		<category><![CDATA[IA]]></category>

		<category><![CDATA[information architecture]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/book-review-information-architecture-for-the-world-wide-web-third-edition/</guid>
		<description><![CDATA[Peter Morville and Louis Rosenfeld are back with an updated Third Edition of Information Architecture for the World Wide Web.
Keeping most of the organization of the Second Edition, the Third Edition addresses emerging web technologies and features such as:

Tagging 
Folksonomies
Social Classification
Guided Navigation.

]]></description>
			<content:encoded><![CDATA[<p>Peter Morville and Louis Rosenfeld are back with an updated Third Edition of <em>Information Architecture for the World Wide Web.</em></p>
<p>Keeping most of the organization of the Second Edition, the Third Edition addresses emerging web technologies and features such as:</p>
<ul>
<li>Tagging </li>
<li>Folksonomies</li>
<li>Social Classification</li>
<li>Guided Navigation.</li>
</ul>
<p> <a href="http://www.cheusability.com/book-review-information-architecture-for-the-world-wide-web-third-edition/#more-29" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/book-review-information-architecture-for-the-world-wide-web-third-edition/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Book review: Prioritizing Web Usability</title>
		<link>http://www.cheusability.com/book-review-prioritizing-web-usability/</link>
		<comments>http://www.cheusability.com/book-review-prioritizing-web-usability/#comments</comments>
		<pubDate>Fri, 29 Feb 2008 14:28:43 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[Book reviews]]></category>

		<category><![CDATA[Usability]]></category>

		<category><![CDATA[GUI]]></category>

		<category><![CDATA[UI]]></category>

		<category><![CDATA[User testing]]></category>

		<category><![CDATA[web usability design]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/book-review-prioritizing-web-usability/</guid>
		<description><![CDATA[Teaming up with Hoa Loranger, a user experience specialist with the Nielsen Norman Group, Jakob Nielsen has come out with Prioritizing Web Usability, his follow-up to his 2000 book, Designing Web Usability: The Practice of Simplicity.
Using research gathered from general usability testing of 716 web sites and 2,163 users around the world, as well as more targeted testing [...]]]></description>
			<content:encoded><![CDATA[<p>Teaming up with Hoa Loranger, a user experience specialist with the <a href="http://www.nngroup.com/">Nielsen Norman Group</a>, <a href="http://www.useit.com/jakob/index.html">Jakob Nielsen</a> has come out with <em>Prioritizing Web Usability,</em> his follow-up to his 2000 book, <a href="http://www.amazon.com/Designing-Usability-VOICES-Jakob-Nielsen/dp/156205810X/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1203691552&amp;sr=1-1">Designing Web Usability: The Practice of Simplicity.</a></p>
<p>Using research gathered from general usability testing of 716 web sites and 2,163 users around the world, as well as more targeted testing of 69 users for purposes of creating the book itself, Nielsen condenses thousands of usability findings into a small number of key principles by emphasizing the ones that will have the most impact on your web site.</p>
<p>Some good points of discussion in the book include searching, prioritizing your usability problems, navigation, and writing for the web.</p>
<p><strong>Must read chapter<br />
</strong>If you don’t have time to read the book cover-to-cover, reading Chapter 3, “Revisiting Earlier Web Findings” is a must.</p>
<p>In this chapter, Nielsen lists 34 of the most prevalent usability issues and guidelines for addressing them. In addition each issue has a skull rating, indicating how important the problem continues to be.</p>
<p>Some issues that continue to cause web usability issues are:</p>
<ul>
<li>Links that don’t change colour when visited</li>
<li>Breaking the back button</li>
<li>Opening new browser windows.</li>
</ul>
<p>This chapter is a great source for evaluating how well your site is doing in regards to its usability.</p>
<p><strong>Who should read this book?</strong><br />
<em>Prioritizing Web Usability</em> is a must-read for both novice and seasoned web designers that develop news sites, e-commerce sites, corporate sites, non-profit sites, and government sites.</p>
<p><a href="http://www.amazon.com/Prioritizing-Usability-VOICES-Jakob-Nielsen/dp/0321350316/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1203694508&amp;sr=8-1">Prioritizing Web Usability</a><br />
Authors: Jakob Nielsen, Hoa Loranger<br />
ISBN: 0-321-35031-6<br />
 </p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/book-review-prioritizing-web-usability/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Videos – are your users actually watching them?</title>
		<link>http://www.cheusability.com/videos-are-your-users-actually-watching-them/</link>
		<comments>http://www.cheusability.com/videos-are-your-users-actually-watching-them/#comments</comments>
		<pubDate>Tue, 26 Feb 2008 14:27:23 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[Usability]]></category>

		<category><![CDATA[Usability design]]></category>

		<category><![CDATA[video usability]]></category>

		<category><![CDATA[web usability guidelines]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/2008/02/26/videos-%e2%80%93-are-your-users-actually-watching-them/</guid>
		<description><![CDATA[Video killed the radio star; is it also killing your web site’s usability?
Maybe that question is a bit dramatic, but research shows that users view well-crafted short videos that take advantage of the medium’s dynamic nature — and by short I mean between 30 and 60 seconds.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.useit.com/alertbox/video.html"></a>Video killed the radio star; is it also killing your web site’s usability?</p>
<p>Maybe that question is a bit dramatic, but research shows that users view well-crafted short videos that take advantage of the medium’s dynamic nature — and by short I mean between 30 and 60 seconds.</p>
<p> <a href="http://www.cheusability.com/videos-are-your-users-actually-watching-them/#more-27" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/videos-are-your-users-actually-watching-them/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Morae 2.0 Review</title>
		<link>http://www.cheusability.com/morae-20-review/</link>
		<comments>http://www.cheusability.com/morae-20-review/#comments</comments>
		<pubDate>Wed, 06 Feb 2008 20:33:34 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[User testing]]></category>

		<category><![CDATA[usability software]]></category>

		<category><![CDATA[web usability testing]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/2008/02/06/morae-20-review/</guid>
		<description><![CDATA[Got my hands on TechSmith’s Morae 2.0 about a month ago and I’m digging it.
Morae Bundle is a usability software kit that enables you to record tests, observe users, and create presentations for your usability testing.
]]></description>
			<content:encoded><![CDATA[<p>Got my hands on TechSmith’s <a href="http://www.techsmith.com/morae.asp">Morae 2.0</a> about a month ago and I’m digging it.</p>
<p>Morae Bundle is a usability software kit that enables you to record tests, observe users, and create presentations for your usability testing.</p>
<p> <a href="http://www.cheusability.com/morae-20-review/#more-26" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/morae-20-review/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Give users what they don’t know they need</title>
		<link>http://www.cheusability.com/give-users-what-they-dont-know-they-need/</link>
		<comments>http://www.cheusability.com/give-users-what-they-dont-know-they-need/#comments</comments>
		<pubDate>Wed, 23 Jan 2008 16:31:24 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[Usability design]]></category>

		<category><![CDATA[user centred design]]></category>

		<category><![CDATA[web usability design]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/2008/01/23/give-users-what-they-don%e2%80%99t-know-they-need/</guid>
		<description><![CDATA[I was watching an afternoon talk show the other day. OK, it was Oprah, but I was really sick and couldn’t change the channel.
She had a dude from 3M showing off their new Flag Highlighter and Pen. (In your best Seinfeld voice say, “It’s great because it’s a highlighter that holds flags!”)
Why am I talking [...]]]></description>
			<content:encoded><![CDATA[<p>I was watching an afternoon talk show the other day. OK, it was Oprah, but I was really sick and couldn’t change the channel.</p>
<p>She had a dude from 3M showing off their new <a href="http://www.3m.com/us/office/postit/products/prod_ft_fph.html">Flag Highlighter and Pen</a>. (In your best <em>Seinfeld</em> voice say, “It’s great because it’s a highlighter that holds flags!”)</p>
<p>Why am I talking about this?</p>
<p>Glad you asked. Oprah asks the 3M guy how they came up with the product. “Did someone tell you that they wanted this?”</p>
<p>The 3M guy responds, “No, we watched people use our products and thought this would be a great invention.”</p>
<p>3M was using a user-centered design process to create a product that people did not know they needed yet. Specifically, they conducted a task analysis.</p>
<p> <a href="http://www.cheusability.com/give-users-what-they-dont-know-they-need/#more-25" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/give-users-what-they-dont-know-they-need/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Leave me hanging, eh?</title>
		<link>http://www.cheusability.com/leave-me-hanging-eh/</link>
		<comments>http://www.cheusability.com/leave-me-hanging-eh/#comments</comments>
		<pubDate>Fri, 11 Jan 2008 20:24:51 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[Usability]]></category>

		<category><![CDATA[Usability design]]></category>

		<category><![CDATA[information architecture]]></category>

		<category><![CDATA[web usability]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/2008/01/11/leave-me-hanging-eh/</guid>
		<description><![CDATA[No, I’m not going to talk about the famous Bob and Doug McKenzie skit on SCTV, but the “Leave me hanging, eh?” comment was stuck in my head in a recent round of user testing I just completed.
I was testing a page of products and services that users found easy to use. They became frustrated, however, when [...]]]></description>
			<content:encoded><![CDATA[<p>No, I’m not going to talk about the famous <a href="http://en.wikipedia.org/wiki/Bob_and_Doug_McKenzie">Bob and Doug McKenzie</a> skit on <a href="http://en.wikipedia.org/wiki/Second_City_Television">SCTV</a>, but the “Leave me hanging, eh?” comment was stuck in my head in a recent round of user testing I just completed.</p>
<p>I was testing a page of products and services that users found easy to use. They became frustrated, however, when they clicked into the documents that explained these products and services.</p>
<p> <a href="http://www.cheusability.com/leave-me-hanging-eh/#more-24" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/leave-me-hanging-eh/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Ten Facilitating Tips</title>
		<link>http://www.cheusability.com/ten-facilitating-tips/</link>
		<comments>http://www.cheusability.com/ten-facilitating-tips/#comments</comments>
		<pubDate>Tue, 08 Jan 2008 18:30:55 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[User testing]]></category>

		<category><![CDATA[usability testing]]></category>

		<category><![CDATA[web user testing]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/2008/01/08/ten-facilitating-tips/</guid>
		<description><![CDATA[Facilitating a user test is a balancing act between letting a participant fumble around until frustration sets in and prompting so many times that you help the user easily complete a task.
 
If you want to successfully run a user evaluation, here’s what to do when:
1. The participant asks questions during the task.
If the user is asking [...]]]></description>
			<content:encoded><![CDATA[<p>Facilitating a user test is a balancing act between letting a participant fumble around until frustration sets in and prompting so many times that you help the user easily complete a task.<br />
 <br />
If you want to successfully run a user evaluation, here’s what to do when:</p>
<p><strong>1. The participant asks questions during the task.</strong><br />
If the user is asking how to accomplish the task, reply “I’m not really sure. What do you think you should do?”</p>
<p>If the question is about the task itself — explain the task further.</p>
<p><strong>2. The participant asks if they completed the task correctly.</strong><br />
Reply with “What do you think?” Remind the user that the purpose of the evaluation is not to judge what is right or wrong but rather to learn how participants use the web site.</p>
<p><strong>3. The participant is stuck on a task.<br />
</strong>Assure the participant that getting stuck is OK, as it highlights problems with the design.</p>
<p><strong>4. The participant thinks they have done the “wrong” thing.</strong><br />
Assure the user that he or she cannot do anything “wrong” in a user evaluation. Remind the user that the goal is to learn how participants use the web site.</p>
<p><strong>5. The participant completes the task correctly.</strong><br />
Simply ask the participant to move on to the next task. Do not say “Good,” “That’s correct,” or “Excellent,” as you are not testing the user but rather the web site.</p>
<p><strong>6. The participant expresses frustration.</strong><br />
Find out what is causing the frustration — “What is frustrating you at this point in the task?”</p>
<p><strong>7. The participant looks confused.</strong><br />
Again, explore the root of the confusion — “I can see that you are confused. What part of the task is causing the confusion?”</p>
<p><strong>8. The participant does the wrong thing but thinks he or she completed the task correctly.</strong><br />
Simply continue with the test.</p>
<p><strong>9. The participant gives you a design recommendation.</strong><br />
Acknowledge the recommendation and refocus the user’s attention on completing the task.</p>
<p><strong>10. The participant gives up.</strong><br />
Assure the user that it is OK to give up, as he or she is helping find design flaws in the web site’s design.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/ten-facilitating-tips/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Problem testers</title>
		<link>http://www.cheusability.com/problem-testers/</link>
		<comments>http://www.cheusability.com/problem-testers/#comments</comments>
		<pubDate>Wed, 12 Dec 2007 20:15:04 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[User testing]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/2007/12/12/problem-testers/</guid>
		<description><![CDATA[I just completed a round of user testing today and had some real characters show up for the evaluations.
Being out of your natural work environment while two people observe you is not really an easy position to be in. As a result, people react in different ways.
Here are the three types of user testers I [...]]]></description>
			<content:encoded><![CDATA[<p>I just completed a round of user testing today and had some real characters show up for the evaluations.</p>
<p>Being out of your natural work environment while two people observe you is not really an easy position to be in. As a result, people react in different ways.</p>
<p>Here are the three types of user testers I came across this week:</p>
<p><strong>The Designer</strong><br />
Instead of just using the page as they would on their own, “designers” want to redesign the interface. They usually have comments like:</p>
<ul>
<li>“It’s ok for me, but people with accessibility issues might have trouble”</li>
<li>“It would be better if you move the button over here”</li>
<li>“I think people with colour blindness might have problems with the colours.”</li>
</ul>
<p>These suggestions might be useful if the participants were actual designers, but most times they’re not, so their suggestions probably will not help you.</p>
<p>To get “designers” back on track, acknowledge their ideas, but remind them that the purpose of the session is to understand how they are able to complete certain tasks.</p>
<p><strong>The Thinker<br />
</strong>Even after having the <a href="http://www.cheusability.com/2007/10/26/talk-talk-%e2%80%93-not-just-a-band-from-the-80s/">“think out loud”</a> process explained to them, “thinkers” explore the page without so much as a grunt. These people drive your note-taker crazy, as there are limited notes to take.</p>
<p>Get “thinkers” talking by asking probing questions such as:</p>
<ul>
<li>“What are you looking for?”</li>
<li>“What are you thinking?”</li>
<li>“Can you talk me through what you just did?”</li>
</ul>
<p><strong>Mr/Ms. Negative<br />
</strong>For these people, there is not one good element on the page. Even a web standard is up for ridicule.</p>
<p>Allow negative types to express themselves, but try to direct them to some positive features by asking “Is there anything about the page that you like?” </p>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/problem-testers/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Use the right word</title>
		<link>http://www.cheusability.com/use-the-right-word/</link>
		<comments>http://www.cheusability.com/use-the-right-word/#comments</comments>
		<pubDate>Thu, 06 Dec 2007 00:20:18 +0000</pubDate>
		<dc:creator>che usability</dc:creator>
		
		<category><![CDATA[Usability]]></category>

		<category><![CDATA[writing for the web]]></category>

		<guid isPermaLink="false">http://www.cheusability.com/2007/12/05/use-the-right-word/</guid>
		<description><![CDATA[Recently, I had a client who took the W3C’s advice about not using “Click here” for links too literally.
The client’s user base is not very web-savvy. To compensate, my client decided to write instructions for a new online form. The form has a variety of features such as:

check boxes
radio buttons
drop down menus, and
action buttons (e.g. [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, I had a client who took the <a href="http://www.w3.org/QA/Tips/noClickHere">W3C’s advice about not using “Click here” for links</a> too literally.</p>
<p>The client’s user base is not very web-savvy. To compensate, my client decided to write instructions for a new online form. The form has a variety of features such as:</p>
<ul>
<li>check boxes</li>
<li>radio buttons</li>
<li>drop down menus, and</li>
<li>action buttons (e.g. Submit and OK).</li>
</ul>
<p>Determined not to use the word “click,” my client used the word “select” throughout the instructions. I know! Oh, the humanity!</p>
<p>“Select” is an acceptable word, but it is <a href="http://www.thebookexperts.com/2007/11/19/of-mandolins-and-violins-choosing-exactly-the-right-word/">not the right one</a> for every situation. Remember: users spend 95 percent of their time on other sites. Most other sites instruct users to “click” on a button, not to “select” a button. Users understand “selecting” a check box or an item from a drop down menu, but they will be confused by “selecting” a button.</p>
<p>More importantly, the W3C advice on not using “Click here” refers to links found in chunks of text. Since users scan information on your site, writing “Click here” for all your links does not help them decide where to go next. However, W3C did not intend for site owners to rid the word “click” from their vocabularies.</p>
<p>Learn two things from this short story:</p>
<ol>
<li>Do not take “advice from the experts” to your peril</li>
<li>Use the right words for both your content and your link names, as doing so will help your users get the most out of your site.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.cheusability.com/use-the-right-word/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
