<?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;C0EGRH46fyp7ImA9WxNbEU0.&quot;"><id>tag:blogger.com,1999:blog-9968619</id><updated>2009-11-13T09:40:25.017+01: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="hub" href="http://pubsubhubbub.appspot.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>434</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><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;DUQMRXY5cSp7ImA9WxNUGEo.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-5911644901243065812</id><published>2009-11-10T13:42:00.008+01:00</published><updated>2009-11-10T19:23:04.829+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-10T19:23:04.829+01:00</app:edited><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="events" /><title>Live webcast of Design for Usability Symposium</title><content type="html">&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/Svln5tChl-I/AAAAAAAAASs/vY38hz0ClQk/s1600-h/DfUwebcast+logo.gif"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 300px; " src="http://3.bp.blogspot.com/_QD5J-lhOPc0/Svln5tChl-I/AAAAAAAAASs/vY38hz0ClQk/s400/DfUwebcast+logo.gif" border="0" alt="" id="BLOGGER_PHOTO_ID_5402463469048010722" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The &lt;a href="http://www.designforusability.org/symposium"&gt;Design for Usability Symposium&lt;/a&gt; of November 12 will be &lt;a href="http://collegerama.tudelft.nl/mediasite/Viewer/?peid=7d0ec5e257d74d6cb15d7c0fab460a1c"&gt;viewable via a live webcast&lt;/a&gt;. It will remain online afterwards as well. The symposium starts at 9:30 am &lt;a href="http://www.timeanddate.com/worldclock/city.html?n=16"&gt;CET&lt;/a&gt; (GMT+1).&lt;br /&gt;&lt;br /&gt;Your chance to see &lt;a href="http://www.designforusability.org/symposium/lectures"&gt;inspiring presentations&lt;/a&gt; by Gerrit van der Veer (President of &lt;a href="http://www.sigchi.org/"&gt;ACM SIGCHI&lt;/a&gt;), Cees van Dok (&lt;a href="http://www.frogdesign.com/contact/amsterdam.html"&gt;frog design Europe&lt;/a&gt;), Abbie Vanhoutte and Robert Eijlander (&lt;a href="http://www.oce.com/"&gt;Océ&lt;/a&gt;) and &lt;a href="http://www.studiolab.io.tudelft.nl/vankuijk"&gt;yours truly&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The symposium is fully booked, though you can still sign up and try your luck on the standby list or watch the webcast in an adjoining room if everyone does show up.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-5911644901243065812?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/5911644901243065812/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=5911644901243065812&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5911644901243065812?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/5911644901243065812?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/qLHE3R-AE1U/live-webcast-of-design-for-usability.html" title="Live webcast of Design for Usability Symposium" /><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/Svln5tChl-I/AAAAAAAAASs/vY38hz0ClQk/s72-c/DfUwebcast+logo.gif" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://www.uselog.com/2009/11/live-webcast-of-design-for-usability.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0IERH07cCp7ImA9WxNUEko.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-8848597438033275143</id><published>2009-11-03T20:52:00.000+01:00</published><updated>2009-11-03T21:18:25.308+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-03T21:18:25.308+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mobile phones" /><category scheme="http://www.blogger.com/atom/ns#" term="computers/software" /><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><title>Comparing iPhone and Android application management</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.lukew.com/ff/entry.asp?930"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 283px; height: 213px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/SvCJdU71_DI/AAAAAAAAAR0/bVDjEyiH2DI/s400/iphone-android.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5399967090146147378" /&gt;&lt;/a&gt;&lt;div&gt;An intriguing &lt;a href="http://www.lukew.com/ff/entry.asp?930"&gt;comparison of the iPhone and Android&lt;/a&gt; UI paradigm for application access and management,  by Luke Wroblewski. In the end, the within-product consistency that the iPhone offers seems to nudge him to a judgement somewhat in favor of the iPhone.&lt;/div&gt;&lt;div&gt;&lt;blockquote&gt;I can’t help but wonder if the singular model Apple employs makes managing a set of mobile applications easier. Every app is accessed the same way and only open apps are running. Sure this is limiting in some ways (customization options, background processes) but empowering in others (clarity, control) at the same time.&lt;/blockquote&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-8848597438033275143?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/8848597438033275143/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=8848597438033275143&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8848597438033275143?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8848597438033275143?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/AG9UX4hG9ec/comparing-iphone-and-android.html" title="Comparing iPhone and Android application management" /><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/SvCJdU71_DI/AAAAAAAAAR0/bVDjEyiH2DI/s72-c/iphone-android.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/11/comparing-iphone-and-android.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQDRn45eCp7ImA9WxNVGUw.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-9103957373738604940</id><published>2009-10-30T08:27:00.013+01:00</published><updated>2009-10-30T14:46:17.020+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-30T14:46:17.020+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="business and usability" /><category scheme="http://www.blogger.com/atom/ns#" term="computers/software" /><category scheme="http://www.blogger.com/atom/ns#" term="usability marketing" /><title>PC owner, but actually an Apple fanboy</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_QD5J-lhOPc0/SuqfedFnrvI/AAAAAAAAARs/MLid8tM0Lew/s1600-h/Apple_sticker_on_Dell_laptop.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 259px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/SuqfedFnrvI/AAAAAAAAARs/MLid8tM0Lew/s400/Apple_sticker_on_Dell_laptop.jpg" border="0" alt="" id="BLOGGER_PHOTO_ID_5398302448910053106" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;div&gt;Saw the guy in the picture above on the train during my commute. He covered the original logo on what appears to be a &lt;a href="http://reviews.cnet.com/laptops/dell-xps-m1330-core/4505-3121_7-32486229.html?tag=mncol;lst"&gt;Dell XPS laptop&lt;/a&gt; with an Apple sticker. Imagine being the product manager for that Dell laptop and then running into this guy. No fun. If people put stickers of your brand's logo over that of others to create the (very poor) illusion that they have a different product than they actually have, you are doing a good job. Apple: congratulations. If people put stickers of another brand's logo over yours, you should worry. They've got no love for you. Dell: maybe you should look into &lt;a href="http://www.studiolab.io.tudelft.nl/russo/"&gt;love in people-product relationships&lt;/a&gt;?&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;I think that what I saw is not an incident. There are &lt;a href="http://www.engadget.com/2004/06/09/turn-your-pc-into-a-mac/"&gt;numerous applications&lt;/a&gt; that let you make your Windows PC desktop &lt;a href="http://www.wikihow.com/Turn-a-Windows-PC-Into-a-Mac"&gt;look like a Mac&lt;/a&gt; (ok, guilty myself, back in 1998...). Ever seen people trying make MacOS look like Windows XP? Somehow it reminds me a little of this &lt;a href="http://carscoop.blogspot.com/2006/08/ferrari-f40-suzuki-replica-for-sale.html"&gt;absurdity&lt;/a&gt;.&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;div&gt;&lt;i&gt;&lt;span class="Apple-style-span"  style="font-size:small;"&gt;(Oh, and if you think the picture is of poor quality, that's because of the crappy camera on my Apple iPhone 3G ;-))&lt;/span&gt;&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;i&gt;&lt;br /&gt;&lt;/i&gt;&lt;/div&gt;&lt;div&gt;&lt;b&gt;UPDATE&lt;/b&gt;&lt;/div&gt;&lt;div&gt;Did a small &lt;a href="http://search.twitter.com/search?q=Dell+Apple+sticker+laptop"&gt;twitter search&lt;/a&gt; on 'Dell laptop Apple sticker'. Putting Apple stickers on Dell laptops seems to happen more often than I thought...&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-9103957373738604940?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/9103957373738604940/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=9103957373738604940&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/9103957373738604940?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/9103957373738604940?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/zWMwYe0JSjY/windows-owner-but-actually-mac-fanboy.html" title="PC owner, but actually an Apple fanboy" /><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/SuqfedFnrvI/AAAAAAAAARs/MLid8tM0Lew/s72-c/Apple_sticker_on_Dell_laptop.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/10/windows-owner-but-actually-mac-fanboy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkAMR389fip7ImA9WxNVFEs.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-3551652630675205831</id><published>2009-10-25T10:56:00.006+01:00</published><updated>2009-10-25T12:06:26.166+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-25T12:06:26.166+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability research" /><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="design research" /><title>Why tablet PCs have failed and will fail</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://news.cnet.com/2300-1044_3-5895753-1.html"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px;" src="http://i.i.com.com/cnwk.1d/i/ne/p/photo/ballmer_500x387.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;In &lt;a href="http://www.mitpressjournals.org/doi/abs/10.1162/desi.2008.24.4.3"&gt;this article in Design Issues&lt;/a&gt; design historian &lt;a href="http://www.paulatkinsondesign.co.uk/"&gt;Paul Atkinson&lt;/a&gt; presents an insightful, amusing and at times depressing analysis of the rise and fall of the tablet computer, from the early pen computing of the &lt;a href="http://www.rand.org/pubs/research_memoranda/RM4122/"&gt;RAND tablet&lt;/a&gt;, via the &lt;a href="http://www.kamranelahian.com/articles/article.php?id=112"&gt;Momenta Pentop&lt;/a&gt;, to the inevitable &lt;a href="http://en.wikipedia.org/wiki/Newton_(platform)"&gt;Apple Newton Messagepad&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Technological or social challenge?&lt;/span&gt;&lt;br /&gt;An interesting aspect of the article is that Atkinson analyses the issue from both the &lt;i&gt;social constructivist&lt;/i&gt; and the &lt;i&gt;technology determinism&lt;/i&gt; perspective. Social constructivists suggest that a complex range of factors are involved in the success of products, and that social factors have precedence in the process. From the technology determinist's perspective "&lt;span style="font-style:italic;"&gt;technology and technological change are independent factors, impacting on society from the outside of that society—and that technology changes as a matter of course, following its own path, and in doing so changes the society on which it impacts.&lt;/span&gt;"&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;The technological challenges have been solved...&lt;/span&gt;&lt;br /&gt;In the end Atkinson suggests that the technological challenges that hampered early tablet PCs have been overcome, and it might be more of an issue of user acceptance than of technological shortcomings that stood and stand in the way of tablet-PC-world-dominance. Users may not want the complexity of the desktop or laptop personal computer in a handheld device and may prefer keyboard input over writing on a screen, especially because - for now - writing on paper is still considered far more comfortable than writing on a screen. So the questions that the history of the tablet PC highlights are: "&lt;i&gt;Can we do it?&lt;/i&gt;" versus "&lt;i&gt;Should we do it?&lt;/i&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;Paul Atkinson Paul (2008) &lt;a href="http://www.mitpressjournals.org/doi/abs/10.1162/desi.2008.24.4.3"&gt;A Bitter Pill to Swallow: The Rise and Fall of the Tablet Computer&lt;/a&gt;. Design Issues, Autumn 2008, Vol. 24, No. 4, Pages 3-25, MIT Press.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;[photo: &lt;a href="http://news.cnet.com/2300-1044_3-5895753-1.html"&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-3551652630675205831?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/3551652630675205831/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=3551652630675205831&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3551652630675205831?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3551652630675205831?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/opJ-T7jS9P4/why-tablet-pcs-have-failed-and-will.html" title="Why tablet PCs have failed and will fail" /><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">1</thr:total><feedburner:origLink>http://www.uselog.com/2009/10/why-tablet-pcs-have-failed-and-will.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkcGQXg9eSp7ImA9WxNWFE4.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-3261437588615032237</id><published>2009-10-12T17:54:00.007+02:00</published><updated>2009-10-13T14:47:00.661+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-13T14:47:00.661+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="events" /><title>Nov.12: Design for Usability Symposium</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.designforusability.org/symposium"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 325px; height: 316px;" src="http://www.designforusability.org/wp-content/themes/cutline-3-column-split-11/images/design-for-usability_symposium.gif" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;On November 12, World Usability Day, the &lt;a href="http://www.designforusability.org/symposium"&gt;Design for Usability&lt;/a&gt; symposium on usability for professional and consumer electronics will take place in Delft. The event targets usability and design professionals as well as academics. The &lt;a href="http://www.designforusability.org/symposium/lectures"&gt;morning program&lt;/a&gt; features state of the art lectures on usability and design:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;span style="font-weight:bold;"&gt;Gerrit van der Veer&lt;/span&gt; (president of CHI): Designing for a moving target - from functionality to usability to experience&lt;br /&gt;&lt;li&gt;&lt;span style="font-weight:bold;"&gt;Cees van Dok&lt;/span&gt; (creative director frog design Europe): The challenges in interaction design for consumer and professional electronics&lt;br /&gt;&lt;li&gt;&lt;span style="font-weight:bold;"&gt;Abbie Vanhoutte and Robert Eijlander&lt;/span&gt; (Océ-Technologies): Usability in a productive print environment&lt;br /&gt;&lt;li&gt;And, well ehh, &lt;span style="font-weight:bold;"&gt;me&lt;/span&gt;, with: No silver bullet - why making usable consumer electronics requires organizational change&lt;/ul&gt;The &lt;a href="http://www.designforusability.org/symposium/workshops"&gt;afternoon program&lt;/a&gt; consists of workshops for usability specialists, designers, and product developers, with subjects such as: managing design for usability in practice, advanced user research and evaluation, guiding and changing user behavior, and small usability techniques.&lt;br /&gt;&lt;br /&gt;Participation in the symposium is free of charge, but tickets and especially workshop slots are limited, so &lt;a href="http://www.designforusability.org/symposium/registration"&gt;registration&lt;/a&gt; is required. The event takes place at the Faculty of &lt;a href="http://www.ide.tudelft.nl"&gt;Industrial Design Engineering&lt;/a&gt; of TU Delft, in The Netherlands.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-3261437588615032237?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/3261437588615032237/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=3261437588615032237&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3261437588615032237?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3261437588615032237?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/A-kORxNmLQs/nov12-design-for-usability-symposium.html" title="Nov.12: Design for Usability Symposium" /><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/10/nov12-design-for-usability-symposium.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUDR34zfCp7ImA9WxNXGU8.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-1360632585970181961</id><published>2009-10-07T14:40:00.011+02:00</published><updated>2009-10-07T17:11:16.084+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-07T17:11:16.084+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="support and manuals" /><category scheme="http://www.blogger.com/atom/ns#" term="non-electronics" /><title>User-centered jigsaw provides background knowledge</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_QD5J-lhOPc0/SsyMYibq7UI/AAAAAAAAARc/_q96fecRcKg/s1600-h/Jigsaw-speed-dial.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 300px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/SsyMYibq7UI/AAAAAAAAARc/_q96fecRcKg/s400/Jigsaw-speed-dial.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5389837207243255106" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;When I buy tools, usually I don't buy the cheapest ones, because I like them to stay in one piece for a number of years. But when buying &lt;a href="http://www.blackanddecker.com/ProductGuide/Product-Details.aspx?ProductID=20099"&gt;this Black &amp; Decker jigsaw&lt;/a&gt; I did not only get a product that seems durable (so far, at least), but also one where considerable thought has been put into making a user-centered design.&lt;br /&gt;&lt;br /&gt;I might not be the sharpest tool in the shed (nudge nudge, wink wink), but I don't know by heart at what speed a jigsaw should be set for each type of material. Hence my liking of the speed dial on my new jigsaw (picture above) that lets you choose based on the material (wood, plywood, plastic, etc), but also lists the speed.&lt;br /&gt;&lt;br /&gt;The second remarkable aspect of the jigsaw were its blades. At first I was angry, because I thought my saw lacked the blades that were supposed to come with it. Then I looked inside the manual and saw that the blades were actually in a compartment on the saw (see picture below). Like the speed dial, the blades are labeled with the material for which they are intended. I should point out that I was a bit annoyed that I could not find the blades to begin with, but that might be fixed by adding a usecue or a temporary label to the compartment for the blades. And as a colleague remarked: it remains to be seen whether the labels on the blades will stay on when you use them. So far they did, but I've only used the saw once.&lt;br /&gt;&lt;br /&gt;And the hard-core do-it-yourself types might find it pathetic that I need all this extra information, but to me this whole product shouted: "Hey, we are Black &amp; Decker, and we have put thought into how you will use this."&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_QD5J-lhOPc0/SsyPOrKb-4I/AAAAAAAAARk/bbQVb4nt0_s/s1600-h/Jigsaw-saws.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 300px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/SsyPOrKb-4I/AAAAAAAAARk/bbQVb4nt0_s/s400/Jigsaw-saws.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5389840336323083138" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-1360632585970181961?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/1360632585970181961/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=1360632585970181961&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1360632585970181961?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1360632585970181961?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/7Snj1LppsWI/user-centered-jigsaw-provides.html" title="User-centered jigsaw provides background knowledge" /><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/SsyMYibq7UI/AAAAAAAAARc/_q96fecRcKg/s72-c/Jigsaw-speed-dial.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/10/user-centered-jigsaw-provides.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0cFRXoyfSp7ImA9WxNQF0U.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2298529554619611223</id><published>2009-09-24T12:34:00.003+02:00</published><updated>2009-09-24T12:43:34.495+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-24T12:43:34.495+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="computers/software" /><category scheme="http://www.blogger.com/atom/ns#" term="guidelines" /><title>10 useful usability findings and guidelines</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.smashingmagazine.com/2009/09/24/10-useful-usability-findings-and-guidelines/"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 117px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/SrtNI4tjBeI/AAAAAAAAARU/06sRxQ_XCjg/s400/usabilityguidelines.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5384982594509276642" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Smashing magazine has a good compilation of (web) &lt;a href="http://www.smashingmagazine.com/2009/09/24/10-useful-usability-findings-and-guidelines/"&gt;usability findings and guidelines&lt;/a&gt;, among which "&lt;span style="font-style:italic;"&gt;Most users do not scroll&lt;/span&gt;" and "&lt;span style="font-style:italic;"&gt;Blue is the best color for links&lt;/span&gt;". If you're on top of the subject it's not particularly new information, but its written down accessibly and attractively and it's very actionable information.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-2298529554619611223?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/2298529554619611223/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=2298529554619611223&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2298529554619611223?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/2298529554619611223?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/4KyhpKSU-P0/10-useful-usability-findings-and.html" title="10 useful usability findings and guidelines" /><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/SrtNI4tjBeI/AAAAAAAAARU/06sRxQ_XCjg/s72-c/usabilityguidelines.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/09/10-useful-usability-findings-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcAR3o_eCp7ImA9WxNQFk0.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-3915744463432109499</id><published>2009-09-22T09:14:00.004+02:00</published><updated>2009-09-22T09:54:06.440+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-22T09:54:06.440+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="public design" /><title>Placebo buttons provide the illusion of control</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.nextnature.net/?p=3968"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://www.nextnature.net/research/wp-content/uploads/2009/09/placebo_button_nextnature.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Placebo buttons are 'false positives'. They're design elements that look like controls, but that actually don't do anything except to give you the illusion that you are in control. Both the &lt;a href="http://www.nextnature.net/?p=3968"&gt;NextNature&lt;/a&gt; and &lt;a href="http://architectures.danlockton.co.uk/2008/10/01/placebo-buttons-false-affordances-and-habit-forming/"&gt;Design With Intent&lt;/a&gt; blog provide an interesting discussion on the subject. See also this 2004 story in the NYT on &lt;a href="http://www.nytimes.com/2004/02/27/nyregion/27BUTT.html?ex=1393218000"&gt;placebo buttons at pedestrian crossings&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;[picture from &lt;a href="http://www.nextnature.net/?p=3968"&gt;NextNature&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-3915744463432109499?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/3915744463432109499/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=3915744463432109499&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3915744463432109499?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3915744463432109499?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/AsLo1SVoKew/placebo-buttons-provide-illusion-of.html" title="Placebo buttons provide the illusion of control" /><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/09/placebo-buttons-provide-illusion-of.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcCQX8yeSp7ImA9WxNQEUQ.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-7560602329923790775</id><published>2009-09-17T14:21:00.004+02:00</published><updated>2009-09-17T14:21:00.191+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-17T14:21:00.191+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="public design" /><title>Very clear Chinese sign</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_QD5J-lhOPc0/Sq-62O2C01I/AAAAAAAAARE/V_vxZf4XqJQ/s1600-h/no-shit2.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; " src="http://4.bp.blogspot.com/_QD5J-lhOPc0/Sq-62O2C01I/AAAAAAAAARE/V_vxZf4XqJQ/s400/no-shit2.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5381725520591508306" /&gt;&lt;/a&gt;&lt;br /&gt;In contrast to the somewhat opaque sign in the Beijing subway of the &lt;a href="http://www.uselog.com/2009/09/general-information-sign.html"&gt;previous post&lt;/a&gt;, this sign - found in what is supposedly one of Beijing's Beijing duck restaurants - is very, very clear: no shit.&lt;br /&gt;&lt;br /&gt;While on the subject of signage, be sure to check out &lt;a href="http://www.telegraph.co.uk/news/newstopics/howaboutthat/3332019/Out-of-office-reply-appears-on-street-sign.html"&gt;this English/Welsh sign&lt;/a&gt;, and the background story on how it came about. (Thanks to 'anonymous' for posting it in the comments of the previous post).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-7560602329923790775?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/7560602329923790775/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=7560602329923790775&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7560602329923790775?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7560602329923790775?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/7cdo0YfPUhQ/very-clear-chinese-sign.html" title="Very clear Chinese sign" /><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/Sq-62O2C01I/AAAAAAAAARE/V_vxZf4XqJQ/s72-c/no-shit2.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/09/very-clear-chinese-sign.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEAQ3s7fCp7ImA9WxNRGUw.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-4727256591985989190</id><published>2009-09-14T10:15:00.003+02:00</published><updated>2009-09-14T10:40:42.504+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-14T10:40:42.504+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="public design" /><title>General information sign</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_QD5J-lhOPc0/Sq4AvNz3vuI/AAAAAAAAAQ0/DjVmvCaYlw4/s1600-h/general_information_sign.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 300px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/Sq4AvNz3vuI/AAAAAAAAAQ0/DjVmvCaYlw4/s400/general_information_sign.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5381239415915396834" /&gt;&lt;/a&gt;&lt;br /&gt;Ran into this little gem of a sign while riding the &lt;a href="http://en.wikipedia.org/wiki/Beijing_Subway"&gt;Beijing subway&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-4727256591985989190?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/4727256591985989190/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=4727256591985989190&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/4727256591985989190?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/4727256591985989190?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/eGFulCKSJSs/general-information-sign.html" title="General information sign" /><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/Sq4AvNz3vuI/AAAAAAAAAQ0/DjVmvCaYlw4/s72-c/general_information_sign.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/09/general-information-sign.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkEAQX87eSp7ImA9WxNTFkw.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-3998186130440856026</id><published>2009-08-18T20:04:00.000+02:00</published><updated>2009-08-18T20:04:00.101+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-18T20:04:00.101+02:00</app:edited><title>Summer break</title><content type="html">I will be taking a break from uselog for the coming month. See you on September 14th.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-3998186130440856026?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/3998186130440856026/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=3998186130440856026&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3998186130440856026?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3998186130440856026?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/wIokQhVBlVA/summer-break.html" title="Summer break" /><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/08/summer-break.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUAASXszeip7ImA9WxNRGUw.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-4761317857833184616</id><published>2009-08-13T11:40:00.005+02:00</published><updated>2009-09-14T10:42:28.582+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-14T10:42:28.582+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" /><title>Study: Expected versus experienced usability</title><content type="html">&lt;img style="width: 400px; height: 300px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/SoRMq84noXI/AAAAAAAAAQs/aWOdIy6ye1s/s400/expected-experienced-usability.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5369500956514296178" /&gt;&lt;br /&gt;&lt;br /&gt;Today I presented, on behalf of my fellow authors and myself, an exploratory study on expected and experienced usability in electronic consumer products at the &lt;a href="http://www.iea2009.org"&gt;IEA2009&lt;/a&gt; congress on ergonomics. You can download the full paper (&lt;a href="http://studiolab.io.tudelft.nl/static/gems/vankuijk/IEA09vankuijk2.pdf"&gt;pdf&lt;/a&gt;), or read a summary below. The study shows that expected and experienced usability can differ significantly under the influence of usage, how expected usability can be influenced, and what the effect of poor experienced usability can be.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Aim&lt;/span&gt;&lt;br /&gt;In the paper we explore why consumers do not seem to have a very pre-purchase distinct preference for usable products, even though these would probably satisfy them more after purchase. We wanted to explore the hypothesis that this might be due to the fact that it might be to hard for consumers to judge before use whether a product is usable or not. We call the pre-use assumptions that people have about the usability of a product expected usability. Experienced usability is the opinion people have about usability after use. We wanted to explore what product properties influence expected usability, and whether and when there is a difference between expected and experienced usability. And what the consequences of that are.&lt;br /&gt;&lt;br /&gt;&lt;img style="width: 400px; height: 126px;" src="http://2.bp.blogspot.com/_QD5J-lhOPc0/SoN97Zl741I/AAAAAAAAAQc/eu17AsDuI4c/s400/Clock-radios-expected-usability.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5369273640191517522" /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Method&lt;/span&gt;&lt;br /&gt;To study this, we showed people a number of consumer electronics products (1 navigation system, 3 alarm clocks), asked for their opinions through a questionnaire and an in-depth interview, gave them the product to use at home for two weeks, and then reassessed their opinions. So contrary to most studies on this issue people got to use the product for an extended amount of time and in their own environment.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;What you see may not be what you get&lt;/span&gt;&lt;br /&gt;The results showed that people's assessment of product usability can differ significantly before and after use. Expected usability was influenced by brand, price, styling and functional form. In addition, indications were found that expected usability can be influenced by marketing efforts, previous experiences with similar products, and opinions of other people. It was shown that product appearance (aesthetics and functional form) can be a misleading predictor for experienced usability. In other words: what you see may not be what you get.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Price as an indicator for experienced usability&lt;/span&gt;&lt;br /&gt;For one of the alarm clocks a significant gap was found between expected and experienced usability. After having used this product the participants indicated they were considerably less willing to pay the indicated retail price. As one of the participants put it: "I would not use this alarm clock even if I would get it for free!" They seemed to use the price they were willing to pay as an expression for the poor experienced usability. These participants also rated usability as a more important product property before then after use. To paraphrase &lt;a href="http://www.sciencedirect.com/science?_ob=ArticleURL&amp;_udi=B6V0D-41TMVFN-2&amp;_user=499885&amp;_rdoc=1&amp;_fmt=&amp;_orig=search&amp;_sort=d&amp;_docanchor=&amp;view=c&amp;_searchStrId=979769102&amp;_rerunOrigin=scholar.google&amp;_acct=C000024500&amp;_version=1&amp;_urlVersion=0&amp;_userid=499885&amp;md5=bcbce11fb5c423d30122f0c028bde589"&gt;Tractinsky&lt;/a&gt; (2000): "When something is unusable, beauty no longer matters."&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Functional form, styling and expected usability&lt;/span&gt;&lt;br /&gt;The appearance of the product seemed to impact expected usability in two ways. The functional form aspects, such as number of buttons and screen size seemed to impact the participants' anticipations about the user interface of a product, while the styling of a product seemed to project a more general image of being easy to use or being aimed at a target group for which products need to be easy to use (children). So designers could use a products appearance to heighten expected usability. However, then the experienced usability needs to be in line with expectations, because disconfirmation of expectations is one of the triggers for customer dissatisfaction.&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;Kuijk, J.I. van, E.E. Preijde, E.N. Toet, H. Kanis (2009) "Expected versus experienced usability: what you see is not always what you get." IEA2009: 17th World Congress on Ergonomics, August 9-14, Beijing, China.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-4761317857833184616?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/4761317857833184616/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=4761317857833184616&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/4761317857833184616?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/4761317857833184616?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/GzLgcAeWdGo/study-expected-versus-experienced.html" title="Study: Expected versus experienced usability" /><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/SoRMq84noXI/AAAAAAAAAQs/aWOdIy6ye1s/s72-c/expected-experienced-usability.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/08/study-expected-versus-experienced.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0MCQXo_fCp7ImA9WxNWGU4.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-8014336376448857843</id><published>2009-08-10T13:45:00.010+02:00</published><updated>2009-10-19T08:57:40.444+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-19T08:57:40.444+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability research" /><category scheme="http://www.blogger.com/atom/ns#" term="events" /><title>Upcoming usability and ergonomics conferences 2009/2010</title><content type="html">I'm currently attending the congress of the International Ergonomics Association (&lt;a href="http://www.iea2009.org/"&gt;IEA2009&lt;/a&gt;) in Beijing, where I will be presenting a paper on 'expected versus experienced usability' (stay tuned, I'll post it thursday, after the presentation). Being here I thought was a good reason to list some of the upcoming usability and ergonomics conferences for 2009 and 2010. Enjoy!&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.mobilehci09.org"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 80px; height: 80px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/Sn97h2UeggI/AAAAAAAAAO8/Ez17vZp8AlU/s320/MobileHCI.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5368145102296220162" /&gt;&lt;/a&gt;&lt;span style="font-weight:bold;"&gt;MobileHCI09&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;September 15-18, 2009 - Bonn (Germany)&lt;/span&gt;&lt;br /&gt;The 11th &lt;a href="http://www.mobilehci09.org/"&gt;International Conference&lt;/a&gt; on Human-Computer Interaction with Mobile Devices and Services.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.utc.fr/dppi09"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 80px; height: 80px;" src="http://4.bp.blogspot.com/_QD5J-lhOPc0/Sn-GdgA8WUI/AAAAAAAAAP8/RURaMUSg740/s320/dppi.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5368157122217138498" /&gt;&lt;/a&gt;&lt;span style="font-weight:bold;"&gt;DPPI'09&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;October 13-16, 2009 - Compiègne (France)&lt;/span&gt;&lt;br /&gt;The 4th &lt;a href="http://www.utc.fr/dppi09/"&gt;International Conference&lt;/a&gt; on Designing Pleasurable Products and Interfaces.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.hfes.org/web/HFESMeetings/09annualmeeting.html/"&gt; &lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 80px; height: 80px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/Sn979aPG36I/AAAAAAAAAPE/ZjC1dHcmg0E/s320/HFES.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5368145575793844130" /&gt;&lt;/a&gt;&lt;span style="font-weight:bold;"&gt;HFES 2009&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;October 19-23, 2009 - San Antonio (USA)&lt;/span&gt;&lt;br /&gt;The 53rd &lt;a href="http://www.hfes.org/web/HFESMeetings/09annualmeeting.html"&gt;Annual Meeting&lt;/a&gt; of the &lt;a href="http://www.hfes.org"&gt;Human Factors and Ergonomics Society&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.designforusability.org"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 80px; height: 80px;" src="http://2.bp.blogspot.com/_QD5J-lhOPc0/Sn9-HpFefXI/AAAAAAAAAPc/GdOC-whzdaU/s320/DfU.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5368147950601928050" /&gt;&lt;/a&gt;&lt;span style="font-weight:bold;"&gt;DfU Symposium&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;November 12, 2009 - Delft (The Netherlands)&lt;/span&gt;&lt;br /&gt;On &lt;a href="http://www.worldusabilityday.org/"&gt;World Usability Day 2009&lt;/a&gt;, the &lt;a href="http://www.designforusability.org"&gt;Design for Usability&lt;/a&gt; research project is hosting a &lt;a href="http://www.designforusability.org/symposium"&gt;symposium on usability&lt;/a&gt; in product development practice. Save the date for a whole day of engaging lectures, workshops and meeting user-centered design professionals and academics.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.chi2010.org"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 80px; height: 80px;" src="http://1.bp.blogspot.com/_QD5J-lhOPc0/Sn98w3l8qtI/AAAAAAAAAPM/dwLB7AyICvQ/s320/CHI2010.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5368146459847600850" /&gt;&lt;/a&gt;&lt;span style="font-weight:bold;"&gt;CHI 2010&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;April 10-15 April 2010 - Atlanta (USA)&lt;/span&gt;&lt;br /&gt;The 28th &lt;a href="http://www.chi2010.org"&gt;conference&lt;/a&gt; of the ACM special interest group for Computer Human Interaction (or &lt;a href="http://sigchi.org/"&gt;SIGCHI&lt;/a&gt;, or CHI).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href= "http://www.usabilityprofessionals.org/conference/2010/index.new.html"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 80px; height: 80px;" src="http://3.bp.blogspot.com/_QD5J-lhOPc0/Sn-BDu2TdYI/AAAAAAAAAP0/7-Qb-oqOZ1Y/s320/UPA2010.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5368151181964309890" /&gt;&lt;/a&gt;&lt;span style="font-weight:bold;"&gt;UPA 2010&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;May 24-28, 2010 - Munich (Germany)&lt;br /&gt;&lt;/span&gt;The &lt;a href="http://www.usabilityprofessionals.org/conference/2010/index.new.html"&gt;annual meeting&lt;/a&gt; of the &lt;a href="http://www.upassoc.org"&gt;Usability Professionals' Association&lt;/a&gt;.&lt;BR&gt;&lt;BR&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-8014336376448857843?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/8014336376448857843/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=8014336376448857843&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8014336376448857843?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/8014336376448857843?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/ti5sfDLmn00/upcoming-usability-and-ergonomics.html" title="Upcoming usability and ergonomics conferences 2009/2010" /><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/Sn97h2UeggI/AAAAAAAAAO8/Ez17vZp8AlU/s72-c/MobileHCI.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://www.uselog.com/2009/08/upcoming-usability-and-ergonomics.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEEFRnYzfSp7ImA9WxJaFUk.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-3728143713059447028</id><published>2009-08-06T08:57:00.007+02:00</published><updated>2009-08-06T09:10:17.885+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-06T09:10:17.885+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="public design" /><title>Redesigning the ATM interface for Wells Fargo</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://physicalinterface.com/view/that-design-is-money"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://physicalinterface.com/files/physicalinterface/wells-fargo-atm-case/wf01-500.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;When replacing their old ATMs with newer touchscreen models, US bank &lt;a href="https://www.wellsfargo.com/"&gt;Wells Fargo&lt;/a&gt; hired design firm &lt;a href="http://www.pentagram.com/en/"&gt;Pentagram&lt;/a&gt; to redesign the on-screen interface. Holger Struppek, who did the visual design on the project, has a &lt;a href="http://physicalinterface.com/view/that-design-is-money"&gt;highly illustrated story&lt;/a&gt; of the design process on his weblog &lt;a href="http://www.physicalinterface.com"&gt;physicalinterface.com&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;In the story there's an excellent example of branding versus usability considerations when designing a user interface: &lt;blockquote&gt;However, blue seemed to be a color that was genuinely pleasant to look at, and even though it was “off-brand”, everyone could live with it. It provided great contrast to the red Return Card button and the yellow alert boxes. During user testing, we presented participants with our color choices and got the same results: “It’s calming”, “I like the blue sky”, ... and so we went with it.&lt;br /&gt;&lt;br /&gt;Surprisingly, Wells Fargo recently switched the UI to the current tan color scheme. I don’t know what prompted that decision, but it does bring it back in line with their brand.&lt;/blockquote&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://physicalinterface.com/files/physicalinterface/wells-fargo-atm-case/wf_colors.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://physicalinterface.com/files/physicalinterface/wells-fargo-atm-case/wf_colors.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;[&lt;span style="font-style:italic;"&gt;Via: &lt;a href="http://twitter.com/janepyle"&gt;Jane Pyle&lt;/a&gt;&lt;/span&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-3728143713059447028?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/3728143713059447028/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=3728143713059447028&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3728143713059447028?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/3728143713059447028?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/w9WU36UxpLc/redesigning-atm-interface-for-wells.html" title="Redesigning the ATM interface for Wells Fargo" /><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/08/redesigning-atm-interface-for-wells.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IGSXc4eyp7ImA9WxJaE0o.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-6697787144322291664</id><published>2009-08-03T09:16:00.005+02:00</published><updated>2009-08-04T10:45:28.933+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-04T10:45:28.933+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="usability resources" /><title>A short history of human-computer interaction, by John Carroll</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.interaction-design.org/encyclopedia/human_computer_interaction_hci.html"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://www.britannica.com/blogs/wp-content/uploads/2008/11/27144-004-822dd3f9.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;One of the 'founding fathers of HCI', &lt;a href="http://ist.psu.edu/ist/directory/faculty/?EmployeeID=234"&gt;John Carroll&lt;/a&gt;, has written an excellent &lt;a href="http://www.interaction-design.org/encyclopedia/human_computer_interaction_hci.html"&gt;historic overview&lt;/a&gt; of how the field of Human-Computer Interaction (HCI) developed, diversified and matured. A must read, really puts some developments into perspective. &lt;blockquote&gt;Today, largely due to the success of that endeavor, HCI is a vast and multifaceted community, loosely bound by the evolving concept of usability, and the integrating commitment to value human concerns as the primary consideration in creating interactive systems.&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-6697787144322291664?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/6697787144322291664/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=6697787144322291664&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/6697787144322291664?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/6697787144322291664?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/8t1zYy-n7Yo/short-history-of-human-computer.html" title="A short history of human-computer interaction, by John Carroll" /><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/08/short-history-of-human-computer.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UNSHs7cSp7ImA9WxJaEE8.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-7006053381155636189</id><published>2009-07-31T08:57:00.006+02:00</published><updated>2009-07-31T09:28:19.509+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-31T09:28:19.509+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="physical ergonomics" /><category scheme="http://www.blogger.com/atom/ns#" term="consumer electronics" /><title>The future of home entertainment: we will all look like dorks</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.dailymail.co.uk/news/article-410642/One-giant-step-home-entertainment.html;jsessionid=275E9529BD8B279BBC41E4C466A38CE2"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px" src="http://img.dailymail.co.uk/i/pix/2006/10/virtualPA_468x335.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Somehow Toshiba came to the conclusions that this is future of home entertainment. Or at least back in 2006 they thought so, because then they presented this helmet offering its user a full 360 degrees view of movies and video games through an integrated 40 centimeter dome-shaped screen. If this is the future of home entertainment I think that in the future we will all have really well-developed neck muscles and no self esteem. The picture is from a &lt;a href="http://www.dailymail.co.uk/news/article-410642/One-giant-step-home-entertainment.html;jsessionid=275E9529BD8B279BBC41E4C466A38CE2"&gt;2006 article in the Daily Mail&lt;/a&gt;, but it's so outrageous I thought it still deserved some attention.&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.youtube.com/watch?v=yo1BRhoBHAs"&gt;Movie from TV Tokyo showing the helmet (in Japanese)&lt;/a&gt;&lt;br /&gt;&gt; Fox News: &lt;a href="http://www.foxnews.com/story/0,2933,225642,00.html"&gt;Virtual-reality helmet gives 360-degree view&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-7006053381155636189?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/7006053381155636189/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=7006053381155636189&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7006053381155636189?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7006053381155636189?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/830uv1zzpmg/future-of-home-entertainment-we-will.html" title="The future of home entertainment: we will all look like dorks" /><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/future-of-home-entertainment-we-will.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkYHSXgzfyp7ImA9WxJaEE8.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-7764229262185804811</id><published>2009-07-28T12:43:00.006+02:00</published><updated>2009-07-31T09:08:58.687+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-31T09:08:58.687+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="mobile phones" /><title>Modular mobile phone from ModuMobile</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.modumobile.com/"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://www.cnet.co.uk/i/c/blg/cat/mobiles/modu/handson/one.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;An interesting new product proposition from &lt;a href="http://www.modumobile.com/"&gt;ModuMobile&lt;/a&gt;: one tiny basic mobile phone module (pictured above) slides into a multitude of modules (below) that extend its functionality or just change the looks. Like &lt;a href="http://en.wikipedia.org/wiki/Nokia_8210"&gt;Nokia's Xpress-on covers&lt;/a&gt;, but with built-in functionality. For now they're just selling in Israel.&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.techcrunch.com/2009/02/11/modu-comes-out-of-the-woodwork-with-a-truly-innovative-mobile-offering/"&gt;Techcrunch: Modu Comes Out Of The Woodwork With A Truly Innovative Mobile Offering&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://cache0.techcrunch.com/wp-content/uploads/2009/02/modu-screen.png"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px;" src="http://cache0.techcrunch.com/wp-content/uploads/2009/02/modu-screen.png" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;[Lower picture from &lt;a href="http://www.techcrunch.com/2009/02/11/modu-comes-out-of-the-woodwork-with-a-truly-innovative-mobile-offering/"&gt;TechCrunch&lt;/a&gt;]&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-7764229262185804811?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/7764229262185804811/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=7764229262185804811&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7764229262185804811?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/7764229262185804811?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/ifLeY3e7umM/modular-mobile-phone-from-modumobile_28.html" title="Modular mobile phone from ModuMobile" /><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/modular-mobile-phone-from-modumobile_28.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEER34_fCp7ImA9WxJbE04.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-1984245948019862250</id><published>2009-07-20T10:09:00.012+02:00</published><updated>2009-07-23T10:26:46.044+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-23T10:26:46.044+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="interaction design" /><category scheme="http://www.blogger.com/atom/ns#" term="product development" /><title>Ensuring consistency and interoperability: monopolize or standardize</title><content type="html">&lt;object width="425" height="344"&gt;&lt;param name="movie" value="http://www.youtube.com/v/gvcmOBWieu8&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/gvcmOBWieu8&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;So how is it that Microsoft Windows, with all the effort put into &lt;a href="http://www.istartedsomething.com/20070130/interview-tjeerd-ces2007/"&gt;user experience design&lt;/a&gt;, does not seem to be able to measure up to Apple computers in terms of usability? There are probably many answers to that question, some of which involve stuff like creating a cult, appealing aesthetics, brand perception and legacy issues.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Owning the eco-system&lt;/span&gt;&lt;br /&gt;One very important factor, I think, is summed up in the &lt;a href="http://www.apple.com/getamac/ads/"&gt;Mac vs PC commercial&lt;/a&gt; &lt;a href="http://movies.apple.com/movies/us/apple/getamac/apple_getamac_breakthrough_20080401_480x272.mov"&gt;breakthrough&lt;/a&gt;. Mac and a therapist are trying to convince PC that it's not his fault that he's underperforming. The therapist says: "&lt;span style="font-style:italic;"&gt;Unlike Mac, whose operating system and hardware are all made by the same people, your stuff comes from a bunch of different places. [...] Under those circumstances, who could expect everything to work together the way they should?&lt;/span&gt;" &lt;br /&gt;&lt;br /&gt;This is a very interesting question, as consumer electronics are turning more and more into &lt;a href="http://www.uselog.com/2009/06/consumer-electronics-have-become.html"&gt;complex systems&lt;/a&gt;. The question is: how do you get all the parts of the system to work together seamlessly? I see two options: monopolize the eco-system or standardize it.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Monopolize the eco-system&lt;/span&gt;&lt;br /&gt;If you look at the iPod/iPhone system it goes beyond just the hardware-software alignment that is mentioned in the commercial. Apple creates and/or controls the hardware (iPhone), firmware (iPhone OS), software (apps), connection software (iTunes), content delivery (iTunes Store) and software delivery (App Store). Owning the whole eco-system of a product makes it easier to create usable products as you can coordinate the application of user experience design guidelines, and deal with connectivity and interoperability issues. And though it might be argued that Apple's complete control over the eco-system might result in higher prices than an open market situation, consumers do get a better user experience for that price.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Standardize&lt;/span&gt;&lt;br /&gt;Another way to at least get the different components of a system to work together - to ensure interoperability - is to standardize. As an industry you define a common standard. And stick to it. Think of for example &lt;a href="http://en.wikipedia.org/wiki/USB"&gt;USB&lt;/a&gt; plugs, &lt;a href="http://en.wikipedia.org/wiki/Wi-Fi"&gt;Wifi&lt;/a&gt; signals, or &lt;a href="http://en.wikipedia.org/wiki/Compact_cassette"&gt;compact cassettes&lt;/a&gt;. If you choose not join &lt;span style="font-style:italic;"&gt;the&lt;/span&gt; standard, as Philips did with the &lt;a href="http://en.wikipedia.org/wiki/Video_2000"&gt;VIDEO2000&lt;/a&gt; video recording system, you run the risk of isolating your users from the rest of the system. VIDEO2000 users could not rent video tapes because they're medium was not the standard.&lt;br /&gt;&lt;br /&gt;However, getting to a standard can be an excruciating process. It can require one system becoming so dominant it is the de facto standard (like &lt;a href="http://en.wikipedia.org/wiki/CD"&gt;CDs&lt;/a&gt;), an industry seeing a big advantage to standardization, or simply forcing it by law, as with the European Commission demanding &lt;a href="http://www.uselog.com/2009/02/european-commission-urges-mobile-phone.html"&gt;standardization of mobile phone chargers&lt;/a&gt;. And even when interoperability standards have been established, some manufacturers may deliberately deviate from it - slightly - so they can claim to adhere to the standard (that's another check-mark on the box), but sales people will still have the argument that it might be better to purchase all equipment from this one manufacturer, because then you'll know for sure it will work.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Interoperability and/or UI consistency&lt;/span&gt;&lt;br /&gt;However, standardizing for interoperability is one thing, but what about user interfaces? What if - for example - you want to run a Route66 personal navigation application on a Nokia mobile phone? Whose interface should be dominant? The Route66 interface that is optimized for navigation, and that users of Route66 software are used to, or the Nokia UI, in order not to break within-product UI consistency? I don't think you're going to solve that one through standardization. Monopolization works better. I think we can expect the &lt;a href="http://iphone.tomtom.com/"&gt;TomTom iPhone App&lt;/a&gt; to adhere to&lt;a href="http://developer.apple.com/iphone/"&gt; iPhone design guidelines&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;So am I in favor of monopolies? No. But I do see some bright sides.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9968619-1984245948019862250?l=www.uselog.com'/&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.uselog.com/feeds/1984245948019862250/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=9968619&amp;postID=1984245948019862250&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1984245948019862250?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/9968619/posts/default/1984245948019862250?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/uselog/~3/jBimDqfBwU0/ensuring-interoperability-monopolize-or.html" title="Ensuring consistency and interoperability: monopolize or standardize" /><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/ensuring-interoperability-monopolize-or.html</feedburner:origLink></entry><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;DkYCSHo6fCp7ImA9WxJaEE8.&quot;"><id>tag:blogger.com,1999:blog-9968619.post-2413176792826925075</id><published>2009-07-14T09:41:00.007+02:00</published><updated>2009-07-31T09:09:29.414+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-31T09:09:29.414+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://www.simplicitylabs.net/"&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="1 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">1</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="8 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">8</thr:total><feedburner:origLink>http://www.uselog.com/2009/06/designing-usable-money-is-not-nickel_29.html</feedburner:origLink></entry></feed>
