<?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/"
	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>Comments on: Finding Steve Fossett: When good UI design can mean life or death</title>
	<atom:link href="http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/</link>
	<description>Personal blog of Paul Annett, web designer and co-founder of Supernice Studio Ltd.</description>
	<lastBuildDate>Thu, 03 May 2012 18:04:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Duncan Cumming</title>
		<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/#comment-291</link>
		<dc:creator><![CDATA[Duncan Cumming]]></dc:creator>
		<pubDate>Fri, 28 Sep 2007 20:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://paulannett.co.uk/mechanical-turk-ui-design#comment-291</guid>
		<description><![CDATA[I would add that some exposure corecting software would also be very useful. Some of the images are very dark, and yet the information is there. It takes a long time to save the picture, then fix it using Adobe Photoshop or whatever, then go back to mturk to report. A simple &quot;fix the exposure&quot; buton would make the user&#039;s task much simpler. Of course, this is a substantial programming effort but a lot of mturk tasks are based on photographs, so such a feature would be useful long after the Fossett search is over.

I agree with requiring a log in, any life-and-death task must have at least a minimal amount of accoutability involved.]]></description>
		<content:encoded><![CDATA[<p>I would add that some exposure corecting software would also be very useful. Some of the images are very dark, and yet the information is there. It takes a long time to save the picture, then fix it using Adobe Photoshop or whatever, then go back to mturk to report. A simple &#8220;fix the exposure&#8221; buton would make the user&#8217;s task much simpler. Of course, this is a substantial programming effort but a lot of mturk tasks are based on photographs, so such a feature would be useful long after the Fossett search is over.</p>
<p>I agree with requiring a log in, any life-and-death task must have at least a minimal amount of accoutability involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anita</title>
		<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/#comment-290</link>
		<dc:creator><![CDATA[Anita]]></dc:creator>
		<pubDate>Sat, 22 Sep 2007 03:32:27 +0000</pubDate>
		<guid isPermaLink="false">http://paulannett.co.uk/mechanical-turk-ui-design#comment-290</guid>
		<description><![CDATA[I couldn&#039;t agree more!  As a person with (beginning) arthritis and full-on mouse-elbow, I know my head and heart could go a LOT longer working HITs if my poor old body didn&#039;t give out first!]]></description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more!  As a person with (beginning) arthritis and full-on mouse-elbow, I know my head and heart could go a LOT longer working HITs if my poor old body didn&#8217;t give out first!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Barbalace</title>
		<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/#comment-289</link>
		<dc:creator><![CDATA[Ken Barbalace]]></dc:creator>
		<pubDate>Thu, 20 Sep 2007 16:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://paulannett.co.uk/mechanical-turk-ui-design#comment-289</guid>
		<description><![CDATA[Paul I completely agree with you, Mechanical Turk&#039;s UI design is simply awful and I wrote as much in my own blog post earlier this week.

It always amazes me that companies as big as Amazon.com can do such a bad job of UI design.  There doesn&#039;t seem to have been one ounce of thought into usability or function. I can not imagine how much potential effort that could have been used looking for Steve Fossett was wasted on the clunky process that is Mechanical Turk.

I will disagree, however, about requiring people to log in. I see this as very valuable in tracking reporting habits.  As an evaluator, I would want to know if reports are coming from someone who has an excessively high rate of reporting leads.  At the same time I would take keen interest in a lead posted by someone who has looked at lots of photos, but made very few reports.  I also see requiring logins as reducing the potential for mischief.]]></description>
		<content:encoded><![CDATA[<p>Paul I completely agree with you, Mechanical Turk&#8217;s UI design is simply awful and I wrote as much in my own blog post earlier this week.</p>
<p>It always amazes me that companies as big as Amazon.com can do such a bad job of UI design.  There doesn&#8217;t seem to have been one ounce of thought into usability or function. I can not imagine how much potential effort that could have been used looking for Steve Fossett was wasted on the clunky process that is Mechanical Turk.</p>
<p>I will disagree, however, about requiring people to log in. I see this as very valuable in tracking reporting habits.  As an evaluator, I would want to know if reports are coming from someone who has an excessively high rate of reporting leads.  At the same time I would take keen interest in a lead posted by someone who has looked at lots of photos, but made very few reports.  I also see requiring logins as reducing the potential for mischief.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nice Paul</title>
		<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/#comment-288</link>
		<dc:creator><![CDATA[Nice Paul]]></dc:creator>
		<pubDate>Tue, 18 Sep 2007 16:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://paulannett.co.uk/mechanical-turk-ui-design#comment-288</guid>
		<description><![CDATA[Sjors: I think that websites should be easy to use regardless of the task at hand, not just if its needed for search and rescue.]]></description>
		<content:encoded><![CDATA[<p>Sjors: I think that websites should be easy to use regardless of the task at hand, not just if its needed for search and rescue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sjors</title>
		<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/#comment-287</link>
		<dc:creator><![CDATA[Sjors]]></dc:creator>
		<pubDate>Tue, 18 Sep 2007 15:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://paulannett.co.uk/mechanical-turk-ui-design#comment-287</guid>
		<description><![CDATA[Amazon&#039;s website was never designed to be a search and rescue platform, so you can&#039;t really blame them, I think. That said, the sooner they upgrade the layout, the better.
I need about 3 seconds per photo, because I scroll down while the page is loading, press the no button and hit &#039;enter&#039; after I&#039;ve seen the image.
Another great feature would be a &#039;back&#039; option, because I tend to make mistakes every now and then.]]></description>
		<content:encoded><![CDATA[<p>Amazon&#8217;s website was never designed to be a search and rescue platform, so you can&#8217;t really blame them, I think. That said, the sooner they upgrade the layout, the better.<br />
I need about 3 seconds per photo, because I scroll down while the page is loading, press the no button and hit &#8216;enter&#8217; after I&#8217;ve seen the image.<br />
Another great feature would be a &#8216;back&#8217; option, because I tend to make mistakes every now and then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pauldwaite</title>
		<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/#comment-286</link>
		<dc:creator><![CDATA[pauldwaite]]></dc:creator>
		<pubDate>Mon, 17 Sep 2007 13:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://paulannett.co.uk/mechanical-turk-ui-design#comment-286</guid>
		<description><![CDATA[A few months back someone put up a little Java app, which showed frames of Michael Jackson’s first TV performance of Billie Jean, and got users to drag a square around where his white glove was.

I guess it’s easier to craft the UI when you’re the only person writing the software (as I assume that person was), but it’s always important.]]></description>
		<content:encoded><![CDATA[<p>A few months back someone put up a little Java app, which showed frames of Michael Jackson’s first TV performance of Billie Jean, and got users to drag a square around where his white glove was.</p>
<p>I guess it’s easier to craft the UI when you’re the only person writing the software (as I assume that person was), but it’s always important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alun Rowe</title>
		<link>http://nicepaul.com/2007/09/16/mechanical-turk-ui-design/#comment-285</link>
		<dc:creator><![CDATA[Alun Rowe]]></dc:creator>
		<pubDate>Mon, 17 Sep 2007 10:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://paulannett.co.uk/mechanical-turk-ui-design#comment-285</guid>
		<description><![CDATA[I felt exactly the same about the task.

I can understand the first time they want people to read the details of the task but after that you just want to get through as many photos as possible.  Adding a preloader would be useful too so it is just a case of look, click, look click etc]]></description>
		<content:encoded><![CDATA[<p>I felt exactly the same about the task.</p>
<p>I can understand the first time they want people to read the details of the task but after that you just want to get through as many photos as possible.  Adding a preloader would be useful too so it is just a case of look, click, look click etc</p>
]]></content:encoded>
	</item>
</channel>
</rss>

