<?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: Ugly UI</title>
	<atom:link href="http://blog.brodzinski.com/2008/04/ugly-ui.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2008/04/ugly-ui.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Fri, 10 Feb 2012 19:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2008/04/ugly-ui.html#comment-1985</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Thu, 24 Apr 2008 13:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2008/04/ugly-ui.html#comment-1985</guid>
		<description>I think that&#039;s another great example when usability isn&#039;t the number one. You hit the nail with your trainable/untrainable definition.</description>
		<content:encoded><![CDATA[<p>I think that&#8217;s another great example when usability isn&#8217;t the number one. You hit the nail with your trainable/untrainable definition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamlet D'Arcy</title>
		<link>http://blog.brodzinski.com/2008/04/ugly-ui.html#comment-1984</link>
		<dc:creator>Hamlet D'Arcy</dc:creator>
		<pubDate>Thu, 24 Apr 2008 13:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2008/04/ugly-ui.html#comment-1984</guid>
		<description>In my industry, I like to make a distinction between people users can train and users I cannot. &lt;br/&gt;&lt;br/&gt;We can&#039;t train people on our public facing website. So our approach to usability here is simplicity and intuitiveness through user-testing. &lt;br/&gt;&lt;br/&gt;We /can/ train internal users (like in a call center or support). So our approach here has little to do with intuitiveness. If we can design a screenflow that shaves 5 seconds off of call time (for every call) at the expense of having to train new hires for an extra 5 minutes (one time only), then we&#039;ll have provided hige ROI over the life of that application. &lt;br/&gt;&lt;br/&gt;For the latter approach, a good industrial engineer is worth more than a set of expert users.</description>
		<content:encoded><![CDATA[<p>In my industry, I like to make a distinction between people users can train and users I cannot. </p>
<p>We can&#8217;t train people on our public facing website. So our approach to usability here is simplicity and intuitiveness through user-testing. </p>
<p>We /can/ train internal users (like in a call center or support). So our approach here has little to do with intuitiveness. If we can design a screenflow that shaves 5 seconds off of call time (for every call) at the expense of having to train new hires for an extra 5 minutes (one time only), then we&#8217;ll have provided hige ROI over the life of that application. </p>
<p>For the latter approach, a good industrial engineer is worth more than a set of expert users.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

