<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-9968619.post6000451827633790375..comments</id><updated>2010-07-10T13:31:20.346+02:00</updated><category term='simplicity'/><category term='business and usability'/><category term='office equipment'/><category term='thesis'/><category term='physical ergonomics'/><category term='packaging'/><category term='principles/guidelines'/><category term='mobile phones'/><category term='events'/><category term='design research'/><category term='product development'/><category term='medical products'/><category term='public design'/><category term='product impact'/><category term='user behaviour'/><category term='consumer electronics'/><category term='non-electronics'/><category term='usability quotes'/><category term='remote controls'/><category term='recommendations for industry'/><category term='marketing'/><category term='home appliances'/><category term='usability resources'/><category term='computers/software'/><category term='automotive'/><category term='user research'/><category term='support and manuals'/><category term='usability research'/><category term='interaction design'/><category term='usability studies'/><title type='text'>Comments on uselog.com | the product usability weblog: 9. Process: A development process that facilitates...</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.uselog.com/feeds/6000451827633790375/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9968619/6000451827633790375/comments/default'/><link rel='alternate' type='text/html' href='http://www.uselog.com/2010/06/9-process-development-process-that.html'/><author><name>Jasper (uselog.com)</name><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://www.oli.tudelft.nl/uselog/pictures/Jasper_van_kuijk_web.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>2</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-9968619.post-2968971252141979117</id><published>2010-07-10T13:31:20.341+02:00</published><updated>2010-07-10T13:31:20.341+02:00</updated><title type='text'>&lt;b&gt;FIRST ITERATION&lt;/b&gt;
@ William
True, it is good ...</title><content type='html'>&lt;b&gt;FIRST ITERATION&lt;/b&gt;&lt;br /&gt;@ William&lt;br /&gt;True, it is good to make a distinction between revolutionary and incremental innovation in development projects. But a UCD process is not necessarily in conflict with radical innovation, but that depends on the &amp;#39;horizon&amp;#39; you are targeting. You can make a very innovative product that fits the current context of use based on current product usage. However, if you would ask the same people what product they want, yes, then you&amp;#39;d probably end up with some very dubious input that is only based on their knowledge of current products, technologies and lifestyles. And if you are talking really radical innovations, with a horizon of 15 to 20 years, than maybe even observing current users is not of much use as the product will be used in a completely different context of use. However, I think that even radical innovations need to fit the properties and needs of the user group, it is just much harder to assess what they are in those cases.&lt;br /&gt;&lt;br /&gt;The distinction you point out, between R&amp;amp;D and product development, is good. The product development organizations and projects I studied were not in a R&amp;amp;D context and my focus was not on innovation but on usability. I will include this context for the recommendations in the introduction. But I will not change this particular recommendation. How does that sound?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9968619/6000451827633790375/comments/default/2968971252141979117'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9968619/6000451827633790375/comments/default/2968971252141979117'/><link rel='alternate' type='text/html' href='http://www.uselog.com/2010/06/9-process-development-process-that.html?showComment=1278761480341#c2968971252141979117' title=''/><author><name>Jasper (uselog.com)</name><uri>http://www.blogger.com/profile/10274466709014480194</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://www.oli.tudelft.nl/uselog/pictures/Jasper_van_kuijk_web.jpg'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.uselog.com/2010/06/9-process-development-process-that.html' ref='tag:blogger.com,1999:blog-9968619.post-6000451827633790375' source='http://www.blogger.com/feeds/9968619/posts/default/6000451827633790375' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-869591515'/></entry><entry><id>tag:blogger.com,1999:blog-9968619.post-7528300678777661016</id><published>2010-06-20T20:42:26.307+02:00</published><updated>2010-06-20T20:42:26.307+02:00</updated><title type='text'>One caveat I would offer on this guideline is that...</title><content type='html'>One caveat I would offer on this guideline is that user-centered design methods are effective for evolutionary design, but often counter-productive for revolutionary r&amp;amp;d-type design. I am reminded of an interview that I did with Dean Kamen where he was explaining that they engaged in very little (i.e., none) UCD research. His comment on the redesign of the wheelchair was that UCD would result in incremental improvements (e.g., a cupholder), but not breakthroughs (e.g., like an iBot). This has been accepted in r&amp;amp;d shops for many years, but UCD researchers are just now gravitating to this point of view. Accordingly, I think it is important to know the kind of design/development you are doing before assuming you are basing practice on UCD.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9968619/6000451827633790375/comments/default/7528300678777661016'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9968619/6000451827633790375/comments/default/7528300678777661016'/><link rel='alternate' type='text/html' href='http://www.uselog.com/2010/06/9-process-development-process-that.html?showComment=1277059346307#c7528300678777661016' title=''/><author><name>William Lidwell</name><uri>http://deconstructingproductdesign.com/</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img1.blogblog.com/img/blank.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.uselog.com/2010/06/9-process-development-process-that.html' ref='tag:blogger.com,1999:blog-9968619.post-6000451827633790375' source='http://www.blogger.com/feeds/9968619/posts/default/6000451827633790375' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-2030483634'/></entry></feed>
