<?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"
	>
<channel>
	<title>Comments on: Why usability is a path to failure</title>
	<atom:link href="http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/</link>
	<description>Adaptive Path Blog</description>
	<pubDate>Thu, 07 Aug 2008 23:42:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Why usability is a path to failure (or &#34;Usability is not design&#34;) &#124; Software Interface Design</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-178725</link>
		<dc:creator>Why usability is a path to failure (or &#34;Usability is not design&#34;) &#124; Software Interface Design</dc:creator>
		<pubDate>Tue, 10 Jun 2008 04:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-178725</guid>
		<description>[...] http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/" rel="nofollow">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Bolt &#124; Peters and Ethnio Blog &#187; Users Suck</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176947</link>
		<dc:creator>The Bolt &#124; Peters and Ethnio Blog &#187; Users Suck</dc:creator>
		<pubDate>Wed, 26 Mar 2008 23:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176947</guid>
		<description>[...] not sure if Todd Wilken&#8217;s blog post on Why usability is a path to failure at the adaptive path blog was just venting, or maybe even going for the &#8220;99% Something [...]</description>
		<content:encoded><![CDATA[<p>[...] not sure if Todd Wilken&#8217;s blog post on Why usability is a path to failure at the adaptive path blog was just venting, or maybe even going for the &#8220;99% Something [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dawn Barber</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176483</link>
		<dc:creator>Dawn Barber</dc:creator>
		<pubDate>Fri, 29 Feb 2008 02:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176483</guid>
		<description>I appreciate your comments about usability. I think it’s important for people in the field hear and understand others’ points of view. It’s stimulating. However, I think this opinion of usability is off the mark and I'll respond to a few of your questions and opinions.

 

You asked this question, “So, why oh why do people in this day age still hold up “usability” as something laudable in product and service design?” I have never experienced being in the limelight simply for being in this field. It’s amazingly hard work to consult with closed-minded people or to travel constantly to cover field studies to gather data while listening to first-hand complaints from users that the performance of the system is frustrating. It’s exhausting to work with developers who are on fire to put you in your place because you try to help them do their jobs. It takes years to prove your worth in this field as it did for my usability team. So, if you hear someone being lauded in this field, they most likely earned it. Recently I heard one of our project managers say, “If I don’t have usability on a project I’m putting it in as a project risk right away”, I sincerely hope any others in our department within earshot did not assume we have a cushy and well liked job.

 

You opined, “Usability is not a strategy for design success. The efficiency you create in your interface will be copied almost instantaneously by your competitors.” If a competitor copies what we’ve done, that would be their first mistake. You see, different products have different users with different needs (the challenge is determining those needs carefully). Most of the users in our company work remotely at client sites (could be a client warehouse, basement or storage closet). Their needs would be different than those sitting at the same desk each day. How do you optimize a design for specific users? What if our users don’t use a mouse because they may not have the desk space in a closet? Do you design for heavy keyboard usage, great! But what if our users are mature and do not have much experience with hot keys? How do we design the UI to accommodate this? The solution must come from using usability methods. User research from field studies, conceptual inquiry (usability methods) and task analysis get us the patterns (I think you may have been referring to patterns as minutia)? Anyway, here is a link to read about the value of patterns. http://humanfactors.com/downloads/whitepapers.asp#UIpatterns

 

Another thought of yours, “It can’t compel people to be interested in interacting with your product or service. It can’t make you compelling or really differentiate you from other organizations.” I agree with this thought if I understand this correctly. I recently experienced a vendor trying to sell their solution to integrate into our own. They continued to state they focused on usability… blah, blah, blah. But the proof was in the numbers. We had our stakeholders, representative users and our usability team fill out a scorecard to rate how well they achieved each task scenario (another usability method). It was proven that their tool in fact had additional steps and a hierarchical navigation that was difficult to remember. So, our usability team did not just choose a product because we get “gold stars” . 

 

Your closing comment, “Or put another way, there’s only so far you can get by streamlining the shopping cart on your website.” How do you know that? I realize this is another opinion, but it sounds like you have a reason for this statement. But please read this HFI white paper about Staples.com. http://humanfactors.com/downloads/whitepapers.asp#keepingusers

 

Last is that I am a photographer too. I learned all of the "ancient" techniques when studying for my BFA. For instance, controlled temperatures and timing must be “dead on” for color prints. When loading your own film by hand in complete darkness it can be tricky. Don't overdevelop your film as it will result in prints with a flat tone – not visually appealing. Artists using the photograph as a medium talk a lot about how well an image has been processed and developed. Artists are very good at recognizing the poorly executed techniques and will be the first to keep other artists in line (we hate laziness and sloppy work). 
 

Again, thank you for the opinions! 
Dawn Barber</description>
		<content:encoded><![CDATA[<p>I appreciate your comments about usability. I think it’s important for people in the field hear and understand others’ points of view. It’s stimulating. However, I think this opinion of usability is off the mark and I&#8217;ll respond to a few of your questions and opinions.</p>
<p>You asked this question, “So, why oh why do people in this day age still hold up “usability” as something laudable in product and service design?” I have never experienced being in the limelight simply for being in this field. It’s amazingly hard work to consult with closed-minded people or to travel constantly to cover field studies to gather data while listening to first-hand complaints from users that the performance of the system is frustrating. It’s exhausting to work with developers who are on fire to put you in your place because you try to help them do their jobs. It takes years to prove your worth in this field as it did for my usability team. So, if you hear someone being lauded in this field, they most likely earned it. Recently I heard one of our project managers say, “If I don’t have usability on a project I’m putting it in as a project risk right away”, I sincerely hope any others in our department within earshot did not assume we have a cushy and well liked job.</p>
<p>You opined, “Usability is not a strategy for design success. The efficiency you create in your interface will be copied almost instantaneously by your competitors.” If a competitor copies what we’ve done, that would be their first mistake. You see, different products have different users with different needs (the challenge is determining those needs carefully). Most of the users in our company work remotely at client sites (could be a client warehouse, basement or storage closet). Their needs would be different than those sitting at the same desk each day. How do you optimize a design for specific users? What if our users don’t use a mouse because they may not have the desk space in a closet? Do you design for heavy keyboard usage, great! But what if our users are mature and do not have much experience with hot keys? How do we design the UI to accommodate this? The solution must come from using usability methods. User research from field studies, conceptual inquiry (usability methods) and task analysis get us the patterns (I think you may have been referring to patterns as minutia)? Anyway, here is a link to read about the value of patterns. <a href="http://humanfactors.com/downloads/whitepapers.asp#UIpatterns" rel="nofollow">http://humanfactors.com/downloads/whitepapers.asp#UIpatterns</a></p>
<p>Another thought of yours, “It can’t compel people to be interested in interacting with your product or service. It can’t make you compelling or really differentiate you from other organizations.” I agree with this thought if I understand this correctly. I recently experienced a vendor trying to sell their solution to integrate into our own. They continued to state they focused on usability… blah, blah, blah. But the proof was in the numbers. We had our stakeholders, representative users and our usability team fill out a scorecard to rate how well they achieved each task scenario (another usability method). It was proven that their tool in fact had additional steps and a hierarchical navigation that was difficult to remember. So, our usability team did not just choose a product because we get “gold stars” . </p>
<p>Your closing comment, “Or put another way, there’s only so far you can get by streamlining the shopping cart on your website.” How do you know that? I realize this is another opinion, but it sounds like you have a reason for this statement. But please read this HFI white paper about Staples.com. <a href="http://humanfactors.com/downloads/whitepapers.asp#keepingusers" rel="nofollow">http://humanfactors.com/downloads/whitepapers.asp#keepingusers</a></p>
<p>Last is that I am a photographer too. I learned all of the &#8220;ancient&#8221; techniques when studying for my BFA. For instance, controlled temperatures and timing must be “dead on” for color prints. When loading your own film by hand in complete darkness it can be tricky. Don&#8217;t overdevelop your film as it will result in prints with a flat tone – not visually appealing. Artists using the photograph as a medium talk a lot about how well an image has been processed and developed. Artists are very good at recognizing the poorly executed techniques and will be the first to keep other artists in line (we hate laziness and sloppy work). </p>
<p>Again, thank you for the opinions!<br />
Dawn Barber</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interesting UX/UCD Reads for the Week at Mobimeet</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176036</link>
		<dc:creator>Interesting UX/UCD Reads for the Week at Mobimeet</dc:creator>
		<pubDate>Thu, 24 Jan 2008 19:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176036</guid>
		<description>[...] Why usability is a path to failure by Todd Wilkens &#8230;So, why oh why do people in this day age still hold up “usability” as something laudable in product and service design? Praising usability is like giving me a gold star for remembering that I have to put each leg in a *different* place in my pants to put them on. (Admittedly, I *do* give my 2 year old daughter a gold star for this but then she’s 2.) Usability is not a strategy for design success. The efficiency you create in your interface will be copied almost instantaneously by your competitors. Recently, I’m even coming to believe that focusing on usability is actually a path to failure. Usability is too low level, too focused on minutia. It can’t compel people to be interested in interacting with your product or service. It can’t make you compelling or really differentiate you from other organizations. Or put another way, there’s only so far you can get by streamlining the shopping cart on your website&#8230;  [read&#8230;] [...]</description>
		<content:encoded><![CDATA[<p>[...] Why usability is a path to failure by Todd Wilkens &#8230;So, why oh why do people in this day age still hold up “usability” as something laudable in product and service design? Praising usability is like giving me a gold star for remembering that I have to put each leg in a *different* place in my pants to put them on. (Admittedly, I *do* give my 2 year old daughter a gold star for this but then she’s 2.) Usability is not a strategy for design success. The efficiency you create in your interface will be copied almost instantaneously by your competitors. Recently, I’m even coming to believe that focusing on usability is actually a path to failure. Usability is too low level, too focused on minutia. It can’t compel people to be interested in interacting with your product or service. It can’t make you compelling or really differentiate you from other organizations. Or put another way, there’s only so far you can get by streamlining the shopping cart on your website&#8230;  [read&#8230;] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Montgomery</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176026</link>
		<dc:creator>Gordon Montgomery</dc:creator>
		<pubDate>Thu, 24 Jan 2008 05:28:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176026</guid>
		<description>What a blatant original post aimed to cause outrage. For sham(e). 
Shocking that so many agreed like sheep. Praise indeed to Jared for cutting to the core...maybe I'll get into brainsparks again...anyway...IMHO it's all about the range of tools in your tool box...anything in isolation can be deadly but beautiful in combination (H2O?)</description>
		<content:encoded><![CDATA[<p>What a blatant original post aimed to cause outrage. For sham(e).<br />
Shocking that so many agreed like sheep. Praise indeed to Jared for cutting to the core&#8230;maybe I&#8217;ll get into brainsparks again&#8230;anyway&#8230;IMHO it&#8217;s all about the range of tools in your tool box&#8230;anything in isolation can be deadly but beautiful in combination (H2O?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Gulick</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176024</link>
		<dc:creator>Ray Gulick</dc:creator>
		<pubDate>Thu, 24 Jan 2008 02:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-176024</guid>
		<description>&lt;em&gt;Talk about missing the point!&lt;/em&gt; (Or are you just kidding?) Attention to usability does not lead to great design: anyone who has visited Jakob Neilsen's website knows that. However, beautiful design coupled with poor usability is of little value either. What good is a beautiful website that is difficult for its intended audience to use? The argument is akin to saying that making sure the lugnuts on the wheels are tight leads to ugly cars.</description>
		<content:encoded><![CDATA[<p><em>Talk about missing the point!</em> (Or are you just kidding?) Attention to usability does not lead to great design: anyone who has visited Jakob Neilsen&#8217;s website knows that. However, beautiful design coupled with poor usability is of little value either. What good is a beautiful website that is difficult for its intended audience to use? The argument is akin to saying that making sure the lugnuts on the wheels are tight leads to ugly cars.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaanon</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-175609</link>
		<dc:creator>Kaanon</dc:creator>
		<pubDate>Thu, 20 Dec 2007 00:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-175609</guid>
		<description>It's because it's very difficult to make thing usable. Most designers (especially developers forced into design) have trouble with it. Most "makers" are inherently more advanced than their users, so something that may be completely usable to them may not be usable to others. This is a non-topic.</description>
		<content:encoded><![CDATA[<p>It&#8217;s because it&#8217;s very difficult to make thing usable. Most designers (especially developers forced into design) have trouble with it. Most &#8220;makers&#8221; are inherently more advanced than their users, so something that may be completely usable to them may not be usable to others. This is a non-topic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Missing the point &#171; World of Usability</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-169632</link>
		<dc:creator>Missing the point &#171; World of Usability</dc:creator>
		<pubDate>Thu, 06 Dec 2007 16:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-169632</guid>
		<description>[...] Shane points to an anti-usability blog entry from Todd Wilkens on Adaptive Path. Shane says, &#8220;He [Todd] likens the quest for better [...]</description>
		<content:encoded><![CDATA[<p>[...] Shane points to an anti-usability blog entry from Todd Wilkens on Adaptive Path. Shane says, &#8220;He [Todd] likens the quest for better [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adaptive path » blog » Todd Wilkens » Why usability is a path to failure &#171; turnings</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-167711</link>
		<dc:creator>adaptive path » blog » Todd Wilkens » Why usability is a path to failure &#171; turnings</dc:creator>
		<pubDate>Mon, 03 Dec 2007 16:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-167711</guid>
		<description>[...] path » blog » Todd Wilkens » Why usability is a path to&#160;failure  3 12 2007    adaptive path » blog » Todd Wilkens » Why usability is a path to failure: Recently, I’m even coming to believe that focusing on usability is actually a path to failure. [...]</description>
		<content:encoded><![CDATA[<p>[...] path » blog » Todd Wilkens » Why usability is a path to&nbsp;failure  3 12 2007    adaptive path » blog » Todd Wilkens » Why usability is a path to failure: Recently, I’m even coming to believe that focusing on usability is actually a path to failure. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scottberkun.com &#187; Usability is not a verb</title>
		<link>http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-167672</link>
		<dc:creator>scottberkun.com &#187; Usability is not a verb</dc:creator>
		<pubDate>Mon, 03 Dec 2007 12:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/07/17/why-usability-is-a-path-to-failure/#comment-167672</guid>
		<description>[...] Why usability is a path to failure (Read the comments) [...]</description>
		<content:encoded><![CDATA[<p>[...] Why usability is a path to failure (Read the comments) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
