<?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: Differentiation: The New Enterprise Search Barrier</title>
	<atom:link href="http://arnoldit.com/wordpress/2009/10/30/differentiation-the-new-enterprise-search-barrier/feed/" rel="self" type="application/rss+xml" />
	<link>http://arnoldit.com/wordpress/2009/10/30/differentiation-the-new-enterprise-search-barrier/</link>
	<description>by Stephen E. Arnold</description>
	<lastBuildDate>Sun, 12 Feb 2012 09:55:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Avi Rappoport, Search Tools Consulting</title>
		<link>http://arnoldit.com/wordpress/2009/10/30/differentiation-the-new-enterprise-search-barrier/comment-page-1/#comment-76618</link>
		<dc:creator>Avi Rappoport, Search Tools Consulting</dc:creator>
		<pubDate>Fri, 30 Oct 2009 18:22:12 +0000</pubDate>
		<guid isPermaLink="false">http://arnoldit.com/wordpress/?p=9156#comment-76618</guid>
		<description>Steve,

People I respect,  like Don Norman, Lou Rosenfeld and Peter Morville have been using the term &quot;user experience&quot; for years, and it means something specific, which needed a name.

&quot;User interface&quot; is the browser or desktop app, with menus and form fields and so on. &quot;Functionality&quot; is the back-end functionality: in search, that&#039;s the query, retrieval and relevance algorithms.  The whole lot of it put together is the UX, (user experience).   If that&#039;s not right, why bother?  You can have a gorgeous design and a fantastic algorithm, but if the UX fails, the search fails.

Not that I necessarily want vendors to blather about it, but I do want some of them to understand UX, to make sure their systems can be usable instead of forcing the customers to do it all individually.

Avi</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>People I respect,  like Don Norman, Lou Rosenfeld and Peter Morville have been using the term &#8220;user experience&#8221; for years, and it means something specific, which needed a name.</p>
<p>&#8220;User interface&#8221; is the browser or desktop app, with menus and form fields and so on. &#8220;Functionality&#8221; is the back-end functionality: in search, that&#8217;s the query, retrieval and relevance algorithms.  The whole lot of it put together is the UX, (user experience).   If that&#8217;s not right, why bother?  You can have a gorgeous design and a fantastic algorithm, but if the UX fails, the search fails.</p>
<p>Not that I necessarily want vendors to blather about it, but I do want some of them to understand UX, to make sure their systems can be usable instead of forcing the customers to do it all individually.</p>
<p>Avi</p>
]]></content:encoded>
	</item>
</channel>
</rss>

