tag:blogger.com,1999:blog-9968619.post3990703659591851935..comments2010-07-10T13:42:27.533+02:00Jasper (uselog.com)noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9968619.post-46349507810543211392010-07-10T13:42:27.528+02:002010-07-10T13:42:27.528+02:00<b>FIRST ITERATION</b><br />@Frederik<br />I have included the phenomenon you describe - focusing on concrete usability issues instead of overhauling the UI concept in follow-up projects - in the recommendation.Jasper (uselog.com)http://www.blogger.com/profile/10274466709014480194noreply@blogger.comtag:blogger.com,1999:blog-9968619.post-57771510342316745282010-06-10T14:39:03.776+02:002010-06-10T14:39:03.776+02:00Great point you&#39;re making here: a good concept can fail if the implementation isn&#39;t done well, and you can make the details perfect, but without a good concept it still doesn&#39;t work. I&#39;ve noticed the same in my own research, both are equally important for optimal usability.<br /><br />When evaluating an existing product however, it is much easier to find and fix problems in the implementation details than in the UI concept. That can make it difficult for usability evaluators to ignore these problems and focus on the concept, but this recommendation reminds you that you can only improve to a certain limit that way: until you reach the hypothetical limit of usability influenced by the UI concept.Fredrikhttp://www.blogger.com/profile/09650713128915213537noreply@blogger.com