<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>User Experience and Cognitive Engineering &#187; Jacob Nielsen</title>
	<atom:link href="http://francoisaubin.com/category/jacob-nielsen/feed/" rel="self" type="application/rss+xml" />
	<link>http://francoisaubin.com</link>
	<description>Ensure useful and usable solutions</description>
	<lastBuildDate>Thu, 05 Mar 2009 09:35:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='francoisaubin.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://www.gravatar.com/blavatar/254ce91f415c9e48124de6382e85b61b?s=96&#038;d=http://s2.wp.com/i/buttonw-com.png</url>
		<title>User Experience and Cognitive Engineering &#187; Jacob Nielsen</title>
		<link>http://francoisaubin.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://francoisaubin.com/osd.xml" title="User Experience and Cognitive Engineering" />
	<atom:link rel='hub' href='http://francoisaubin.com/?pushpress=hub'/>
		<item>
		<title>The Mechanics of Politics in IT: Part 1</title>
		<link>http://francoisaubin.com/2008/03/13/the-mechanics-of-politics-in-it-part-1/</link>
		<comments>http://francoisaubin.com/2008/03/13/the-mechanics-of-politics-in-it-part-1/#comments</comments>
		<pubDate>Fri, 14 Mar 2008 01:03:15 +0000</pubDate>
		<dc:creator>Francois Aubin</dc:creator>
				<category><![CDATA[Cognitive Egonomics]]></category>
		<category><![CDATA[Cognitive Engineering]]></category>
		<category><![CDATA[Don Norman]]></category>
		<category><![CDATA[Gallileo]]></category>
		<category><![CDATA[HCI]]></category>
		<category><![CDATA[Human Computer Interaction]]></category>
		<category><![CDATA[Human Factors]]></category>
		<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Jacob Nielsen]]></category>
		<category><![CDATA[User Experience]]></category>
		<category><![CDATA[cognitive group]]></category>
		<category><![CDATA[Design decision]]></category>
		<category><![CDATA[Heuristic Evaluation]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://francoisaubin.wordpress.com/?p=51</guid>
		<description><![CDATA[Last year, the government of Quebec asked Cognitive Group to do a heuristic evaluation (expert evaluating usability with a list of usability heuristics) and usability testing of their web portal. First, heuristic evaluation is not reliable because: Experts cannot assess terminology choice and evaluate task compatibility. Terminology and task compatibility account for the majority of [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=francoisaubin.com&blog=509005&post=51&subd=francoisaubin&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<p>Last year, the government of Quebec asked <a href="http://www.cognitivegroup.com/" title="cognitive">Cognitive Group</a> to do a <a href="http://www.useit.com/papers/heuristic/" title="ehuristic">heuristic evaluation</a> (expert evaluating usability with a list of usability heuristics) and usability testing of their web portal. First, heuristic evaluation is not reliable because:</p>
<ol>
<li><span id="more-51"></span>Experts cannot assess terminology choice and evaluate task compatibility. Terminology and task compatibility account for the majority of usability problems. To my knowledge, the only effective approach to evaluate terminology and task compatibility is through usability testing and field study.</li>
<li>The importance of heuristic (guidelines) depends of the context of use. For example, is the user going their once in a lifetime? Or is he a power user going there all the time on a mandatory basis.</li>
</ol>
<p>As I always do, I complied telling the client I will do heuristic evaluation with the help of informal usability testing instead of pure heuristic evaluation. That way, I don’t loose time explaining clients why they are wrong. I asked a few colleagues or friends to act as subjects for the informal usability testing who could be representative of the  audience.</p>
<p>Following the evaluation, I found the design of the portal was poor but I was not surprised, I have often seen bad design throughout my consulting practice. As usual, most usability problems were associated with confusing wording, task compatibility issues and funky use of interaction techniques. Up to now nothing unusual. I went on presenting my findings. But, while presenting, the client constantly interrupted me saying this or that; we cannot change it because it is a decision from the upper management. In some cases the minister himself got involved in the design choices.</p>
<p>Only later, after the formal usability testing where all users failed on all tasks, I got the client to admit the design was poor.  At that point they had no choice but accept my recommendations. This situation is painful because it places the management in a bad position. They were involved in poor design decisions.</p>
<p>More recently, a client in the airline industry told me he does not want to hear about usability because everybody has a different opinion. They often end up asking the CEO to decide. Again, I will have a very challenging consulting project because it might show the CEO made the wrong decision. Of course, I will try to find ways around it but nevertheless, it is not easy.</p>
<p>For many organizations, design (user interface design, user requirement, and functional specifications) is a painstaking process involving fierce battle between stakeholders. When they do not agree, they escalate to upper management for decision.</p>
<p>Escalating design decision that otherwise should be taken by the design team is a sure recipe for politics. If decisions are wrong, it will be uncovered sooner or later. Then, you will be in serious trouble.</p>
<p>How to prevent this?<br />
If you’re an executive, never get yourself involved in detailed design aspect. Keep yourself at the goal level and let your team design solutions.  If your team tries to get you involved in design deadlock, it is because they have not done their homework or they lack expertise. Your project manager might say there is a deadlock; he needs your help to move forward.  He will try to reassure you by saying he will fix the usability issues later. Don’t believe that, it will never happen and you will get stuck with a poor design for years. Stress it to your team you don’t care if the screens are blue, white or yellow as long as users were able to achieve their goals rapidly, without hesitation and errors. Get an external usability company to evaluate the design of your internal team so you will get an objective assessment of the design. Don’t worry about the susceptibility of your people, there is an easy way to manage that. If you don’t show leadership, you risk to be stuck with poor design for years if not forever.</p>
<p>Never forget, usability equals productivity. The first reason why we use technology is to improve productivity, so good design is extremely important.</p>
<p>If you are member of a project team, base your design decision on facts instead of opinion. How?  Learn usability best practices, build a prototype and test your design with users with usability testing. If you do not have this expertise, don’t hesitate, get and external consultant in usability.</p>
<br /><img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/francoisaubin.wordpress.com/51/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/francoisaubin.wordpress.com/51/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/francoisaubin.wordpress.com/51/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/francoisaubin.wordpress.com/51/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/francoisaubin.wordpress.com/51/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/francoisaubin.wordpress.com/51/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/francoisaubin.wordpress.com/51/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/francoisaubin.wordpress.com/51/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/francoisaubin.wordpress.com/51/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/francoisaubin.wordpress.com/51/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/francoisaubin.wordpress.com/51/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/francoisaubin.wordpress.com/51/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=francoisaubin.com&blog=509005&post=51&subd=francoisaubin&ref=&feed=1" />]]></content:encoded>
			<wfw:commentRss>http://francoisaubin.com/2008/03/13/the-mechanics-of-politics-in-it-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/2b273abf3fcddf7702dbcd2f5eaa8334?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Frank</media:title>
		</media:content>
	</item>
		<item>
		<title>10 things to do for the success of your web site &#8211; the practitioner view</title>
		<link>http://francoisaubin.com/2007/12/01/10-things-to-do-for-the-success-of-your-web-site-the-practitioner-view/</link>
		<comments>http://francoisaubin.com/2007/12/01/10-things-to-do-for-the-success-of-your-web-site-the-practitioner-view/#comments</comments>
		<pubDate>Sat, 01 Dec 2007 04:42:16 +0000</pubDate>
		<dc:creator>Francois Aubin</dc:creator>
				<category><![CDATA[Cognitive Egonomics]]></category>
		<category><![CDATA[Cognitive Engineering]]></category>
		<category><![CDATA[HCI]]></category>
		<category><![CDATA[Human Computer Interaction]]></category>
		<category><![CDATA[Human Factors]]></category>
		<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Jacob Nielsen]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Thomas Tullis]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[User Experience]]></category>
		<category><![CDATA[Web usability]]></category>
		<category><![CDATA[cognitive group]]></category>
		<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://francoisaubin.com/2007/12/01/10-things-to-do-for-the-success-of-your-web-site-the-practitioner-view/</guid>
		<description><![CDATA[1. Know what is important. 1. Bring users to your site, 2. Ensure usefulness and usability, 3. Maximize trust. You will make much more money trying to bring users to your site and ensuring good usability than trying to have beautiful flash and look. Most users care only about finding rapidly what they are looking [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=francoisaubin.com&blog=509005&post=38&subd=francoisaubin&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<p><strong>1. Know what is important.</strong> <strong>1.</strong> Bring users to your site, <strong>2.</strong> Ensure usefulness and usability, <strong>3.</strong> Maximize trust. You will make much more money trying to bring users to your site and ensuring good usability than trying to have beautiful flash and look. Most users care only about finding rapidly what they are looking for and achieving their goals. They don’t care <span id="more-38"></span>about color and visual appearance. When they find what they are looking for, they usually don’t notice the look. <a href="http://www.amazon.com" title="amazon">Amazon</a>, <a href="http://www.google.com" title="google">Google</a>, <a href="http://www.yahoo.com" title="yahoo">Yahoo</a>, <a href="http://www.ebay.com" title="ebay">Ebay</a> and <a href="http://www.craigslist.org/about/sites.html" title="cragiglist">Craigslist</a> are very successful but they are not beautiful, they are effective.</p>
<p><strong>2. Avoid having wrong design goals.</strong> For example minimizing the number of clicks. To ensure having the proper design goals, know the users, their goals and the context of use. If users are going to your site once in a while on a non-mandatory basis (online banking, news, shopping…), you have to treat them as a novice. They have to understand instantly how to use the site. In this context, it is preferable having a few more clicks and pages with less information.  On the other hand, for power user, speed is more important. In this context, less actions, pages and clicks are more important.</p>
<p><strong>3. Do few things and do them well. </strong>For example for an e-commerce site, ease of finding the product, having the right information on the product and trust are the key success factors. For a search engine, ease of entering queries, speed and  pertinence are the key success factors. Don’t spread your energy on other features unless you master your key success factors better than any others.</p>
<p><strong>4. Design for user limited attention.</strong> On the web, many users have little patience and do many things at the same time (they might go on your site while at work). Within 10 seconds, they will abandon if they don’t find what they are looking for.  Since the reading speed is about 200 words per minute, you can provide a maximum of 35 words to read before a user abandons.  So minimize the quantity of text. Contrary to TV where the full screen is in use, on a computer, only a small portion of the screen is viewed simultaneously (roughly 6 to 7 cm diameter). This is due to the useful field of view, which corresponds to the subtended angle of the <a href="http://francoisaubin.com/2006/12/01/making-and-add-effective-why-useful-field-of-view-ufov-is-so-important/" title="Foveal vision">fovea vision</a>. Information must be grouped within this diameter. That’s why banners are so ineffective. For most page layout you can afford about 4 to 5 groups.  Avoid long lists of items, users read only the first few items at the top of the list. Organize according to the natural eye path. Remember users start from the top left corner, go to the center and if they don’t find what they are looking for, then they try to go to the left expecting a menu. For this reason, avoid menus on the right. The bottom right is the worst real estate of a page.</p>
<p><a href="http://francoisaubin.files.wordpress.com/2007/12/eyepatern.jpg" title="Eye patern on a web page"><img src="http://francoisaubin.files.wordpress.com/2007/12/eyepatern.thumbnail.jpg?w=500" alt="Eye patern on a web page" /></a></p>
<p>This sketch show the typical eye pattern on a web page.<strong> </strong></p>
<p><strong>5. Avoid relying on branding.</strong> Users do not remember seeing your ads, brochure and other corporate information. Keep your brand simple and name your entire product line in relation to a user goal. If you already have a brand for a product, provide a prompt matching the user goal. This also help SEO (Search Engine Optimization). For the same reason, you don’t need to be that consistent between corporate brochure and web site.</p>
<p><strong>6. Users don’t read, they scan. </strong>Users will scan text and when they find something that is likely to meet their goals, they click on it. You better to expect that users won’t read your text.  A good approach is to provide just a list of hyperlinks with a large font. You can also provide a small description with a maximum of 15 words with smaller lighter font under the hyperlink. This technique is ideal for a newsletter. Users will scan the list, if they are interested, they will click on it and read the description under it.</p>
<p><strong>7. Ensure users understand your text and graphics.</strong> At least 50 % of the usability problems are related to the wrong choice terminology. Users get easily confused between concepts such as events and news, schedule and time table…. Minimize the number of concepts. Don’t worry, users mix apples and oranges. Test and test again your site with real users to find the right terminology.</p>
<p><strong>8. Don’t reinvent the wheel. </strong>Use basic web controls. You don’t need to create complex navigation structure. A simple menu and the browser’s back and forward button are Ok for most of the cases. Once users have a successful behavior, they continue to us it for other goals. For example, if they find something through the menu, they will try this method again for another goal. Limit your design to familiar controls. Use straight hyperlinks to select a page. You will make more money with blue underlined hyperlinks because the users’ reaction time is about 30 ms less.</p>
<p><strong>9. Use readable font.</strong> If users find the information and can’t read it, it’s zero. Why using small fonts? If your fonts are too small, only younger users will be able to read it. With the right size, everybody will be able to read it. Fonts must have a size equal to <a href="http://francoisaubin.com/2007/11/18/on-the-size-of-font/" title="eye size">1/200th the distance</a> of reading for proper readability. On a computer screen, fonts must be at least 3 mm. For example MS Sans Serif or Verdana at a minimum of 11 points are Ok. Font adjustment controls don’t work because most users that would need them never use them. Those having serious reading problems already have special adjustments on their browser.</p>
<p><strong>10. Be permissive to errors.</strong> Users make errors. The best way to manage errors is to allow them. For example, be permissive to various date formats. On the other hand, if users make errors, ensure proper detection, recovery and simple messages. Messages must have two items:  the status and the corrective action.</p>
<p>For more information , you should check the <a href="http://www.useit.com/alertbox/20031222.html" title="Top 10 web Design Mistakes">Top 10 Web Design Mistakes of 2003</a> from <a href="http://www.useit.com/jakob/" title="Jacob Nielsen">Jacob Nielsen</a></p>
<br /><img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/francoisaubin.wordpress.com/38/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/francoisaubin.wordpress.com/38/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/francoisaubin.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/francoisaubin.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/francoisaubin.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/francoisaubin.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/francoisaubin.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/francoisaubin.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/francoisaubin.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/francoisaubin.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/francoisaubin.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/francoisaubin.wordpress.com/38/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=francoisaubin.com&blog=509005&post=38&subd=francoisaubin&ref=&feed=1" />]]></content:encoded>
			<wfw:commentRss>http://francoisaubin.com/2007/12/01/10-things-to-do-for-the-success-of-your-web-site-the-practitioner-view/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/2b273abf3fcddf7702dbcd2f5eaa8334?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Frank</media:title>
		</media:content>

		<media:content url="http://francoisaubin.files.wordpress.com/2007/12/eyepatern.thumbnail.jpg" medium="image">
			<media:title type="html">Eye patern on a web page</media:title>
		</media:content>
	</item>
	</channel>
</rss>