<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;CkcBQXs_fip7ImA9WxJUF04.&quot;"><id>tag:blogger.com,1999:blog-9968619</id><updated>2009-07-16T09:40:50.546+02:00</updated><title>uselog.com | the product usability weblog</title><subtitle type="html">Online resource about consumer product usability: news, research, events, design examples, and blatantly subjective opinions. Also includes links en literature on usability.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://www.uselog.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://www.uselog.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>416</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/uselog" type="application/atom+xml" /><feedburner:browserFriendly>This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site.</feedburner:browserFriendly><entry gd:etag="W/&quot;CkcBQXs-fip7ImA9WxJUF04.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2370256106747883709</id><published>2009-07-16T09:14:00.005+02:00</published><updated>2009-07-16T09:40:50.556+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-16T09:40:50.556+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><category scheme="http://www.blogger.com/atom/ns#" term="usability research" /><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><title>The Touch project: exploring the possibilities of RFID</title><content type="html">&lt;object width="400" height="225"&gt;&lt;param name="allowfullscreen" value="true" /&gt;&lt;param name="allowscriptaccess" value="always" /&gt;&lt;param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=3684601&amp;amp;server=vimeo.com&amp;amp;show_title=1&amp;amp;show_byline=1&amp;amp;show_portrait=0&amp;amp;color=ffffff&amp;amp;fullscreen=1" /&gt;&lt;embed src="http://vimeo.com/moogaloop.swf?clip_id=3684601&amp;amp;server=vimeo.com&amp;amp;show_title=1&amp;amp;show_byline=1&amp;amp;show_portrait=0&amp;amp;color=ffffff&amp;amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="225"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;br /&gt;&lt;br /&gt;At &lt;a href="http://www.nearfield.org/"&gt;nearfield.org&lt;/a&gt; you'll find a weblog on &lt;a href="http://en.wikipedia.org/wiki/Near_Field_Communication"&gt;nearfield communication&lt;/a&gt;, run by the 'Touch' research project, which investigates the possibilities for new interaction styles using near field communication (NFC). The project features an inter-disciplinary team involved in social and cultural enquiry, interaction/industrial design, rapid prototyping, software, testing and exhibitions. It is based in the &lt;a href="http://www.aho.no/en/AHO/Institutter/Industridesign/"&gt;Interaction Design&lt;/a&gt; department of the &lt;a href="http://www.aho.no/"&gt;Oslo School of Architecture and Design&lt;/a&gt; in Norway. The project ends this year, so it will be interesting to see the end results rolling out.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-2370256106747883709?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/2370256106747883709/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=2370256106747883709&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2370256106747883709?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2370256106747883709?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/5OSp-AznRY8/touch-project-exploring-possibilities.html" title="The Touch project: exploring the possibilities of RFID" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/07/touch-project-exploring-possibilities.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0QHQHw5eCp7ImA9WxJUFkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2413176792826925075</id><published>2009-07-14T09:41:00.006+02:00</published><updated>2009-07-15T10:08:51.220+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-15T10:08:51.220+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="user research" /><title>Online concept evaluation in Philips' Simplicity Labs</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_QD5J-lhOPc0/Slw6OK7NuMI/AAAAAAAAAO0/3v4wbahsMNI/s1600-h/Picture+7.png"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 229px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/Slw6OK7NuMI/AAAAAAAAAO0/3v4wbahsMNI/s400/Picture+7.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5358221671789344962" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.research.philips.com/"&gt;Philips Research&lt;/a&gt; usually does not work on the next big thing in consumer electronics, but on the next-next big thing in consumer electronics. To give you a sense of the timelines we're talking about: back in 1994 they were exploring the possibilities of the networked home in the &lt;a href="http://www.research.philips.com/technologies/projects/homelab/wwice.html"&gt;WWICE project&lt;/a&gt;. &lt;br /&gt;&lt;br /&gt;Over the past years user-involvement has become more and more important when they develop future product concepts and now Philips Research is opening up: on their &lt;a href="http://www.simplicitylabs.net/"&gt;SimplicityLabs&lt;/a&gt; website you can see, evaluate and contribute to new interaction concepts. The presentation is not extremely engaging, and some of the concepts may make you wonder: will I ever use this? But that's the idea...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-2413176792826925075?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/2413176792826925075/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=2413176792826925075&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2413176792826925075?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2413176792826925075?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/v9sXchAJ1MQ/online-concept-evaluation-in-philips.html" title="Online concept evaluation in Philips' Simplicity Labs" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_QD5J-lhOPc0/Slw6OK7NuMI/AAAAAAAAAO0/3v4wbahsMNI/s72-c/Picture+7.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/07/online-concept-evaluation-in-philips.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4BSH84fip7ImA9WxJUEkw.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-5640647029899488432</id><published>2009-07-10T10:24:00.006+02:00</published><updated>2009-07-10T11:09:19.136+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-10T11:09:19.136+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="consumer electronics" /><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><title>Overview of digital camera user interfaces</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://i.gizmodo.com/5165225/click-a-visual-tour-of-camera-interfaces?skyline=true&amp;s=x"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 280px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/Slb64y2UErI/AAAAAAAAAOk/hvgiIkLxMGo/s400/Picture+1.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5356744660432982706" /&gt;&lt;/a&gt;&lt;br /&gt;Gizmodo provides an &lt;a href="http://i.gizmodo.com/5165225/click-a-visual-tour-of-camera-interfaces?skyline=true&amp;s=x"&gt;extensive overview&lt;/a&gt; of the user interfaces of all major digital camera manufacturers such as Canon, Nikon and Samsung.&lt;blockquote&gt;User interfaces matter in these cameras more than ever because they’re increasingly the major way you drill down to change settings or switch modes—rather than manually cranking a dial, like on a pro DSLR. Some are pretty good (Canon, Samsung) while some are pretty bad (Casio).&lt;/blockquote&gt;[&lt;span style="font-style:italic;"&gt;Via &lt;a href="http://www.smallsurfaces.com/"&gt;Small Surfaces&lt;/a&gt;, which sadly fell silent after a streak of excellent posts&lt;/span&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-5640647029899488432?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/5640647029899488432/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=5640647029899488432&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5640647029899488432?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5640647029899488432?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/ReYvHPitTI0/overview-of-digital-camera-user.html" title="Overview of digital camera user interfaces" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_QD5J-lhOPc0/Slb64y2UErI/AAAAAAAAAOk/hvgiIkLxMGo/s72-c/Picture+1.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/07/overview-of-digital-camera-user.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUEESXgzcSp7ImA9WxJUEEk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-343860463301373076</id><published>2009-07-08T09:31:00.009+02:00</published><updated>2009-07-08T11:00:08.689+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-08T11:00:08.689+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><category scheme="http://www.blogger.com/atom/ns#" term="computers/software" /><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="events" /><title>When a UI paradigm reaches its limits: Office 2007</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://videos.visitmix.com/MIX08/UX09"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 300px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/SlRQncEEz3I/AAAAAAAAAOU/2I5z3Xztykk/s400/Harris_UX09_Office-menu-items.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5355994495328767858" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;In &lt;a href="http://videos.visitmix.com/MIX08/UX09"&gt;this presentation&lt;/a&gt; at &lt;a href="http://archive.visitmix.com/2008/"&gt;Mix08&lt;/a&gt; on the development of the Microsoft Office 2007 'ribbon' interface, &lt;a href="http://blogs.msdn.com/jensenh/"&gt;Jensen Harris&lt;/a&gt;, design lead for the MS Office User Experience team provides an excellent example of how a UI paradigm can reach a point, where it has to be overhauled completely, because it can no longer sustain the &lt;a href="http://www.uselog.com/2008/03/8-tips-to-manage-feature-creep-blithe.html"&gt;increasing functionality&lt;/a&gt; of the product. In the 45 minute presentation he very openly discusses Microsoft's struggle of fitting all (new) features into the existing user interface, leading to 'interesting' UI elements such as hidden menu items, &lt;a href="http://www.informit.com/articles/article.aspx?p=102147"&gt;task panes&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Office_Assistant"&gt;paperclips&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;See also:&lt;/span&gt;&lt;br /&gt;&gt; &lt;a href="http://www.adaptivepath.com/ideas/essays/archives/000977.php"&gt;Adaptive path interviews Jensen Harris about the ribbon&lt;/a&gt;&lt;br /&gt;&gt; &lt;a href="http://www.uselog.com/2007/09/office-2007-new-features-that-were.html"&gt;No new features in Office 2007&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;[Via &lt;a href="http://blogs.harvardbusiness.org/merholz/2009/06/why-microsoft-had-to-destroy-w.html"&gt;HBR blogs&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-343860463301373076?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/343860463301373076/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=343860463301373076&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/343860463301373076?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/343860463301373076?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/ljwKeBesiEI/when-ui-paradigm-reaches-its-limits.html" title="When a UI paradigm reaches its limits: Office 2007" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_QD5J-lhOPc0/SlRQncEEz3I/AAAAAAAAAOU/2I5z3Xztykk/s72-c/Harris_UX09_Office-menu-items.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/07/when-ui-paradigm-reaches-its-limits.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE4NQXczfip7ImA9WxJUEkw.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-7608375311998103708</id><published>2009-07-03T09:11:00.003+02:00</published><updated>2009-07-10T11:09:50.986+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-10T11:09:50.986+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="consumer electronics" /><category scheme="http://www.blogger.com/atom/ns#" term="simplicity" /><title>13-year old reviews the original Sony Walkman</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://news.bbc.co.uk/2/hi/uk_news/magazine/8117619.stm#graphic"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://newsimg.bbc.co.uk/media/images/45984000/jpg/_45984325_scott_466.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;On the occasion of the &lt;a href="http://news.yahoo.com/s/ap/20090701/ap_on_en_ot/as_japan_sony_walkman"&gt;30-year anniversary&lt;/a&gt; of the Sony Walkman BBC's The Magazine asked 13 year old Scott Campbell to trade his iPod for the original Sony Walkman for a week, which led to a (hilarious) &lt;a href="http://news.bbc.co.uk/2/hi/uk_news/magazine/8117619.stm#graphic"&gt;review&lt;/a&gt;, including gems like this one:&lt;blockquote&gt;It took me three days to figure out that there was another side to the tape. That was not the only naive mistake that I made; I mistook the metal/normal switch on the Walkman for a genre-specific equaliser, but later I discovered that it was in fact used to switch between two different types of cassette.&lt;/blockquote&gt;Earlier the simplicity of the first walkman was heralded in an article called &lt;a href="http://www.technologyreview.com/Infotech/18620/page1/"&gt;Objects of Desire&lt;/a&gt; (members only) in Technology Review, which included the following quote:&lt;blockquote&gt;"It has simplicity of use," says Logan. "You could give it to someone who's never used one before and they can use it. "&lt;/blockquote&gt; And at the time I read that, &lt;a href="http://www.uselog.com/2007/05/simplicity-of-sony-walkman.html"&gt;I totally agreed&lt;/a&gt;. Only to be proven wrong by 13-year old Scott. Back then, in the 1980's, you could give the walkman to anyone and they'd know how to use it (also because in comparison to an iPod it has way less features), but today's (younger) users lack some of the required knowledge to interact with it. Once again it turns out that there is no such thing as a usable product. It really depends on who will interact with the product, what knowledge and skills this person has, and in what kind of context the interaction takes place.&lt;br /&gt;&lt;br /&gt;[Via &lt;a href="http://nickbaum.com/2009/06/13-year-old-reviews-walkman/"&gt;Nickbaum&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-7608375311998103708?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/7608375311998103708/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=7608375311998103708&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7608375311998103708?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7608375311998103708?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/-2tEg9763VY/13-year-old-reviews-original-sony.html" title="13-year old reviews the original Sony Walkman" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://www.uselog.com/2009/07/13-year-old-reviews-original-sony.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A04ERH85fCp7ImA9WxJVFUk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-6776895441867461609</id><published>2009-07-02T13:55:00.005+02:00</published><updated>2009-07-02T17:51:45.124+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-02T17:51:45.124+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="office equipment" /><category scheme="http://www.blogger.com/atom/ns#" term="usability marketing" /><title>Usability as sales argument for Sharp copiers</title><content type="html">&lt;object width="400" height="344"&gt;&lt;param name="movie" value="http://www.youtube.com/v/nx3MvoUR1io&amp;hl=en&amp;fs=1&amp;"&gt;&lt;/param&gt;&lt;param name="allowFullScreen" value="true"&gt;&lt;/param&gt;&lt;param name="allowscriptaccess" value="always"&gt;&lt;/param&gt;&lt;embed src="http://www.youtube.com/v/nx3MvoUR1io&amp;hl=en&amp;fs=1&amp;" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="400" height="324"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;br /&gt;&lt;br /&gt;In addition to &lt;a href="http://www.uselog.com/2005/11/usability-at-xerox-when-user-hits.html"&gt;Xerox&lt;/a&gt; - just push the green button - and &lt;A HREF="http://portal.acm.org/citation.cfm?id=1125480"&gt;Océ&lt;/a&gt;, who have been paying attention to the usability of their copiers and advertising that, we can now add Sharp to the 'usable copiers' list. Or at least advertised as usable. In the commercial above, the protagonist asks the following question:&lt;blockquote&gt;Why does my company have so many different printers and copiers, all different brands, with different controls? Give me one product line with a big colorful LCD screen and common controls. [...] &lt;br /&gt;And I don't wanna use one of those mini-screen keyboards! How about: a built-in keyboard? &lt;woosh, keyboard flies out...&gt; &lt;br /&gt;Was that too much too ask?&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-6776895441867461609?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/6776895441867461609/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=6776895441867461609&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/6776895441867461609?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/6776895441867461609?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/28ChWhlqfFk/usability-as-sales-argument-for-sharp.html" title="Usability as sales argument for Sharp copiers" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/07/usability-as-sales-argument-for-sharp.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcMQ3g-eyp7ImA9WxJVGU0.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-1342998096291249912</id><published>2009-06-29T14:18:00.003+02:00</published><updated>2009-07-06T20:48:02.653+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-06T20:48:02.653+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="non-electronics" /><category scheme="http://www.blogger.com/atom/ns#" term="public design" /><title>Designing usable money is not nickel and dime stuff</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_QD5J-lhOPc0/SkbiElJ7DgI/AAAAAAAAANc/0RKoBUpeFXg/s1600-h/US-Coins_small.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 128px;" src="http://2.bp.blogspot.com/_QD5J-lhOPc0/SkbiElJ7DgI/AAAAAAAAANc/0RKoBUpeFXg/s400/US-Coins_small.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5352213775497498114" /&gt;&lt;/a&gt;&lt;br /&gt;One of the perks of spending some time abroad is that you get to be naive again. You are not accustomed to the design of what you interact with in daily life, so you see new things. I've had the opportunity and pleasure of spending two months at &lt;a href="http://www.northwestern.edu"&gt;Northwestern University&lt;/a&gt;'s &lt;a href="http://www.segal.northwestern.edu/"&gt;Segal Design Institute&lt;/a&gt; and &lt;a href="http://www.mmm.northwestern.edu/"&gt;MMM-program&lt;/a&gt;. And for all the things I thoroughly enjoyed in the US, I must say, it was not the design of the coins and banknotes.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;What confused me about US coins&lt;/span&gt;&lt;br /&gt;First of all, looking at the coins (pictured above) you can see that it's not very clearly indicated what the denomination of the coins is. On most of them it is printed in quite a small typeface, and in the case of the 10 cent coin it doesn't even say that it's a ten cent coin. Just 'one dime', which basically is &lt;a href="http://en.wikipedia.org/wiki/Jargon"&gt;jargon&lt;/a&gt; to an ignorant foreigner like me. And then there's the size. The five cent coin is bigger than the 10 cent coin (but the material looks very similar). I guess it's because traditionally the value of a coin was inherent - it should actually be worth what it represented. Once again, no biggie if you've been using it for years, but for me - the naive Dutch guy - that was pretty confusing. Especially because in the line at the counter you don't usually have lots of time to start reviewing each coin. You'll get nasty looks from the people in line behind you.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkbiRNQyYSI/AAAAAAAAANk/taDIzcS_rzg/s1600-h/Dutch_guilder.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 107px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkbiRNQyYSI/AAAAAAAAANk/taDIzcS_rzg/s400/Dutch_guilder.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5352213992422138146" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;The old Dutch Guilder coins&lt;/span&gt;&lt;br /&gt;Now, here's a range of coins that's different: the coins of the old &lt;a href="http://en.wikipedia.org/wiki/Dutch_guilder"&gt;Dutch Guilder&lt;/a&gt;. Sorry for the slight hint of chauvinism here, but this is just the best example of functional coin design I know. They're obviously all designed using the same design language. The designer, &lt;a href="http://www.vividvormgeving.nl/vormgeverpagina/ninaber.htm"&gt;Bruno Ninaber van Eyben&lt;/a&gt;, chose to communicate the denomination of the coins using their size, material, typography and a system of lines. Note that the 10 and 5 cent coins only have vertical lines, the guilder and the quarter have horizontal and vertical lines, and the 2,5 guilder coin (rijksdaalder) has vertical, horizontal and diagonal lines. I can't be sure, but I think a naive user would have less trouble with these coins than with the US coins.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;US banknotes&lt;/span&gt;&lt;br /&gt;In addition to being outsmarted by coins, there were banknotes to make my life harder. My gripe with US banknotes (but many bills all over the world have the same issue) is that they all have &lt;a href="http://en.wikipedia.org/wiki/File:USCurrency_Federal_Reserve.jpg"&gt;the same color&lt;/a&gt;. Basically in your wallet a stack of Dollar bills looks like this:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_QD5J-lhOPc0/SkbkzMS4sBI/AAAAAAAAANs/oLIaBNcbdnc/s1600-h/US-bills-stack.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 208px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/SkbkzMS4sBI/AAAAAAAAANs/oLIaBNcbdnc/s400/US-bills-stack.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5352216775301312530" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And those are actually 1, 10, 20 and 50 dollar bills in that picture. The only way to distinguish them properly is to read the denomination. Recently the five Dollar bill got &lt;a href="http://www.typography.com/ask/showBlog.php?blogID=93"&gt;a slight makeover&lt;/a&gt;, making the denomination easier to distinguish, but the overall color of the banknote remains the same. &lt;del&gt;By the way, you don't have to be foreign to notice this issue. American&lt;/del&gt;Richard Smith has started the &lt;a href="http://richardsmith.posterous.com/"&gt;The Dollar Redesign Project&lt;/a&gt;: anyone can submit their designs for a better Dollar.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Dutch banknotes of the guilder&lt;/span&gt;&lt;br /&gt;But aren't most banknotes of the same generic color? Well, no. Take a look at these - again, I'm sorry - &lt;a href="http://www.rgaros.nl/money/netherlands.html"&gt;Dutch banknotes&lt;/a&gt; by Ootje Oxenaar, once heralded by the English visual design magazine Creative Review as &lt;a href="http://www.creativereview.co.uk/cr-blog/2007/february/the-money-maker"&gt;the most beautiful money in the world&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkblnfeJ6mI/AAAAAAAAAN0/PrP-UzheEmA/s1600-h/Oxenaar-guilder-notes.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 225px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkblnfeJ6mI/AAAAAAAAAN0/PrP-UzheEmA/s400/Oxenaar-guilder-notes.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5352217673802050146" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;But actually I'm not into them because of their beauty. I love the functional use of graphic design in these banknotes: because of their very distinguishable color scheme (and slightly different sizes), if you put them in a stack in your wallet, you get this:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkbmHHrKS6I/AAAAAAAAAN8/KkFCvpGbofk/s1600-h/Dutch-bills-oxenaar.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 239px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkbmHHrKS6I/AAAAAAAAAN8/KkFCvpGbofk/s400/Dutch-bills-oxenaar.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5352218217169963938" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And that makes it much easier to locate the right one. Now, the aforementioned Guilder coins and bills have of course been replaced by the Euro &lt;a href="http://en.wikipedia.org/wiki/Euro_coins"&gt;coins&lt;/a&gt; and &lt;a href="http://en.wikipedia.org/wiki/Euro_banknotes"&gt;banknotes&lt;/a&gt;. But thankfully the Euro bills and coins have the same properties that made the 'design of the Guilder' so appealing to me: differences in color and size, clear typography, and an overall design language. Though I should say I find the graphic design of the bills not particularly inspiring.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;A lack of incentive&lt;/span&gt;&lt;br /&gt;So why are there so many poorly designed banknotes around? These are products that are used by millions everyday. Why not make that usage a little easier? Well, I think first of all there is no incentive for the creator of the notes to implement a better design, as usage problems with bills don't cause product returns or customer complaints at the help desk, and people have no alternative. Users of the - let's just say - Australian Dollar will not suddenly turn to the Euro because the Austrialian Dollar could have been designed better. And there's lots of incentives to keep stick with an old design: tradition, nostalgia, etc. The design of the Dollar bills stems from the 1930s. That's a good deal of tradition, right there. And if you want to do it right you have to design and replace a whole range of coins or bills at once. That's quite the logistics operation. So in the end it probably all comes down to the motivation of a country's central bank.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;More about Ootje Ooxenaar&lt;/span&gt;&lt;br /&gt;&gt; &lt;a href="http://www.rgaros.nl/money/oxenaar/index.html"&gt;Transcript of lecture by Ootje Oxenaar on designing banknotes&lt;/a&gt;&lt;br /&gt;&gt; &lt;a href="http://www.youtube.com/watch?v=m5BlybJGiiU"&gt;Interview with Ootje Oxenaar on YouTube&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-1342998096291249912?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/1342998096291249912/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=1342998096291249912&amp;isPopup=true" title="7 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1342998096291249912?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1342998096291249912?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/UDuW-hXOnQo/designing-usable-money-is-not-nickel_29.html" title="Designing usable money is not nickel and dime stuff" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_QD5J-lhOPc0/SkbiElJ7DgI/AAAAAAAAANc/0RKoBUpeFXg/s72-c/US-Coins_small.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">7</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/designing-usable-money-is-not-nickel_29.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QMQH4-eip7ImA9WxJVEE8.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-9055697568692224820</id><published>2009-06-26T15:03:00.004+02:00</published><updated>2009-06-26T15:03:01.052+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-26T15:03:01.052+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mobile phones" /><title>How to dial phonewords on a Blackberry?</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_QD5J-lhOPc0/SkQ8Bt9Bz2I/AAAAAAAAANM/7Ssa7MIV46E/s1600-h/phone_blackberry_keyboard.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 145px;" src="http://2.bp.blogspot.com/_QD5J-lhOPc0/SkQ8Bt9Bz2I/AAAAAAAAANM/7Ssa7MIV46E/s400/phone_blackberry_keyboard.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5351468257436094306" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;On phones with a regular keypad (left) on every numbered key there's three letters as well, allowing for the use of &lt;a href="http://en.wikipedia.org/wiki/Phoneword"&gt;phonewords&lt;/a&gt; or vanity numbers. Think &lt;a href="http://www.1800flowers.com"&gt;1-800-flowers&lt;/a&gt; or &lt;a href="http://www.enterprise.com"&gt;1-800-rent-a-car&lt;/a&gt;. In the US, advertisers often only list the phoneword (as in the photo below). But I was just wondering: how do you enter a phoneword number on a Blackberry keypad (pictured right), where the distribution of letters and numbers over the keys is different? As it turns out, you need to use a &lt;a href="http://www.geekberry.net/how-to-dial-a-phone-word-number-from-your-blackberry/"&gt;workaround&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkQ6kGzcatI/AAAAAAAAANE/qtb6LZSPBXo/s1600-h/enterprise_rent-a-car.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 195px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/SkQ6kGzcatI/AAAAAAAAANE/qtb6LZSPBXo/s400/enterprise_rent-a-car.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5351466649199078098" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-9055697568692224820?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/9055697568692224820/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=9055697568692224820&amp;isPopup=true" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/9055697568692224820?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/9055697568692224820?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/VL79-2MWIcM/how-to-dial-phonewords-on-blackberry.html" title="How to dial phonewords on a Blackberry?" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_QD5J-lhOPc0/SkQ8Bt9Bz2I/AAAAAAAAANM/7Ssa7MIV46E/s72-c/phone_blackberry_keyboard.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/how-to-dial-phonewords-on-blackberry.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEEER3s_eip7ImA9WxJWF0s.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-8935756767248217314</id><published>2009-06-23T14:34:00.002+02:00</published><updated>2009-06-23T15:10:06.542+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-23T15:10:06.542+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="non-electronics" /><title>FoodUX: for UX designers that are hungry for more</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.flickr.com/photos/36955640@N07/3404044653/"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://farm4.static.flickr.com/3654/3404044653_d71bcbaf07.jpg?v=0" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;It's good to get inspired by other disciplines once in a while. Here's a combination that I hadn't seen before, but that put a smile on my face when I did: &lt;a href="http://www.foodux.org/"&gt;FoodUX&lt;/a&gt; - gastronomic inspiration for UX designers. As the author puts it: &lt;blockquote&gt;FoodUX is a passion synergy of the creation of memorable culinary experiences and the design for compelling user experiences.&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-8935756767248217314?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/8935756767248217314/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=8935756767248217314&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8935756767248217314?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8935756767248217314?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/iYP8ahhUVZs/foodux-for-ux-designers-that-are-hungry.html" title="FoodUX: for UX designers that are hungry for more" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/foodux-for-ux-designers-that-are-hungry.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C04MSHY7cCp7ImA9WxJWFUs.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2934577896981929466</id><published>2009-06-18T20:16:00.003+02:00</published><updated>2009-06-21T07:26:29.808+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-21T07:26:29.808+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="non-electronics" /><title>When graphic design gets in the way</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.fire-design.fr/epages/270867.sf"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 290px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/SjhaRPn8OkI/AAAAAAAAAMc/KJAC_FNYSxc/s400/Picture+4.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5348123809800796738" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;When I first saw the products pictured above I was not sure what to make of them. You are wondering what you are looking at? They're actually fire extinguishers from &lt;a href="http://www.fire-design.fr/epages/270867.sf"&gt;Fire Design&lt;/a&gt;. However, in case of fire I would like anyone who's around to be able to find the fire extinguisher in the blink of an eye.  And a cool graphic design doesn't exactly help to identify these objects as being fire extinguishers. They might as well be one of those hip 'design' &lt;a href="http://www.sigg.com/uk-shop/index.php/en/design"&gt;SIGG bottles&lt;/a&gt;.&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.sigg.com/uk-shop/index.php/en/design"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 85px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/SjhWPfBIOxI/AAAAAAAAAMU/qvtwz0ZfaAQ/s400/Picture+7.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5348119381526723346" /&gt;&lt;/a&gt;&lt;br /&gt;When someone has to find something quick, it helps if the 'something' is looking like they expect it to. In which case it helps to conform to the norm. And in western countries a bright red fire extinguisher (&lt;a href="http://www.uselog.com/2009/03/finding-fire-extinguisher-cultural.html"&gt;and not blue&lt;/a&gt;) is still the norm. Of course fire extinguishers don't have to be ugly. They can be quite stylish, as Maarten Heijltjes and Sanne Pelgrom demonstrate with their award-winning &lt;a href="http://www.io.tudelft.nl/live/pagina.jsp?id=07d90d6f-9028-491a-9f33-e9a859606138&amp;lang=en"&gt;submission for a design competition&lt;/a&gt; for a new fire extinguisher.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.io.tudelft.nl/live/pagina.jsp?id=07d90d6f-9028-491a-9f33-e9a859606138&amp;lang=en"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 360px;" src="http://www.delta.tudelft.nl/uploads/images/lifestyle_39_14.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;[Fire Design extinguishers via &lt;a href="http://thinkemotions.blogspot.com/2009/06/fire-extinguisherstheyre-not-red.html"&gt;thinkemotions&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-2934577896981929466?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/2934577896981929466/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=2934577896981929466&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2934577896981929466?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2934577896981929466?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/zgtYplE9cQA/when-graphic-design-gets-in-way_18.html" title="When graphic design gets in the way" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_QD5J-lhOPc0/SjhaRPn8OkI/AAAAAAAAAMc/KJAC_FNYSxc/s72-c/Picture+4.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/when-graphic-design-gets-in-way_18.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc-fCp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-6994269294138997573</id><published>2009-06-15T14:35:00.006+02:00</published><updated>2009-06-17T15:54:35.954+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.954+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="consumer electronics" /><title>Bue-ray player installation annoys Wired reviewers</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://akamaipix.crutchfield.com/products/2009/03/305/p305BD4600-f.jpeg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://akamaipix.crutchfield.com/products/2009/03/305/p305BD4600-f.jpeg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;In their &lt;a href="http://www.wired.com/reviews/product/pr_0610_blueray"&gt;review of this wall-mountable Samsung blue-ray player&lt;/a&gt; Wired points out an annoying trend in home entertainment electronics: they're a pain to install and setup properly because of the huge amount of connections and settings. &lt;blockquote&gt;Initial installation proved to be a troubling process of trial-and-error steps to get all the features working properly. Like all entertainment electronics today, the bulk of setup and navigational controls falls to the remote, also encased in a shiny black luster. Basic controls are hidden under the front panel with easy-to-miss, touch-sensitive backlit buttons. Discs are inconveniently slot-loaded on the side.&lt;/blockquote&gt;This product seems to be a matter of valuing 'design' over usability. It's kind of hard to make a 1,5 inch thick blue-ray player and also make it comfortable to plug all the cables into it. And touch-sensitive controls definitely &lt;span style="font-style:italic;"&gt;look&lt;/span&gt; cool, but 'controls' is actually not such a good word for them; LG &lt;a href="http://www.uselog.com/2006/08/lg-chocolate-can-be-sticky-mess-nyt.html"&gt;learned that on the Chocolate&lt;/a&gt;. No wonder AT&amp;T started offering a &lt;a href="http://www.uselog.com/2008/11/at-offers-home-cinema-installation.html"&gt;home cinema installation service&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-6994269294138997573?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/6994269294138997573/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=6994269294138997573&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/6994269294138997573?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/6994269294138997573?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/FXZzsxrSswA/bue-ray-player-installation-annoys.html" title="Bue-ray player installation annoys Wired reviewers" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/bue-ray-player-installation-annoys.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc-fSp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-197176080376898961</id><published>2009-06-12T15:52:00.007+02:00</published><updated>2009-06-17T15:54:35.955+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.955+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mobile phones" /><category scheme="http://www.blogger.com/atom/ns#" term="events" /><title>Apple App Wall: color organized icons to the extreme</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.flickr.com/photos/liquidx/3610318765"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://infosthetics.com/archives/apple_app_wall.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;A while ago I was amazed by having found someone who had arranged her &lt;a href="http://www.uselog.com/2009/04/color-organized-iphone-icons.html"&gt;iPhone icons by color&lt;/a&gt;. Now there is a new version of that - to the extreme. &lt;a href="http://www.techcrunch.com"&gt;TechCrunch&lt;/a&gt; reports that at the Apple &lt;a href="http://developer.apple.com/WWDC/"&gt;WWDC Event&lt;/a&gt;, Apple hooked up a bunch of cinema displays into a &lt;a href="http://www.techcrunch.com/2009/06/08/apples-cool-matrix-style-app-wall/"&gt;Matrix-Style App Wall&lt;/a&gt;. On it are the icons of the more than 50.000 apps in the app store. Each icon will pulsate for a while when someone buys the app. I want one at home.&lt;br /&gt;&lt;br /&gt;&lt;object width="400" height="334"&gt;&lt;param name="movie" value="http://www.youtube.com/v/KiQ62WVvT10&amp;hl=en&amp;fs=1&amp;"&gt;&lt;/param&gt;&lt;param name="allowFullScreen" value="true"&gt;&lt;/param&gt;&lt;param name="allowscriptaccess" value="always"&gt;&lt;/param&gt;&lt;embed src="http://www.youtube.com/v/KiQ62WVvT10&amp;hl=en&amp;fs=1&amp;" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;br /&gt;&lt;br /&gt;[via &lt;a href="http://infosthetics.com/archives/2009/06/apple_matrix-style_app_wall.html"&gt;infosthetics&lt;/a&gt;, photo: &lt;a href="http://www.flickr.com/photos/liquidx/3610318765/"&gt;liquidx&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-197176080376898961?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/197176080376898961/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=197176080376898961&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/197176080376898961?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/197176080376898961?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/RzDSvAhr5nk/apple-app-wall-color-organized-icons-to.html" title="Apple App Wall: color organized icons to the extreme" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/apple-app-wall-color-organized-icons-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc-fip7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-5624927427784465987</id><published>2009-06-11T15:00:00.006+02:00</published><updated>2009-06-17T15:54:35.956+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.956+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mobile phones" /><category scheme="http://www.blogger.com/atom/ns#" term="simplicity" /><title>Doro's super-simple mobile phones</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.cnet.co.uk/i/c/blg/cat/mobiles/doro/3.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand; width: 400px;" src="http://www.cnet.co.uk/i/c/blg/cat/mobiles/doro/3.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Because they are so incredibly charming and ridiculously simple I had to give some love to the Swedish mobile phone maker &lt;a href="http://www.doro.com/global/businessunit/dorocare"&gt;Doro&lt;/a&gt;. They recently &lt;a href="http://www.doro.com/global/businessunit/dorocare/experiencedoro/news/janusaward"&gt;got an iF Gold Award&lt;/a&gt; for outstanding product design for five of their products, among which three mobile phones. CNET &lt;a href="http://crave.cnet.co.uk/mobiles/0,39029453,49294416-1,00.htm"&gt;reviewed two Doro phones&lt;/a&gt; (one of which reminds me a bit of the &lt;a href="http://www.uselog.com/2006/06/easy-5-easy-yes-but-phone_114923535669485638.html"&gt;ITT Easy5&lt;/a&gt;) and &lt;a href="http://mobihealthnews.com/2336/designing-mobiles-for-seniors-lessons-from-doro/"&gt;mobilehealthnews&lt;/a&gt; interviewed Doro's Jerome Arnaud, who made the following interesting statement: &lt;blockquote&gt;Doro aims to help those who are still in the majority of seniors who have not gotten used to mobile technology, are unfamiliar and would never accept it as it exists today. In some cases it’s not a matter of whether they are actually able to use it, but rather if they can connect with the image that the product conveys. Even if, a given 80-year-old could use iPhones, Arnaud argues that it is very likely that person would reject the iPhone simply because of the device’s youth-centric branding.&lt;/blockquote&gt;&lt;span style="font-weight:bold;"&gt;More uselog posts about simple phones:&lt;/span&gt;&lt;br /&gt;&gt; &lt;a href="http://www.uselog.com/2007/04/how-simple-is-vodafone-simply.html"&gt;Simple phones and basic phones&lt;br /&gt;&lt;/a&gt; &gt; &lt;a href="http://www.uselog.com/2005/06/easy-to-use-nokias.html"&gt;Easy to use Nokias&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;[photo: &lt;a href="http://crave.cnet.co.uk/mobiles/0,39029453,49294416-1,00.htm"&gt;CNET&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-5624927427784465987?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/5624927427784465987/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=5624927427784465987&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5624927427784465987?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5624927427784465987?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/27myiobUBjY/doros-super-simple-mobile-phones.html" title="Doro's super-simple mobile phones" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/doros-super-simple-mobile-phones.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc-fyp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-1452530148510593382</id><published>2009-06-09T14:55:00.011+02:00</published><updated>2009-06-17T15:54:35.957+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.957+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><category scheme="http://www.blogger.com/atom/ns#" term="consumer electronics" /><category scheme="http://www.blogger.com/atom/ns#" term="usability research" /><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="guidelines" /><category scheme="http://www.blogger.com/atom/ns#" term="product development" /><title>Consumer electronics have become complex systems</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_QD5J-lhOPc0/Si52k3GdGkI/AAAAAAAAAL8/d3VWfKmvD6U/s1600-h/20060828-NokiaSU.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 303px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/Si52k3GdGkI/AAAAAAAAAL8/d3VWfKmvD6U/s400/20060828-NokiaSU.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5345340183373748802" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;In &lt;a href="http://www.sciencedirect.com/science?_ob=ArticleURL&amp;_udi=B6V1W-4SJ954P-2&amp;_user=3525751&amp;_rdoc=1&amp;_fmt=&amp;_orig=search&amp;_sort=d&amp;view=c&amp;_acct=C000052790&amp;_version=1&amp;_urlVersion=0&amp;_userid=3525751&amp;md5=5132625194151eddea927d953fa2e1d0"&gt;this article&lt;/a&gt; in the &lt;a href="http://www.elsevier.com/wps/find/journaldescription.cws_home/30389/description#description"&gt;Journal of Applied Ergonomics&lt;/a&gt;, entitled '&lt;span style="font-style:italic;"&gt;From telephones to iPhones: Applying systems thinking to networked, interoperable products&lt;/span&gt;' the authors point out that consumer electronics have turned into complex, networked platforms for services, as opposed to the 'as is' stand alone consumer electronics of twenty years ago. Designing these products, they argue, requires a systems thinking design approach. In the insightful, but sometimes a bit fuzzily worded article, the authors use the iPhone as a case study to illustrate their point. Below I've listed a number of trends they identify, emphasizing what I consider the most important ones, and supplemented here and there with my own examples.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Increased complexity&lt;/span&gt;&lt;br /&gt;Current consumer electronics can perform a broad range of tasks. Often a product category, such as mobile phones, may have started out basic (consider the first telephones), but the very presence of this new product triggered people to think about new possible functions for the product, in a process that the authors call coevolution, resulting in what's known as &lt;a href="http://www.uselog.com/2008/03/8-tips-to-manage-feature-creep-blithe.html"&gt;feature creep or blithe&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Product-service combination&lt;/span&gt;&lt;br /&gt;Often consumer electronics are part of a service offering, as in for example the mobile phone, which is an interface to the service your telecom provider offers. As the authors put it:&lt;blockquote&gt;Are some consumer products becoming a bit more like services? Is it the case that ‘‘It’s not what you sell a customer, it's what you do for them. It’s not what something is, it’s what it is connected to, what it does.’’?&lt;/blockquote&gt;&lt;span style="font-weight:bold;"&gt;Networked&lt;/span&gt;&lt;br /&gt;In addition electronic consumer products are becoming more and more networked: your DVD recorder is part of a network with your TV and cable decoder and possible you've even added a home theatre system to that. This - in combination with a sometimes near-criminal lack of standardization in the consumer electronics industry - offers a splendid opportunity for a whole range of new possibilities for system failure, interconnectivity, and usability issues.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;'Connected'&lt;/span&gt;&lt;br /&gt;Now if you have a blue-ray player instead of a DVD-recorder your personal network is in turn &lt;a href="http://www.blu-ray.com/faq/#bluray_connection"&gt;connected to the Internet&lt;/a&gt;. The authors of the article don't explicitly distinguish between 'networked' and 'connected', but I like the distinction between a product being connected to other products in a local network for the purpose of reinforcing or enabling each others functionality, and a product being able to access a communications network (such as the Internet) for the purpose of accessing or communicating information. Interestingly, apart from accessing information and services, connectedness gives product developers the ability to update the product after they have launched it, which is standard practice for software, but pretty new for consumer electronics.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Systems thinking&lt;/span&gt;&lt;br /&gt;These trends suggest you no longer sell people a product that offers a specific functionality. You give people something they can customize according to their needs. There's a shift from - as the authors put it - end products to initial conditions (for product use). However, that makes it kind of hard to predict how people will use your product and how to design it, and that's where systems thinking approach comes in.&lt;blockquote&gt;Systems thinking is ‘‘a framework for conceptualizing or viewing the world’’ (Carvajal, 1983, p. 230). In this regard the  networked, interoperable consumer products that are the topic of this paper are conceptually no different from any large-scale system to which ‘systems thinking’ is normally applied. Although rarely seen in this way, certain types of product can also be seen as '‘a set of interrelated elements’’ (Hall and Fagen, 1956 cited in Carvajal, 1983) and a ‘‘regularly interacting or interdependent group of items forming a uniﬁed whole’’ (Merriam-Webster, 2007).  [...] In a sense the information-age raises the systemic level at which products need to be considered, in other words the designer needs to include more of the world in their design.. &lt;br /&gt;&lt;/blockquote&gt;&lt;span style="font-weight:bold;"&gt;A new framework for human-product interaction&lt;/span&gt;&lt;br /&gt;As a consequence, when looking at human-product interaction frameworks (which indicate what components make up the interaction and how they are related) we should not only consider the interaction between the individual user and his/her product, but also the interaction with other products and other people, as I outlined in &lt;a href="http://www.uselog.com/2009/03/representative-usage-in-user-testing.html"&gt;this earlier post&lt;/a&gt; and this article on &lt;a href="http://www.informaworld.com/smpp/content~content=a794528509~db=all~jumptype=rss"&gt;user-centred design for sustainable behavior&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_QD5J-lhOPc0/SfAeO5AfusI/AAAAAAAAAJg/s26OYaVVRIU/s400/Human-Product_interaction_van_Kuijk.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 248px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/SfAeO5AfusI/AAAAAAAAAJg/s26OYaVVRIU/s400/Human-Product_interaction_van_Kuijk.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Reference&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;Walker, G., Stanton, N., Jenkins, D., Salmon, P., March 2009. From telephones to iphones: Applying systems thinking to networked, interoperable products. Applied Ergonomics 40 (2), 206-215.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-1452530148510593382?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/1452530148510593382/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=1452530148510593382&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1452530148510593382?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1452530148510593382?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/sMcbuic1a6k/consumer-electronics-have-become.html" title="Consumer electronics have become complex systems" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_QD5J-lhOPc0/Si52k3GdGkI/AAAAAAAAAL8/d3VWfKmvD6U/s72-c/20060828-NokiaSU.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/consumer-electronics-have-become.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQNQXY-eyp7ImA9WxJWGEg.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-8603946661239012363</id><published>2009-06-04T14:03:00.004+02:00</published><updated>2009-06-24T17:29:50.853+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-24T17:29:50.853+02:00</app:edited><title>New uselog shirts (and now shipping worldwide)</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://shirts.uselog.com"&gt;&lt;img style=" align:center; cursor:pointer; cursor:hand;width: 320px; height: 319px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/SibKZGF73sI/AAAAAAAAALs/2jU95ND-s18/s320/Picture+32.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5343180540402720450" /&gt;&lt;/a&gt;&lt;br /&gt;I've added a number of new designs to the &lt;A HREF="http://uselog.oli.tudelft.nl/uselog-design/shirtsredirect.html"&gt;uselog shirtshop&lt;/a&gt;. And because it seems a bit silly for an Internet shop only to ship within the EU, in addition to the original shop, I've now added a second shop that ships worldwide: &lt;a href="http://uselog.spreadshirt.com"&gt;uselog shirts | worldwide&lt;/a&gt;. This may cause some confusion, but for EU citizens it's cheaper to order in the EU shop, that's why I'm keeping the original shop online.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-8603946661239012363?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/8603946661239012363/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=8603946661239012363&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8603946661239012363?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8603946661239012363?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/w4tF5RqK2Bw/new-uselog-shirts-and-now-shipping.html" title="New uselog shirts (and now shipping worldwide)" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_QD5J-lhOPc0/SibKZGF73sI/AAAAAAAAALs/2jU95ND-s18/s72-c/Picture+32.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/new-uselog-shirts-and-now-shipping.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc-cCp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-8293594966361412238</id><published>2009-06-02T15:37:00.010+02:00</published><updated>2009-06-17T15:54:35.958+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.958+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="business and usability" /><category scheme="http://www.blogger.com/atom/ns#" term="consumer electronics" /><category scheme="http://www.blogger.com/atom/ns#" term="computers/software" /><category scheme="http://www.blogger.com/atom/ns#" term="product development" /><title>The Flip and Apple got it right by failing.</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.techcrunch.com/2009/03/19/flip-video-wrong-wrong-wrong-and-then-so-so-right/"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; " src="http://cache0.techcrunch.com/wp-content/uploads/2009/03/pda.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;What do Apple and Pure Digital (the maker of the &lt;a href="http://www.uselog.com/2008/07/flip-video-doesnt-come-any-easier.html"&gt;Flip Video camera&lt;/a&gt;) have in common? They both have products on the market renowned for their usability, partly due to a focus on the essentials. But they share something else: failure. Big time failure. TechCrunch takes a look at the &lt;a href="http://www.techcrunch.com/2009/03/19/flip-video-wrong-wrong-wrong-and-then-so-so-right/"&gt;predecessors of the Flip&lt;/a&gt; and concludes that:&lt;blockquote&gt;Pure Digital wasn’t always selling hit products - it took seven years for the company to get it right. In the meantime, they launched products that just weren’t quite the right thing at the right time.&lt;/blockquote&gt;And while Apple is by now considered the pinnacle of product innovation, design and usability, the company has had it's fair share of failed products, that by now journalists are of course very willing to highlight (&lt;a href="http://www.forbes.com/2008/10/29/apple-product-flops-tech-personal-cx_ag_1030apple.html"&gt;Forbes&lt;/a&gt;, &lt;a href="http://www.wired.com/gadgets/mac/multimedia/2008/01/gallery_apple_flops"&gt;Wired&lt;/a&gt;, &lt;a href="http://www.maclife.com/article/top_10_apple_flops"&gt;MacLife&lt;/a&gt;). But appropriately, the Wired article is entitled 'Learning From Failure', because the question arises whether the iPhone would have been the iPhone if it had not been preceded by the &lt;a href="http://www.forbes.com/2008/10/29/apple-product-flops-tech-personal-cx_ag_1030apple_slide_5.html?thisSpeed=15000"&gt;Apple Newton&lt;/a&gt; and the &lt;a href="http://www.forbes.com/2008/10/29/apple-product-flops-tech-personal-cx_ag_1030apple_slide_9.html?thisSpeed=15000"&gt;Motorola ROKR&lt;/a&gt;. Then again, Apple's still struggling with &lt;a href="http://www.wired.com/gadgetlab/2009/02/what-we-need-in/"&gt;AppleTV&lt;/a&gt;, and that was preceded by &lt;a href="http://www.wired.com/gadgets/mac/multimedia/2008/01/gallery_apple_flops?slide=4&amp;slideView=2"&gt;Macintosh TV&lt;/a&gt;. So I guess that failing doesn't offer any guarantees either.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-8293594966361412238?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/8293594966361412238/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=8293594966361412238&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8293594966361412238?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8293594966361412238?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/W0irn82Urpk/want-to-get-it-right-dare-to-fail.html" title="The Flip and Apple got it right by failing." /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/want-to-get-it-right-dare-to-fail.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc-cSp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-914719835863228732</id><published>2009-05-29T18:09:00.009+02:00</published><updated>2009-06-17T15:54:35.959+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.959+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="events" /><title>Friday afternoon lead: ZINK design competition</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.zink.com/ZeroBoundaries"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; " src="http://www.zink.com/files/images/DESIGNCHALLENGE.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;For those of you who don't have any plans for the weekend: &lt;a href="http://www.zink.com/"&gt;ZINK&lt;/a&gt; (ZeroInk), the company that provides the technology for the &lt;a href="http://www.polaroid.com/pogo/nl/"&gt;new generation of Polaroid cameras&lt;/a&gt;,  (picture below) has a design challenge for you. The &lt;a href="http://www.zink.com/ZeroBoundaries"&gt;ZINK zero boundaries&lt;/a&gt; competition challenges you to design and imagine "&lt;span style="font-style:italic;"&gt;new and innovative solutions that enable and enhance printing with ZINK Technology&lt;/span&gt;". They would like you to "&lt;span style="font-style:italic;"&gt;re-imagine printing and its role in the digital world using the ZINK Technology to fuel the future possibilities of this unique technology platform&lt;/span&gt;". &lt;br /&gt;&lt;br /&gt;Quite an impressive &lt;a href="http://www.zink.com/judges"&gt;jury&lt;/a&gt; by the way, with people from for example Frog Design, Gizmodo, and Harvard Business School. A (relatively) cheap and fun way for ZINK to get inspired, a good way for you to get noticed (if you want to). Deadline is monday June 8.&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://zedomax.com/blog/wp-content/uploads/2008/05/polaroid-gogo-2.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 500px; height: 351px;" src="http://zedomax.com/blog/wp-content/uploads/2008/05/polaroid-gogo-2.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-914719835863228732?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/914719835863228732/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=914719835863228732&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/914719835863228732?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/914719835863228732?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/wbxcgS-vAyc/friday-afternoon-lead-zink-design.html" title="Friday afternoon lead: ZINK design competition" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/friday-afternoon-lead-zink-design.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc-cSp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-3335381015139836830</id><published>2009-05-28T13:30:00.001+02:00</published><updated>2009-06-17T15:54:35.959+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.959+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="home appliances" /><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><category scheme="http://www.blogger.com/atom/ns#" term="computers/software" /><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="guidelines" /><category scheme="http://www.blogger.com/atom/ns#" term="non-electronics" /><title>Checklists and water taps for usability in design</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://malcolmcoles.co.uk/blog/wp-content/uploads/2009/04/massive-sign.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; " src="http://malcolmcoles.co.uk/blog/wp-content/uploads/2009/04/massive-sign.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;Check out this useful overview of &lt;a href="http://bestwebdesignschools.com/2009/usabilityedu-25-incredibly-useful-usability-cheat-sheets-checklists/"&gt;usability cheat-sheets&lt;/a&gt; from Designer City, USA. And while you're in a learning mood, you might want to look at these &lt;a href="http://www.malcolmcoles.co.uk/blog/usability-taps-lessons-web-design/#comments"&gt;lessons for webdesign from water taps&lt;/a&gt;. Yes, you read it right, water taps, fountains. For example the lesson learned from the picture above was: &lt;span style="font-style:italic;"&gt;If you need massive instructions, you've cocked it up.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-3335381015139836830?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/3335381015139836830/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=3335381015139836830&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3335381015139836830?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3335381015139836830?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/7gWu0tL5TiM/checklists-and-water-taps-for-usability_28.html" title="Checklists and water taps for usability in design" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/checklists-and-water-taps-for-usability_28.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc9eCp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-7444344181725610169</id><published>2009-05-25T03:16:00.002+02:00</published><updated>2009-06-17T15:54:35.960+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.960+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mobile phones" /><category scheme="http://www.blogger.com/atom/ns#" term="consumer electronics" /><category scheme="http://www.blogger.com/atom/ns#" term="user behaviour" /><category scheme="http://www.blogger.com/atom/ns#" term="product impact" /><title>What the iPhone can do to dinner with friends</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.flickr.com/photos/garrettmurray/1730083803/"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px;" src="http://farm3.static.flickr.com/2018/1730083803_5d1677f069_b.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;A friend of mine was recently a bit insulted/disappointed when she started telling what she thought to be an engaging story to a group of friends, and one of them zoned out and pulled out his iPhone. When catching her raised eyebrow he said: "I already know this story." Having dinner with friends is not quite the same if everyone brings (and uses) their iPhone at the table. Found &lt;a href="http://www.flickr.com/photos/garrettmurray/1730083803/"&gt;this picture&lt;/a&gt; (entitled iPhone insanity) with the following hilarious description on flickr:&lt;blockquote&gt;Kevin, Keith and Nick using their iPhones, while PJ watches a movie on Brian's iPhone. And I took this with an iPhone. Ridiculous. &lt;/blockquote&gt;Always having e-mail, phone, photos, movies and news at your fingertips does seem to stimulate &lt;a href="http://www.uselog.com/2008/07/continuous-partial-attention-versus.html?widgetType=BlogArchive&amp;widgetId=BlogArchive1&amp;action=toggle&amp;dir=close&amp;toggle=YEARLY-1199142000000&amp;toggleopen=MONTHLY-1220220000000"&gt;continuous partial attention&lt;/a&gt;. And sometimes I find it a little rude (guilty myself as well!). Or maybe it's just that the times are a-changing.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;UPDATE:&lt;/span&gt;&lt;br /&gt;New York Times article on texting and dinner etiquette: &lt;a href="http://www.nytimes.com/2009/05/27/dining/27text.html?_r=1"&gt;Play With Your Food, Just Don’t Text!&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-7444344181725610169?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/7444344181725610169/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=7444344181725610169&amp;isPopup=true" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7444344181725610169?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7444344181725610169?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/0Xi1kbdsOAo/what-iphone-can-do-to-dinner-with_25.html" title="What the iPhone can do to dinner with friends" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">5</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/what-iphone-can-do-to-dinner-with_25.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc9eSp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2653090874626971950</id><published>2009-05-25T01:03:00.010+02:00</published><updated>2009-06-17T15:54:35.961+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.961+02:00</app:edited><title>Follow uselog on Twitter</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://twitter.com/uselog"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 64px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/ShnaqqZlicI/AAAAAAAAALk/e7h3YPccoqA/s320/twitter-uselog.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5339539259695401410" /&gt;&lt;/a&gt;For your convenience I have added a &lt;a href="http://twitter.com/uselog"&gt;Twitter-feed&lt;/a&gt; to the possibilities of staying up to date on uselog posts, in addition to the &lt;a href="http://feeds.feedburner.com/uselog"&gt;rss-feed&lt;/a&gt; and &lt;a href="http://www.feedblitz.com/f/?Sub=64533"&gt;e-mail updates&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-2653090874626971950?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/2653090874626971950/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=2653090874626971950&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2653090874626971950?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2653090874626971950?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/GlxFaLNnjoU/follow-uselog-on-twitter.html" title="Follow uselog on Twitter" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_QD5J-lhOPc0/ShnaqqZlicI/AAAAAAAAALk/e7h3YPccoqA/s72-c/twitter-uselog.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/follow-uselog-on-twitter.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc9eip7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2681872593496407304</id><published>2009-05-20T04:50:00.003+02:00</published><updated>2009-06-17T15:54:35.962+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.962+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><category scheme="http://www.blogger.com/atom/ns#" term="usability research" /><category scheme="http://www.blogger.com/atom/ns#" term="events" /><category scheme="http://www.blogger.com/atom/ns#" term="design research" /><category scheme="http://www.blogger.com/atom/ns#" term="user research" /><title>Contextmapping symposium videos online</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://collegerama.tudelft.nl/mediasite/Catalog/pages/catalog.aspx?catalogId=280c51cd-1264-4289-af39-b110d78815c9"&gt;&lt;img style="display:block; margin:0px auto 0px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 211px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/ShS8WVLvUmI/AAAAAAAAALM/rmrVzvfTZzE/s400/DSC_0208-reduced.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5338098550170407522" /&gt;&lt;/a&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://collegerama.tudelft.nl/mediasite/Catalog/pages/catalog.aspx?catalogId=280c51cd-1264-4289-af39-b110d78815c9"&gt;&lt;img style="display:block; margin:0px auto 0px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 96px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/ShS4rIz6xLI/AAAAAAAAAKk/yOz9LsKAziU/s400/May13bannerlong500b.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5338094509580010674" /&gt;&lt;/a&gt;&lt;br /&gt;If you were not one of the 150 designers and design researchers from industry or 200 students and academics who attended the contextmapping symposium &lt;a href="http://studiolab.io.tudelft.nl/contextmapping/symposium"&gt;Designing for, with, and from User Experiences&lt;/a&gt;, but you had actually wanted to, this is your chance. The presentations, by Liz Sanders, Jacob Buur, and Froukje Sleeswijk Visser can now be &lt;a href="http://collegerama.tudelft.nl/mediasite/Catalog/pages/catalog.aspx?catalogId=280c51cd-1264-4289-af39-b110d78815c9"&gt;viewed online&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Contextmapping?&lt;/span&gt;&lt;br /&gt;Under the flag of '&lt;a href="http://studiolab.io.tudelft.nl/contextmapping"&gt;contextmapping&lt;/a&gt;', the &lt;a href="http://www.studiolab.nl/stappers/research"&gt;tools and techniques group&lt;/a&gt; at &lt;a href="http://www.ide.tudelft.nl"&gt;IDE/TU Delft&lt;/a&gt; has been exploring designerly techniques of user/context research, in close collaboration with education (600 students) and industries in the Netherlands and across Europe. The symposium took place after five years of this program, on the occasion of the PhD defense of Froukje Sleeswijk Visser, on communicating user experiences to design teams (pdf of &lt;a href="http://studiolab.io.tudelft.nl/static/gems/sleeswijkvisser/sleeswijkthesis.pdf"&gt;thesis&lt;/a&gt; and &lt;a href="http://www.studiolab.nl/sleeswijkvisser/publications"&gt;other publications&lt;/a&gt;).&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.maketools.com"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 100px; height: 100px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/ShS5AYpwV7I/AAAAAAAAAKs/6BljsCDXrag/s200/2liz.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5338094874609604530" /&gt;&lt;/a&gt;&lt;a href="http://www.maketools.com/"&gt;Liz Sanders&lt;/a&gt;, of MakeTools, talked about large-scale co-creation she has been doing with architectural firm NBBJ, discussing the difficulties in bringing these processes in architecture. Besides giving an impression of the sheer size of the projects (building whole hospitals), and the complexity of developing user-centered design insights, she discusses the tools and techniques that have been used to bring the user experience into building processes.&lt;br /&gt;&lt;a href="http://collegerama.tudelft.nl/mediasite/Viewer/?peid=35a0ffdf188342f7a7b39c0e212d531d"&gt;&gt; see video&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" hfref="http://www1.sdu.dk/Nat/MCI/m/GenInfo/People/BuurJ.htm"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 100px; height: 100px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/ShS5aNXEghI/AAAAAAAAAK0/MgqpVIX22C0/s200/3jacob.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5338095318255043090" /&gt;&lt;/a&gt;&lt;a href="http://www1.sdu.dk/Nat/MCI/m/GenInfo/People/BuurJ.htm"&gt;Jacob Buur&lt;/a&gt;, of the University of Southern Denmark, discussed his experiences in applying ethnographic provocation in companies, and showed examples how video as a co-creation tool can be used to bring out misunderstandings in design communication.&lt;br /&gt;&lt;a href="http://collegerama.tudelft.nl/mediasite/Viewer/?peid=2be0852f0b254d74a7568908cfdfa77b"&gt;&gt; see video&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://studiolab.io.tudelft.nl/sleeswijkvisser"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 100px; height: 100px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/ShS5oJKy9nI/AAAAAAAAAK8/oVkJbVSpUUQ/s200/4froukje.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5338095557647988338" /&gt;&lt;/a&gt;&lt;a href="http://studiolab.io.tudelft.nl/sleeswijkvisser"&gt;Froukje Sleeswijk Visser&lt;/a&gt; introduced the education program at Delft, and led a series of 10 graduates who related their experience in applying contextmapping, co-creation and other user-centered design processes during and after their studies. These 10 presentations in pechakucha style give an impression of the diversity of companies trying out these techniques, and of the changing Zeitgeist, ranging from the first graduate finding a non-receptive market to several recent graduates who set up their own design research consultancies.&lt;br /&gt;&lt;a href="http://collegerama.tudelft.nl/mediasite/Viewer/?peid=6fd81deac6224e37aed1a5a83e2ff6bf"&gt;&gt; see video&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/ShNovDCxxuI/AAAAAAAAAKU/66Qkkc0fNo0/s1600-h/2.+Shoes+awareness.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 256px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/ShNovDCxxuI/AAAAAAAAAKU/66Qkkc0fNo0/s400/2.+Shoes+awareness.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5337725140844267234" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-2681872593496407304?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/2681872593496407304/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=2681872593496407304&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2681872593496407304?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2681872593496407304?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/TDHGO6ITZqM/online-videos-of-presentations-on.html" title="Contextmapping symposium videos online" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_QD5J-lhOPc0/ShS8WVLvUmI/AAAAAAAAALM/rmrVzvfTZzE/s72-c/DSC_0208-reduced.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/online-videos-of-presentations-on.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc9eip7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-4847953651471921410</id><published>2009-05-18T16:46:00.007+02:00</published><updated>2009-06-17T15:54:35.962+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.962+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="user research" /><category scheme="http://www.blogger.com/atom/ns#" term="usability studies" /><title>How to kill a good idea: the focus group approach</title><content type="html">&lt;object width="400" height="323"&gt;&lt;param name="movie" value="http://www.youtube.com/v/OORnMYoWX9c&amp;hl=nl&amp;fs=1&amp;rel=0"&gt;&lt;/param&gt;&lt;param name="allowFullScreen" value="true"&gt;&lt;/param&gt;&lt;param name="allowscriptaccess" value="always"&gt;&lt;/param&gt;&lt;embed src="http://www.youtube.com/v/OORnMYoWX9c&amp;hl=nl&amp;fs=1&amp;rel=0" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;br /&gt;As a follow up to the previous post, on the danger of &lt;a href="http://www.uselog.com/2009/05/danger-of-usability-evaluation.html"&gt;killing good ideas by usability evaluation&lt;/a&gt;, a second option: killing good a good idea by having a focus group. The video actually beautifully illustrates another notion from the previously mentioned &lt;a href="http://portal.acm.org/citation.cfm?id=1357054.1357074"&gt;Greenberg/Buxton paper&lt;/a&gt;: that today's consumers/users may find it hard to evaluate tomorrow's products. Remember the &lt;a href="http://www.uselog.com/2007/11/sony-walkman-history.html"&gt;Walkman legend&lt;/a&gt;?&lt;br /&gt;&lt;br /&gt;[&lt;span style="font-style:italic;"&gt;Thanks to &lt;a href="http://www.floriswiegerinck.nl/"&gt;Floris&lt;/a&gt; for the tip&lt;/span&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-4847953651471921410?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/4847953651471921410/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=4847953651471921410&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/4847953651471921410?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/4847953651471921410?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/iZABJPShCxE/how-to-kill-good-idea-focus-group.html" title="How to kill a good idea: the focus group approach" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/how-to-kill-good-idea-focus-group.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc9eyp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-1192032217150709163</id><published>2009-05-15T15:48:00.011+02:00</published><updated>2009-06-17T15:54:35.963+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.963+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><category scheme="http://www.blogger.com/atom/ns#" term="usability research" /><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="usability studies" /><title>The danger of usability evaluation</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://web.mit.edu/6.933/www/Fall2000/teradyne/susdir2.JPG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 301px;" src="http://web.mit.edu/6.933/www/Fall2000/teradyne/susdir2.JPG" border="0" alt="" /&gt;&lt;/a&gt;If there's one thing we know that's beneficial for making good products it's usability evaluation, right? So - being the usability zealot that I am - I felt an immediate urge of disagreement hitting me when I saw the title of the &lt;a href="http://www.chi2008.org/"&gt;CHI2008&lt;/a&gt; paper &lt;a href="http://portal.acm.org/citation.cfm?id=1357054.1357074"&gt;Usability Evaluation Considered Harmful (Some of the Time)&lt;/a&gt;* (&lt;a href="http://grouplab.cpsc.ucalgary.ca/grouplab/uploads/Publications/Publications/2008-UsabilityHarmful.CHI.pdf"&gt;pdf&lt;/a&gt;) by &lt;a href="http://pages.cpsc.ucalgary.ca/~saul/wiki/pmwiki.php"&gt;Saul Greenberg&lt;/a&gt; and &lt;a href="http://www.billbuxton.com/"&gt;Bill Buxton&lt;/a&gt;. But fortunately I did read the article and discovered Greenberg and Buxton lay out a very compelling argument against usability evaluation being misused as the standard method to evaluate any design, including innovative, conceptually new user interfaces.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Formative versus summative testing&lt;/span&gt;&lt;br /&gt;The gist of it is that there's no use in comparing the usability of an immature tangible interaction concept (say, the &lt;a href="http://alumni.media.mit.edu/~andyd/folio/wobble.html"&gt;Wobble Lamp&lt;/a&gt;) against an element of a mature on-screen user interface (e.g., Windows 98). It's the &lt;a href="http://www.businessweek.com/chapter/christensen.htm"&gt;innovator's dilemma&lt;/a&gt;: you might dismiss a new technology or concept because it doesn't perform sufficiently, but it only underperforms because it is immature; the potential of the immature might be much bigger than that of the existing (see illustration above). You want to know and show what's good about your design, its potential, and what can be improved to reach it. And that is not something that only performing a usability evaluation will give you an answer to.&lt;br /&gt;&lt;blockquote&gt;&lt;span style="font-weight:bold;"&gt;Abstract&lt;/span&gt;&lt;br /&gt;Current practice in Human Computer Interaction as encouraged by educational institutes, academic review processes, and institutions with usability groups advocate usability evaluation as a critical part of every design process. This is for good reason: usability evaluation has a significant role to play when conditions warrant it. Yet evaluation can be ineffective and even harmful if naively done ‘by rule’ rather than ‘by thought’. If done during early stage design, it can mute creative ideas that do not conform to current interface norms. If done to test radical innovations, the many interface issues that would likely arise from an immature technology can quash what could have been an inspired vision. If done to validate an academic prototype, it may incorrectly suggest a design’s scientific worthiness rather than offer a meaningful critique of how it would be adopted and used in everyday practice.  If done without regard to how cultures adopt technology over time, then today’s reluctant reactions by users will forestall tomorrow’s eager acceptance. The choice of evaluation methodology – if any – must arise from and be appropriate for the actual problem or research question under consideration.&lt;/blockquote&gt;&lt;span style="font-weight:bold;"&gt;Alternative methods&lt;/span&gt;&lt;br /&gt;As alternatives to usability evaluation the authors suggest &lt;a href="http://en.wikipedia.org/wiki/Design_Rationale"&gt;design rationale&lt;/a&gt;, &lt;a href="http://www.usabilitynet.org/tools/scenarios.htm"&gt;scenarios of use&lt;/a&gt;, &lt;a href="http://en.wikipedia.org/wiki/Case_study"&gt;case studies&lt;/a&gt;, and participatory critiques. I would add &lt;a href="http://portal.acm.org/citation.cfm?id=1247660.1247670"&gt;user experience sampling&lt;/a&gt;, &lt;a href="http://www.socialresearchmethods.net/tutorial/Brown/lauratp.htm"&gt;observational research&lt;/a&gt;, and &lt;a href="http://edis.ifas.ufl.edu/FY393"&gt;in-depth interviews&lt;/a&gt; to that. Greenberg and Buxton do a very good job at pointing out that the evaluation of innovative interaction concepts should be &lt;a href="http://www.cs.bgsu.edu/maner/domains/Formeval.htm"&gt;formative&lt;/a&gt;, not &lt;a href="http://www.devicelink.com/mddi/archive/07/10/003.html"&gt;summative&lt;/a&gt;, and that usability is just one of the product properties to evaluate a product by.&lt;br /&gt;&lt;br /&gt;Read the paper: it's a mind-changer. &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;See also&lt;/span&gt;&lt;br /&gt;&gt; &lt;a href="http://www.slideshare.net/saul.greenberg/usability-evaluation-considered-harmful-some-of-the-time"&gt;Greenberg's slideshare set of the CHI presentation of the article&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Reference&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;*Greenberg, S. and Buxton, B. 2008. Usability evaluation considered harmful (some of the time). In Proceeding of the Twenty-Sixth Annual SIGCHI Conference on Human Factors in Computing Systems (Florence, Italy, April 05 - 10, 2008). CHI '08. ACM, New York, NY, 111-120.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;[Illustration: &lt;a href="http://web.mit.edu/6.933/www/Fall2000/teradyne/clay.html"&gt;MIT Aurora project&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-1192032217150709163?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/1192032217150709163/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=1192032217150709163&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1192032217150709163?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1192032217150709163?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/pN4ZviTzHp0/danger-of-usability-evaluation.html" title="The danger of usability evaluation" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/danger-of-usability-evaluation.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc9fCp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-5964638388660427779</id><published>2009-05-11T18:15:00.008+02:00</published><updated>2009-06-17T15:54:35.964+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.964+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><title>The many definitions of human factors and ergonomics</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/SghSMrWm-QI/AAAAAAAAAKA/y5U30N6BOmY/s1600-h/Human+Factors.png"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 239px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/SghSMrWm-QI/AAAAAAAAAKA/y5U30N6BOmY/s400/Human+Factors.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5334604136369813762" /&gt;&lt;/a&gt;So, what is human factors (or ergonomics)? You would have thought that a domain that busies itself with creating a fit between people and their tools and surroundings would have chosen a name that fits people's knowledge and preconceptions. But alas. So often human factors professionals find themselves explaining what human factors is. People who call themselves ergonomists have the added difficulty that people find the name hard to pronounce, or &lt;a href="http://www.uselog.com/2007/06/west-wing-on-ergonomics.html"&gt;plain silly&lt;/a&gt;. Oddly enough, you hardly ever see business people having to explain what 'business' is (up until recently at least). In addition to that, as any self-respecting profession, human factors and ergonomics professionals are self-obsessed and feel a need to define themselves.&lt;br /&gt;&lt;br /&gt;Those might be some causes for the interesting array of &lt;a href="http://www.thehumanfactorblog.com/2009/03/16/the-many-definitions-of-human-factors-and-ergonomics/"&gt;definitions of human factors and ergonomics&lt;/a&gt; that Eric Shaver of the &lt;a href="http://www.thehumanfactorblog.com/"&gt;Human Factors Blog&lt;/a&gt; found in literature. He provides a good overview (including literature references), and, ironically, adds a definition of his own.&lt;br /&gt;&lt;br /&gt;By the way, my favorite &lt;span style="font-style:italic;"&gt;let's-look-up-this-word tool&lt;/span&gt; (&lt;a href="www.visualthesaurus.com"&gt;visualthesaurus&lt;/a&gt;) did not know what human factors is (see image above), but it does know ergonomics. As usual, wikipedia knows them both: &lt;a href="http://en.wikipedia.org/wiki/Human_factors"&gt;human factors&lt;/a&gt;, &lt;a href="http://en.wikipedia.org/wiki/Ergonomics"&gt;ergonomics&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-5964638388660427779?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/5964638388660427779/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=5964638388660427779&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5964638388660427779?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5964638388660427779?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/PATCXmiEbJw/many-definitions-of-human-factors-and.html" title="The many definitions of human factors and ergonomics" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_QD5J-lhOPc0/SghSMrWm-QI/AAAAAAAAAKA/y5U30N6BOmY/s72-c/Human+Factors.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/many-definitions-of-human-factors-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8DRHc9fCp7ImA9WxJWEkk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2551155219617754903</id><published>2009-05-07T14:21:00.006+02:00</published><updated>2009-06-17T15:54:35.964+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-17T15:54:35.964+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mobile phones" /><title>Top 10 of lamest mobile phones</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.pcworld.com/article/163922/dirty_dozen_ugliest_and_lamest_cell_phones.html"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; " src="http://images.pcworld.com/news/graphics/163922-slide-00_introslide_slide.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;If someone is out and about trashing mobile phone designs I can't resist, I just have to read. And in this case justifiably so, because it's plain fun: PC world reviews the &lt;a href="http://www.pcworld.com/article/163922/dirty_dozen_ugliest_and_lamest_cell_phones.html"&gt;10 ugliest and lamest mobile phones&lt;/a&gt;. Of course usability plays a role in some of the reviews, as for example for Nokia's lipstick-like &lt;a href="http://www.pcworld.com/article/163922-5/dirty_dozen_ugliest_and_lamest_cell_phones.html"&gt;7380&lt;/a&gt;.&lt;blockquote&gt;If you owned the Nokia 7380 and had to send a quick text message to save your life, you’d be dead by now. This handset, which looks like a fancy pencil box, has to go down as one of the most unusable phones ever made. Critics commented that the only thing you could do fast with this phone is answer an incoming call.&lt;/blockquote&gt;You've got to admit that it takes guts though: removing almost all controls from a phone. About almost as gutsy as placing the controls over the screen so that your hand blocks the screen while operating the phone, as on the &lt;a href="http://www.pcworld.com/article/163922-10/dirty_dozen_ugliest_and_lamest_cell_phones.html"&gt;B&amp;O Serenata&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;[Picture from &lt;a href="http://www.pcworld.com/article/163922/dirty_dozen_ugliest_and_lamest_cell_phones.html"&gt;PC World&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-2551155219617754903?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/2551155219617754903/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=2551155219617754903&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2551155219617754903?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2551155219617754903?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/rFXIQZEpTGE/top-10-of-lamest-mobile-phones.html" title="Top 10 of lamest mobile phones" /><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:extendedProperty name="OpenSocialUserId" value="03737889052026384670" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://www.uselog.com/2009/05/top-10-of-lamest-mobile-phones.html</feedburner:origLink></entry></feed>
