<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Usability heuristics 1</title>
	<link>http://www.multimedia-engineer.nl/2006/02/14/usability-heuristics-1/</link>
	<description>Webdevelopment</description>
	<pubDate>Thu, 29 Jul 2010 19:31:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Ruben's usability</title>
		<link>http://www.multimedia-engineer.nl/2006/02/14/usability-heuristics-1/#comment-10</link>
		<pubDate>Sun, 19 Feb 2006 11:53:46 +0000</pubDate>
		<guid>http://www.multimedia-engineer.nl/2006/02/14/usability-heuristics-1/#comment-10</guid>
					<description>What I also usually add under &quot;visibility of system status&quot;, is navigation status. Indicate where a user is at the moment, show visited and active links etc.

And consitency and real world matching should always come together. Use the language of your (potential) users/ customers. Don't let a horny marketing department invent cute names for stuff. Just check the search engine volume, see where (on which keywords) your conversion lies and use those terms.

Anyway, I think Nielsen's usability heuristics are nice, but a more comprehensive low-level list is worth more. His list is too hard to make a checklist out of, there are tons of other nice lists that are more concrete. Moreover, I think he created the list for his book &quot;Usability engineering&quot;, which isn't about websites, but more about systems in general, while most people think of websites when they want to learn about usability.

PS: Why write in English? The Dutch community needs more quality content like this. The stuff you write here seems quite dupe-like, in English.</description>
		<content:encoded><![CDATA[<p>What I also usually add under &#8220;visibility of system status&#8221;, is navigation status. Indicate where a user is at the moment, show visited and active links etc.</p>
<p>And consitency and real world matching should always come together. Use the language of your (potential) users/ customers. Don&#8217;t let a horny marketing department invent cute names for stuff. Just check the search engine volume, see where (on which keywords) your conversion lies and use those terms.</p>
<p>Anyway, I think Nielsen&#8217;s usability heuristics are nice, but a more comprehensive low-level list is worth more. His list is too hard to make a checklist out of, there are tons of other nice lists that are more concrete. Moreover, I think he created the list for his book &#8220;Usability engineering&#8221;, which isn&#8217;t about websites, but more about systems in general, while most people think of websites when they want to learn about usability.</p>
<p>PS: Why write in English? The Dutch community needs more quality content like this. The stuff you write here seems quite dupe-like, in English.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
