<?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/"
	>

<channel>
	<title>Design vs Art Blog &#187; Errors</title>
	<atom:link href="http://www.designvsart.com/blog/category/errors/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designvsart.com/blog</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 17 May 2010 08:48:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<cloud domain='www.designvsart.com' port='80' path='/blog/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Poka-Yoke Design</title>
		<link>http://www.designvsart.com/blog/2009/10/29/poka-yoke-design/</link>
		<comments>http://www.designvsart.com/blog/2009/10/29/poka-yoke-design/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 13:31:23 +0000</pubDate>
		<dc:creator>Alexis Brion</dc:creator>
				<category><![CDATA[Errors]]></category>
		<category><![CDATA[Input Prediction]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[User Experience]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.designvsart.com/blog/?p=380</guid>
		<description><![CDATA[Poka-Yoke is a concept coming from Japan and means mistake-proof. It could be any mechanism helping users to avoid making mistakes while using an interface or product. The concept it&#8217;s focus on prevention, influencing the users&#8217; behavior through the design of the product or interface. Poka-Yoke not only improves the user experience, it also helps [...]]]></description>
			<content:encoded><![CDATA[<p>Poka-Yoke is a concept coming from Japan and means mistake-proof. It could be any mechanism helping users to avoid making mistakes while using an interface or product. The concept it&#8217;s focus on prevention, influencing the users&#8217; behavior through the design of the product or interface. Poka-Yoke not only improves the <strong>user experience</strong>, it also helps improving safety.</p>
<p>I would like to show you some Poka-Yoke examples.</p>
<p>SIM Cards. Thanks to the <strong>trimmed corner</strong>, a SIM Card can not be put into a cell phone in a wrong way.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-735" style="border: 1px solid #000000;" title="sim_card" src="http://www.designvsart.com/blog/wp-content/uploads/2009/10/sim_card.jpg" alt="Close look to SIM Card" width="450" height="210" /> SIM Card. Picture by <a href="http://www.flickr.com/photos/declanjewell/">Declan Jewell</a>.</p>
<p style="text-align: left;">
<p>On Search. Poka-Yoke concept is used by Google&#8217;s search box and by other search engines <strong>to suggest users possible search terms</strong>. In the example, I mistyped &#8220;Poka-Yoke&#8221; so the search box proposes to search for the right term. The problem with this behavior is that these suggestions could influence what users search.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-738" style="border: 1px solid #000000;" title="poka-yoke_on_google" src="http://www.designvsart.com/blog/wp-content/uploads/2009/10/poka-yoke_on_google.png" alt="Poka-Yoke behavior on Google Search" width="450" height="148" />Google search box.</p>
<p>iPhone. Every time a user starts a new note on the Notes application for iPhone, <strong>the upper case option is on and ready for the first letter</strong>. This is a way to prevent orthographic mistakes.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-740" style="border: 1px solid #000000;" title="photo" src="http://www.designvsart.com/blog/wp-content/uploads/2009/10/photo.jpg" alt="iPhone Notes application screenshot" width="256" height="384" />iPhone Notes application screenshot.</p>
<p>USB Connector. Thanks to its <strong>inner shape</strong>, an USB connector can not be connected in the wrong way.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-743" style="border: 1px solid #000000;" title="usb_connector" src="http://www.designvsart.com/blog/wp-content/uploads/2009/10/usb_connector.jpg" alt="USB Connector, inside view" width="450" height="245" />USB Connector. Picture by <a href="http://www.flickr.com/photos/pjstoneson/">PJstoneson</a>.</p>
<p>&#8230;actually, the shape of the connector not only prevents from connecting it upside down but also to connect it in the <strong>wrong place</strong>.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-746" style="border: 1px solid #000000;" title="connectors_on_macbook" src="http://www.designvsart.com/blog/wp-content/uploads/2009/10/connectors_on_macbook.jpg" alt="Different connectors in a MacBook" width="450" height="211" />Different shapes for each connector. Picture by <a href="http://www.flickr.com/photos/goodrob13/">Goodrob13</a>.</p>
<p>Padlocks. Good padlocks <strong>do not release the key</strong> if it is not totally locked, making sure that the mechanism is totally closed and avoiding mistakes. In this case safety is a big issue.</p>
<p style="text-align: center;"><img class="aligncenter size-full wp-image-748" style="border: 1px solid #000000;" title="padlock" src="http://www.designvsart.com/blog/wp-content/uploads/2009/10/padlock.jpg" alt="Padlock in San Francisco" width="450" height="233" />A padlock. Picture by <a href="http://www.flickr.com/photos/themacinator/">Greenkozi</a>.</p>
<img src="http://www.designvsart.com/blog/?ak_action=api_record_view&id=380&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.designvsart.com/blog/2009/10/29/poka-yoke-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Problem That Happens, a Solution Designed</title>
		<link>http://www.designvsart.com/blog/2008/07/17/a-problem-that-happens-a-solution-designed/</link>
		<comments>http://www.designvsart.com/blog/2008/07/17/a-problem-that-happens-a-solution-designed/#comments</comments>
		<pubDate>Thu, 17 Jul 2008 11:58:14 +0000</pubDate>
		<dc:creator>Alexis Brion</dc:creator>
				<category><![CDATA[Errors]]></category>
		<category><![CDATA[Good Design]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[User]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.designvsart.com/blog/2008/07/17/a-problem-that-happens-a-solution-designed/</guid>
		<description><![CDATA[Accidents are gonna always happen, you can prevent them but nothing is going to stop them happening. Users loosing passwords, usernames, invoices with wrong prices, etcetera, etcetera&#8230; An important part of a good design is the prevention, how to avoid erros and headaches. But, as problems can not be totally avoided it is very important [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: x-large;"><b>A</b></span>ccidents are gonna always happen, you can prevent them but nothing is going to stop them happening. Users loosing passwords, usernames, invoices with wrong prices, etcetera, etcetera&#8230;</p>
<p><span style="background-color: rgb(255, 204, 0);">An important part of a good design is the prevention</span>, how to avoid erros and headaches. But, as problems can not be totally avoided<span style="background-color: rgb(255, 204, 0);"> it is very important to design a good &quot;recovery&quot; experience</span>, a way to solve those issues. The iTunes Store gives us an example of good problem solving design.&nbsp;</p>
<table width="550" cellspacing="1" cellpadding="1" border="0" align="center">
<tbody>
<tr>
<td style="text-align: center;"><img height="43" width="122" alt="iTunes Logo" src="http://www.designvsart.com/blog/wp-content/uploads/iTune Logo.jpg" /></td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>After buying an album I got the following invoice per email. The underlined text &quot;Ein Problem melden&quot; means in German language &quot;Notify a problem&quot;. This is great. Users could have problems with downloads or audio quality, for example. If this happens they can contact Apple in a very handy way.&nbsp;</p>
<table width="550" cellspacing="1" cellpadding="1" border="0" align="center">
<tbody>
<tr>
<td style="text-align: center;"><img height="144" width="514" border="1" alt="Notify a Problem" src="http://www.designvsart.com/blog/wp-content/uploads/Ein Problem melden.jpg" /></td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p>Problems make users unhappy but <span style="background-color: rgb(255, 204, 0);">if you provide a way to solve those issues users will understand that you are trying hard to make things work.</span></p>
<img src="http://www.designvsart.com/blog/?ak_action=api_record_view&id=378&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.designvsart.com/blog/2008/07/17/a-problem-that-happens-a-solution-designed/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Making Clear Error Messages</title>
		<link>http://www.designvsart.com/blog/2008/02/15/making-clear-error-messages/</link>
		<comments>http://www.designvsart.com/blog/2008/02/15/making-clear-error-messages/#comments</comments>
		<pubDate>Fri, 15 Feb 2008 05:00:09 +0000</pubDate>
		<dc:creator>Alexis Brion</dc:creator>
				<category><![CDATA[Errors]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web2.0]]></category>

		<guid isPermaLink="false">http://www.designvsart.com/blog/2008/02/15/making-clear-error-messages/</guid>
		<description><![CDATA[Explaining errors is one of the basic concepts in usability for the web. It is as simple and obvious as telling the user what was wrong and how to solve that problem. &#34;It is important that error messages are clear&#8230;&#34; There are many ways of explaining errors, like going back to the web form marking [...]]]></description>
			<content:encoded><![CDATA[<p><b>Explaining errors</b> is one of the basic concepts in <b>usability for the web</b>. It is as simple and obvious as telling the user what was wrong and how to solve that problem.</p>
<h3 style="text-align: center;">
<p><i> &quot;It is important that error messages are clear&#8230;&quot;</i></h3>
<p>There are many ways of explaining errors, like going back to the <b>web form</b> marking the erroneous fields. It is important that error <b>messages are clear</b>, avoid things like &quot;error 4055&quot;.</p>
<table width="550" cellspacing="1" cellpadding="1" border="0" align="center">
<tbody>
<tr>
<td style="text-align: center;"><img width="500" height="220" border="1" alt="Digg Error Message" src="http://www.designvsart.com/blog/wp-content/uploads/Digg Error 20080207(1).jpg" /></td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p><a target="_blank" href="http://www.digg.com"> Digg</a>, the social bookmarking website, displays from time to time an error message at the end of the submission procedure. I don&#8217;t really know why this happens because the error message is not clear, no solution is proposed and there is no entry about that on the FAQ section. The <b>user experience</b> could not be worse in this situation.</p>
<p><a target="_self" href="http://www.designvsart.com/blog/category/errors/">See previous entries about this topic.</a></p>
<img src="http://www.designvsart.com/blog/?ak_action=api_record_view&id=314&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.designvsart.com/blog/2008/02/15/making-clear-error-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Better User Experience With Meaningful Errors Messages</title>
		<link>http://www.designvsart.com/blog/2008/01/18/better-user-experience-with-meaningful-errors-messages/</link>
		<comments>http://www.designvsart.com/blog/2008/01/18/better-user-experience-with-meaningful-errors-messages/#comments</comments>
		<pubDate>Fri, 18 Jan 2008 05:39:14 +0000</pubDate>
		<dc:creator>Alexis Brion</dc:creator>
				<category><![CDATA[Bad Design]]></category>
		<category><![CDATA[Errors]]></category>
		<category><![CDATA[Good Design]]></category>
		<category><![CDATA[Interfaces]]></category>
		<category><![CDATA[Online Shopping]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://www.designvsart.com/blog/2008/01/18/better-user-experience-with-meaningful-errors-messages/</guid>
		<description><![CDATA[Giving users meaningful error messages is very important but, maybe, even more important to improve the user experience is to provide a solution to the error that is rising the error message. &#34;Give always an explanatory error message&#8230;&#34; It is very frustrating for users to get error messages and no way to solve the problem. [...]]]></description>
			<content:encoded><![CDATA[<p>Giving users <b>meaningful error messages</b> is very important but, maybe, even more important to improve the <b>user experience</b> is to provide a solution to the error that is rising the error message.</p>
<h3 style="text-align: center;">
<p><i> &quot;Give always an explanatory error message&#8230;&quot;</i></h3>
<p>It is very frustrating for users to get error messages and no way to solve the problem. Give always an explanatory error message and include in your <b>design an obvious way to keep on with the process</b>.</p>
<table width="550" cellspacing="1" cellpadding="1" border="0" align="center">
<tbody>
<tr>
<td style="text-align: center;"><img width="500" height="208" border="1" src="http://www.designvsart.com/blog/wp-content/uploads/Lufthansa Big 20080117.png" alt="Lufthansa Ticket Reservation Message" /></td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p><a href="http://www.lufthansa.com" target="_blank" title="Go to Lufthansa website"> Lufthansa</a>, the airline, gave me the other day an example of poor <b>web design</b>. After choosing a flight I got the option to enter my frequent flyer username and password. The system didn&#8217;t recognize my username and asked me to <i>&quot;Create new user profile&quot;</i>. Well, there was NO &quot;Create new user profile&quot; link on that page.</p>
<table width="550" cellspacing="1" cellpadding="1" border="0" align="center">
<tbody>
<tr>
<td style="text-align: center;"><img width="460" height="69" border="1" src="http://www.designvsart.com/blog/wp-content/uploads/Lufthansa Detail 20080117.png" alt="Lufthansa Detail Error Message" /></td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p><b> Improve usability</b> and <b>user experience</b> with a web design that avoids error messages that tell the users that she was wrong and don&#8217;t provide solutions. <a href="http://www.designvsart.com/blog/category/errors/" target="_self">More Design vs Art articles about error messages. </a></p>
<img src="http://www.designvsart.com/blog/?ak_action=api_record_view&id=319&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.designvsart.com/blog/2008/01/18/better-user-experience-with-meaningful-errors-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Meaningful Error Messages, Usability Issue</title>
		<link>http://www.designvsart.com/blog/2008/01/11/meaningful-error-messages-usability-issue/</link>
		<comments>http://www.designvsart.com/blog/2008/01/11/meaningful-error-messages-usability-issue/#comments</comments>
		<pubDate>Fri, 11 Jan 2008 06:08:08 +0000</pubDate>
		<dc:creator>Alexis Brion</dc:creator>
				<category><![CDATA[Bad Design]]></category>
		<category><![CDATA[Errors]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web2.0]]></category>

		<guid isPermaLink="false">http://www.designvsart.com/blog/2008/01/11/meaningful-error-messages-usability-issue/</guid>
		<description><![CDATA[Reddit provides an example of poor usability during the site submission form. They try to make fun of users&#8217; errors. If the user enters a wrong CAPTCHA the website displays a &#34;your letters stink&#34; message. &#34;websites should have meaningful and explanatory error messages&#8230;&#34; Even worse, the instructions of what to do with that weird image [...]]]></description>
			<content:encoded><![CDATA[<p><a target="_blank" href="http://www.reddit.com">Reddit</a> provides an example of poor <b>usability</b> during the site submission form. They try to make fun of users&#8217; errors. If the user enters a wrong CAPTCHA the website displays a <b>&quot;your letters stink&quot;</b> message.</p>
<h3 style="text-align: center;">
<p><i> &quot;websites should have meaningful and explanatory error messages&#8230;&quot;</i></h3>
<p>
Even worse, the instructions of what to do with that weird image (many users don&#8217;t know what a CAPTCHA is) were inside the &quot;<i>human?</i>&quot; field, so after entering something there the <b>instructions disappear</b>. 
</p>
<table width="550" cellspacing="1" cellpadding="1" border="0" align="center">
<tbody>
<tr>
<td style="text-align: center;"><img width="450" height="228" border="1" alt="Reddit Screenshot" src="http://www.designvsart.com/blog/wp-content/uploads/Reddit Screenshot 20080111.jpg" /></td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
<p><b> Error messages</b> are not something users like seeing. Usually they are frustrating, so websites should have meaningful and explanatory error messages, they should tell users <b>how to resolve the problem</b>. Remember that if your users are not allow to finish a process, you might be loosing money. </p>
<p>&nbsp;</p>
<table width="550" cellspacing="1" cellpadding="1" border="0" align="center">
<tbody>
<tr>
<td style="text-align: center;"><img width="174" height="99" border="1" alt="Reddit Your Letters Stink" src="http://www.designvsart.com/blog/wp-content/uploads/Reddit Your Letters Stink 20080111.jpg" /></td>
</tr>
</tbody>
</table>
<p>
</p>
<p>
Remember that after an error users usually want an <b>explanatory message</b> that helps them <b>reach their goal</b> (e.g. for example buying something at your site!)</p>
<p>&nbsp;&nbsp;</p>
<img src="http://www.designvsart.com/blog/?ak_action=api_record_view&id=312&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://www.designvsart.com/blog/2008/01/11/meaningful-error-messages-usability-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
