<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The 8 Criteria For Usable Software</title>
	<atom:link href="http://anthonyfranco.wordpress.com/2009/02/14/the-8-criteria-for-usable-software/feed/" rel="self" type="application/rss+xml" />
	<link>http://anthonyfranco.wordpress.com/2009/02/14/the-8-criteria-for-usable-software/</link>
	<description>People Deserve Better Software</description>
	<lastBuildDate>Thu, 17 Dec 2009 16:25:30 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave Sherohman</title>
		<link>http://anthonyfranco.wordpress.com/2009/02/14/the-8-criteria-for-usable-software/#comment-4487</link>
		<dc:creator>Dave Sherohman</dc:creator>
		<pubDate>Thu, 19 Feb 2009 11:57:33 +0000</pubDate>
		<guid isPermaLink="false">http://anthonyfranco.wordpress.com/?p=254#comment-4487</guid>
		<description>Excellent article!  One minor correction/refinement of point 1, though:

&quot;&lt;i&gt;Some of the ways to ensure this on a project is to go out and interview the target customers of the application.&lt;/i&gt;&quot;

It&#039;s important to interview the target &lt;i&gt;users&lt;/i&gt; of the application.  Far and away, the worst-designed, most useless software projects I&#039;ve worked on have been those which were designed based on what the customer (i.e., management) thought the users would/should need without talking to the people who would be using it day in and day out to find out what they actually needed.</description>
		<content:encoded><![CDATA[<p>Excellent article!  One minor correction/refinement of point 1, though:</p>
<p>&#8220;<i>Some of the ways to ensure this on a project is to go out and interview the target customers of the application.</i>&#8221;</p>
<p>It&#8217;s important to interview the target <i>users</i> of the application.  Far and away, the worst-designed, most useless software projects I&#8217;ve worked on have been those which were designed based on what the customer (i.e., management) thought the users would/should need without talking to the people who would be using it day in and day out to find out what they actually needed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
