<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Living With Bugs: How To Mitigate Usability Issues</title>
	<atom:link href="http://www.usabilitycounts.com/2008/09/10/living-with-bugs-how-to-mitigate-usability-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.usabilitycounts.com/2008/09/10/living-with-bugs-how-to-mitigate-usability-issues/</link>
	<description>Usability, User Experience, Social Media, and Content Management</description>
	<lastBuildDate>Tue, 07 Sep 2010 00:56:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: jbeller</title>
		<link>http://www.usabilitycounts.com/2008/09/10/living-with-bugs-how-to-mitigate-usability-issues/comment-page-1/#comment-63</link>
		<dc:creator>jbeller</dc:creator>
		<pubDate>Wed, 10 Sep 2008 19:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.usabilitycounts.com/?p=417#comment-63</guid>
		<description>Patrick, thank you for referencing my recent blog post. I think I should clarify my stance regarding how bugs and workarounds should never be acceptable.

This is what happens when frustrations boil over to a blog. I probably shouldn&#039;t have posted my frustrations because they largely had to do with a project I am working on.  Unfortunately, I can&#039;t reveal the client.  Oddly enough many people I&#039;m working with feel the same way about the situation and some things are just out of our control.

This particular project is a very simple application that queries a database.  It&#039;s hastily put together and users are expected to use it in their work.  It&#039;s far from perfect in its current state.  Without considering HOW people work, the not ready for prime time application does more harm than good for the end-user because the bugs, errors and workarounds slow them down.

Do I expect bug-free applications?  Absolutely not.  Just like you I am a realist and your points in your post are quite good.  It&#039;s nearly impossible to be bug free, but what I am saying is if the business conditions allow, do the due diligence necessary to minimize the bugs, errors and usability issues as much as you can before release.  This way you spend less time fixing problems.  You also remove barriers to performance - which is what the application is supposed to do in the first place.

Hope this clears things up. I appreciate you taking me to task on this issue.</description>
		<content:encoded><![CDATA[<p>Patrick, thank you for referencing my recent blog post. I think I should clarify my stance regarding how bugs and workarounds should never be acceptable.</p>
<p>This is what happens when frustrations boil over to a blog. I probably shouldn&#8217;t have posted my frustrations because they largely had to do with a project I am working on.  Unfortunately, I can&#8217;t reveal the client.  Oddly enough many people I&#8217;m working with feel the same way about the situation and some things are just out of our control.</p>
<p>This particular project is a very simple application that queries a database.  It&#8217;s hastily put together and users are expected to use it in their work.  It&#8217;s far from perfect in its current state.  Without considering HOW people work, the not ready for prime time application does more harm than good for the end-user because the bugs, errors and workarounds slow them down.</p>
<p>Do I expect bug-free applications?  Absolutely not.  Just like you I am a realist and your points in your post are quite good.  It&#8217;s nearly impossible to be bug free, but what I am saying is if the business conditions allow, do the due diligence necessary to minimize the bugs, errors and usability issues as much as you can before release.  This way you spend less time fixing problems.  You also remove barriers to performance &#8211; which is what the application is supposed to do in the first place.</p>
<p>Hope this clears things up. I appreciate you taking me to task on this issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.297 seconds -->
