<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for Lyle</title><link>http://disqus.com/people/8fc436239651f735b20bd86dc60421e3/</link><description></description><language>en</language><lastBuildDate>Thu, 07 May 2009 11:30:35 -0000</lastBuildDate><item><title>Re: Redesigning the boxee experience</title><link>http://whitneyhess.disqus.com/redesigning_the_boxee_experience/#comment-4488770</link><description>Congrats on the new position.  Sounds like a great and fun challenge ahead.  &lt;br&gt;&lt;br&gt;Question: How will you determine what the next gen/level of users need?  What if the "masses" need something different from the (presumably tech-savvy) early adopters?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lyle</dc:creator><pubDate>Thu, 18 Dec 2008 16:14:59 -0000</pubDate></item><item><title>Re: Photo of the day: Whirlpool Quiet Partner 1 utensil tray</title><link>http://whitneyhess.disqus.com/photo_of_the_day_whirlpool_quiet_partner_1_utensil_tray/#comment-9094538</link><description>Have had a dishwasher like this for about 6 years...never knew it didn't have to go on the door.  Can you say "lack of affordance" or "non-intuitive?"  I thought you could.  :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lyle</dc:creator><pubDate>Thu, 07 May 2009 11:30:35 -0000</pubDate></item><item><title>Re: Interruptions: Nuisance or Valuable Data Source? (A UBlog Rerun&amp;#8230;)</title><link>http://usabilityblog.disqus.com/interruptions_nuisance_or_valuable_data_source_a_ublog_rerun8230/#comment-4785071</link><description>I think having fewer distractions during testing can be a Good Thing.  Granted, it may falsely set the application up to succeed or to do better than it might in the real world.  But even given that kind of benefit, most applications will have many problems uncovered during testing.&lt;br&gt;&lt;br&gt;In your hypothetical example, you have to question whether the reason the app earned undeservedly high marks was due to a lack of interruptions or due to some other issues with the usability testing methods applied.  For example: Were the tasks too simple and not representative of real world tasks? Were the evaluators truly representative of the user base?  Did the facilitator ask any leading questions?  etc...&lt;br&gt;&lt;br&gt;Of course, your theory about distractions might be right for the hypothetical situation...and you could use other UCD methods to validate or reinforce that theory.  For example, you might use a little ethnographic field study with tech support and managers and observe them using this application and others to determine if distractions were the cause of user errors that didn't turn up when there were no distractions.&lt;br&gt;&lt;br&gt;P.S. Glad to see you blogging!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lyle</dc:creator><pubDate>Mon, 11 Apr 2005 12:52:59 -0000</pubDate></item></channel></rss>