<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>UsabilityBlog - Latest Comments in Liveblogging A Game Usability Test</title><link>http://usabilityblog.disqus.com/</link><description>Blogging about usability and the user experience</description><atom:link href="https://usabilityblog.disqus.com/liveblogging_a_game_usability_test/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 16 Dec 2008 05:12:32 -0000</lastBuildDate><item><title>Re: Liveblogging A Game Usability Test</title><link>http://www.usabilityblog.com/2008/12/liveblogging-a-game-usability-test/#comment-4785127</link><description>&lt;p&gt;Hi there. My first visit to this blog. Great post about the live-blogging-game-test. I really enjoyed it. Sort of gonzo-style within usability. Loved the reference to "gulf of execution", I often forget these thing we've learned from the master, to integrate them in my descriptions of challenges or problems. Thanks, Ole&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ole Gregersen</dc:creator><pubDate>Tue, 16 Dec 2008 05:12:32 -0000</pubDate></item><item><title>Re: Liveblogging A Game Usability Test</title><link>http://www.usabilityblog.com/2008/12/liveblogging-a-game-usability-test/#comment-4785126</link><description>&lt;p&gt;I was under the impression that the learning curve usually refers to what the situation necessitates for success, not the rate at which learning is actually achieved. That is, by default when you say "learning curve", most people assume you are referring to the task, not the subject.&lt;/p&gt;&lt;p&gt;So it sounds possible that the game's learning curve is steeper than it was thought to be.&lt;/p&gt;&lt;p&gt;I suppose that, if you enjoy being misinterpreted because you use non-standard although correct on a technicality usage of the term, you could say that the learning curve of the players was long and flat, but to just say "It’s a long flat learning curve" is ambiguous. Most people would think that you're applying that sentence to the requirement of the task and would be misled or would assume you're misusing the term.&lt;/p&gt;&lt;p&gt;My two cents. Whether you agree with my understanding or not, I'm not sure how I feel about a usability expert intentionally writing in a way that they know will be misunderstood. ;)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave</dc:creator><pubDate>Fri, 12 Dec 2008 14:36:37 -0000</pubDate></item><item><title>Re: Liveblogging A Game Usability Test</title><link>http://www.usabilityblog.com/2008/12/liveblogging-a-game-usability-test/#comment-4785125</link><description>&lt;p&gt;Paul,&lt;/p&gt;&lt;p&gt;I really enjoy this. Any way that "Paul visits X and liveblogs a test/focus group" could be a regular feature?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Neil</dc:creator><pubDate>Thu, 11 Dec 2008 19:22:42 -0000</pubDate></item></channel></rss>