<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: KMail icon test #2 &#8211; have you participated?</title>
	<atom:link href="http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/</link>
	<description>Professional OpenSource Usability</description>
	<lastBuildDate>Thu, 02 Feb 2012 17:59:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Björn Balazs</title>
		<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/comment-page-1/#comment-1807</link>
		<dc:creator>Björn Balazs</dc:creator>
		<pubDate>Mon, 11 Jan 2010 10:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.opensource-usability-labs.com/?p=291#comment-1807</guid>
		<description>@next_ghost: Sorry, but no: not this test should be different - there should additionally be different tests. This test has one big stregth you cannot achieve in a setting you propose: it can meassure the time participants need to select an icon. This is not possible in an multiple &quot;best fit&quot; test. We have tested these options and they lead to worse results than the current testing methodology.</description>
		<content:encoded><![CDATA[<p>@next_ghost: Sorry, but no: not this test should be different &#8211; there should additionally be different tests. This test has one big stregth you cannot achieve in a setting you propose: it can meassure the time participants need to select an icon. This is not possible in an multiple &#8220;best fit&#8221; test. We have tested these options and they lead to worse results than the current testing methodology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: next_ghost</title>
		<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/comment-page-1/#comment-1741</link>
		<dc:creator>next_ghost</dc:creator>
		<pubDate>Sat, 09 Jan 2010 15:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.opensource-usability-labs.com/?p=291#comment-1741</guid>
		<description>I agree that the icon test should be a little different.
1) You should be able to select multiple &quot;best fit&quot; icons so that it&#039;s obvious which ones are easy to confuse with others for a particular user (not just statistically to a group of users).
2) Another part of the test should show an icon and a list of possible task descriptions this icon might represent (multiple choice again) so that it&#039;s obvious which icons don&#039;t have a clear meaning.</description>
		<content:encoded><![CDATA[<p>I agree that the icon test should be a little different.<br />
1) You should be able to select multiple &#8220;best fit&#8221; icons so that it&#8217;s obvious which ones are easy to confuse with others for a particular user (not just statistically to a group of users).<br />
2) Another part of the test should show an icon and a list of possible task descriptions this icon might represent (multiple choice again) so that it&#8217;s obvious which icons don&#8217;t have a clear meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luca</title>
		<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/comment-page-1/#comment-1552</link>
		<dc:creator>Luca</dc:creator>
		<pubDate>Tue, 05 Jan 2010 09:31:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.opensource-usability-labs.com/?p=291#comment-1552</guid>
		<description>hi, 
very helpfull test, even if I don&#039;t like I have complete it with iceweasel because konqueror 3.5.9 on my machine don&#039;t menage the site very well.

bye</description>
		<content:encoded><![CDATA[<p>hi,<br />
very helpfull test, even if I don&#8217;t like I have complete it with iceweasel because konqueror 3.5.9 on my machine don&#8217;t menage the site very well.</p>
<p>bye</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Björn Balazs</title>
		<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/comment-page-1/#comment-1551</link>
		<dc:creator>Björn Balazs</dc:creator>
		<pubDate>Tue, 05 Jan 2010 08:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.opensource-usability-labs.com/?p=291#comment-1551</guid>
		<description>Hey, cool - thanks for inspiring and motivating comments :)

This is ONE approach to usability testing. Not the ONLY one. And, hey - this is open source: you are free to make it any better!

The results of the past tests proved to be very useful indeed - please wait for a summary of the results or take a look at the results of the last test here in the blog.</description>
		<content:encoded><![CDATA[<p>Hey, cool &#8211; thanks for inspiring and motivating comments <img src='http://www.opensource-usability-labs.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>This is ONE approach to usability testing. Not the ONLY one. And, hey &#8211; this is open source: you are free to make it any better!</p>
<p>The results of the past tests proved to be very useful indeed &#8211; please wait for a summary of the results or take a look at the results of the last test here in the blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/comment-page-1/#comment-1544</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 04 Jan 2010 21:07:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.opensource-usability-labs.com/?p=291#comment-1544</guid>
		<description>I think this test is really flawed.

1) The icons are confusing, even when you can &quot;sort of&quot; tell that the icon matches what you are searching for.

2) For a usability test, I would have expected a &quot;pick the best metaphor&quot; approach where you have several icons that might be associated with the term.

3) There is no &quot;I have no idea&quot; option, when none of the icons make any sense.

4) The test takes a really long time, and just shows the same 8 icons over-and-ver again...</description>
		<content:encoded><![CDATA[<p>I think this test is really flawed.</p>
<p>1) The icons are confusing, even when you can &#8220;sort of&#8221; tell that the icon matches what you are searching for.</p>
<p>2) For a usability test, I would have expected a &#8220;pick the best metaphor&#8221; approach where you have several icons that might be associated with the term.</p>
<p>3) There is no &#8220;I have no idea&#8221; option, when none of the icons make any sense.</p>
<p>4) The test takes a really long time, and just shows the same 8 icons over-and-ver again&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Panke</title>
		<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/comment-page-1/#comment-1543</link>
		<dc:creator>Panke</dc:creator>
		<pubDate>Mon, 04 Jan 2010 18:54:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.opensource-usability-labs.com/?p=291#comment-1543</guid>
		<description>I don&#039;t think, that this test generates any usefull information. Presented with 8 (or so) icons finding the only one that might be the right choice isn&#039;t hard at all. For example: Sending later. Why the hell should i choose the cross in the red button?

Show me some icons for the same purpose and i will tell you, which one does the job best - for me.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think, that this test generates any usefull information. Presented with 8 (or so) icons finding the only one that might be the right choice isn&#8217;t hard at all. For example: Sending later. Why the hell should i choose the cross in the red button?</p>
<p>Show me some icons for the same purpose and i will tell you, which one does the job best &#8211; for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: purple-bobby</title>
		<link>http://www.opensource-usability-labs.com/kde/2010/01/04/kmail-icon-test-2-have-you-participated/comment-page-1/#comment-1541</link>
		<dc:creator>purple-bobby</dc:creator>
		<pubDate>Mon, 04 Jan 2010 18:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.opensource-usability-labs.com/?p=291#comment-1541</guid>
		<description>Icons should be visually different, so that you can quickly locate the command you wish to perform, from this point of view, it does not matter what symbol appears, so long as it is different. The &#039;open&#039; icon looks too like the &#039;save&#039; one.

The icons should NOT have an inappropriate metaphoric symbol.To me: 
an &#039;open envelop&#039; implies opening/reading a received message;
does &#039;sign&#039; mean add your signature: name, address, etc., or add a tamper proof code number;
several views to the same data/document does not make much real-world sense, but &#039;paper&#039; folded over to hide and reveal other parts of the document is perhaps more real-world;
...</description>
		<content:encoded><![CDATA[<p>Icons should be visually different, so that you can quickly locate the command you wish to perform, from this point of view, it does not matter what symbol appears, so long as it is different. The &#8216;open&#8217; icon looks too like the &#8216;save&#8217; one.</p>
<p>The icons should NOT have an inappropriate metaphoric symbol.To me:<br />
an &#8216;open envelop&#8217; implies opening/reading a received message;<br />
does &#8216;sign&#8217; mean add your signature: name, address, etc., or add a tamper proof code number;<br />
several views to the same data/document does not make much real-world sense, but &#8216;paper&#8217; folded over to hide and reveal other parts of the document is perhaps more real-world;<br />
&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

