<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: Designing for Faceted Search</title>
	<atom:link href="http://www.uie.com/brainsparks/2009/04/28/uietips-faceted-search/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2009/04/28/uietips-faceted-search/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Wed, 19 Jun 2013 09:10:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Brian Robson</title>
		<link>http://www.uie.com/brainsparks/2009/04/28/uietips-faceted-search/comment-page-1/#comment-152672</link>
		<dc:creator>Brian Robson</dc:creator>
		<pubDate>Mon, 06 Sep 2010 00:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=812#comment-152672</guid>
		<description>It seem to me that if you have three facets and each has five possibilities, that gives 125 combinations and not 243 as given in the article.</description>
		<content:encoded><![CDATA[<p>It seem to me that if you have three facets and each has five possibilities, that gives 125 combinations and not 243 as given in the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephanie Lemieux</title>
		<link>http://www.uie.com/brainsparks/2009/04/28/uietips-faceted-search/comment-page-1/#comment-147163</link>
		<dc:creator>Stephanie Lemieux</dc:creator>
		<pubDate>Tue, 23 Jun 2009 18:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=812#comment-147163</guid>
		<description>These are really great comments - appreciate the feedback...
I also got a great question about ordering facets that I answered on my blog (sethearley.wordpress.com).
I&#039;ll be sure to take these two points into consideration in a follow-up piece!
Thanks,
Stephanie</description>
		<content:encoded><![CDATA[<p>These are really great comments &#8211; appreciate the feedback&#8230;<br />
I also got a great question about ordering facets that I answered on my blog (sethearley.wordpress.com).<br />
I&#8217;ll be sure to take these two points into consideration in a follow-up piece!<br />
Thanks,<br />
Stephanie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melissa Cooper</title>
		<link>http://www.uie.com/brainsparks/2009/04/28/uietips-faceted-search/comment-page-1/#comment-147066</link>
		<dc:creator>Melissa Cooper</dc:creator>
		<pubDate>Fri, 19 Jun 2009 04:18:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=812#comment-147066</guid>
		<description>Hi Jared, 
I&#039;ve just read your article and the one by Stephanie Lemieux regarding faceted search. I&#039;d have really liked to comment directly on her article... Loads of thought provoking stuff. 
 
I&#039;ve been involved in various faceted search projects on classified sites, and have since begun really thinking about employing my learning on the mobile platform. Obviously the solution needs to be quite different, but I think some of the considerations are the same. Are you aware of any articles on this?

One thing I think tends to get overlooked with faceted search is designing for many *and* few results. Most articles I&#039;ve seen on faceted search really focus on narrowing search results. However, we should bare in mind that faceted search also allows users to broaden their results as needed. This is really important if a single facet dramatically changes the range of content available in combination with another facet. Faceted item counts are really important as well as designing suggestions for no results, or very few. 

In summary, I think more thought in this area needs to go towards designing for few results. Especially as there are more entry points with navigational elements such as tagging that can bring a user to search result formats. 

Regards,
@mississa</description>
		<content:encoded><![CDATA[<p>Hi Jared,<br />
I&#8217;ve just read your article and the one by Stephanie Lemieux regarding faceted search. I&#8217;d have really liked to comment directly on her article&#8230; Loads of thought provoking stuff. </p>
<p>I&#8217;ve been involved in various faceted search projects on classified sites, and have since begun really thinking about employing my learning on the mobile platform. Obviously the solution needs to be quite different, but I think some of the considerations are the same. Are you aware of any articles on this?</p>
<p>One thing I think tends to get overlooked with faceted search is designing for many *and* few results. Most articles I&#8217;ve seen on faceted search really focus on narrowing search results. However, we should bare in mind that faceted search also allows users to broaden their results as needed. This is really important if a single facet dramatically changes the range of content available in combination with another facet. Faceted item counts are really important as well as designing suggestions for no results, or very few. </p>
<p>In summary, I think more thought in this area needs to go towards designing for few results. Especially as there are more entry points with navigational elements such as tagging that can bring a user to search result formats. </p>
<p>Regards,<br />
@mississa</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elizabeth Pek</title>
		<link>http://www.uie.com/brainsparks/2009/04/28/uietips-faceted-search/comment-page-1/#comment-146180</link>
		<dc:creator>Elizabeth Pek</dc:creator>
		<pubDate>Wed, 29 Apr 2009 23:27:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=812#comment-146180</guid>
		<description>Hi Jared, I work at one of Australia&#039;s leading media organisations. We&#039;ve recently implemented faceted search through out our major websites including our rich information news sites (eg. www.smh.com.au) as well as our utility sites (eg. www.drive.com.au).

Your design dos and don&#039;ts definitely resonated with us and definitely agreed that you need to build your taxonomy with faceted search in mind. One key learning that we&#039;ve gained from the project on drive.com.au is that choosing the right interface for the search starting point is also very important in helping users discover the &#039;right&#039; content.

To help people find their dream car, we initially implemented a single keyword search interface (like Google) together with faceted navigation as our new search model on drive.com.au. We thought that the single keyword search interface would allow flexibility (eg. search for types such as &#039;Sedan&#039;, or by makes and models). A single keyword box was also considered by the team to be intuitive and familiar - given that it&#039;s synonymous with Google&#039;s search.

At the time of the project, there were much debate amongst the business owners whether this was a right decision. One group felt that this new &#039;Google&#039; style interface model was too different from the other search interfaces in the automotive category in Australia. They felt for the car category - giving users a more &#039;structured&#039; starting point such as drop downs of makes and models would be better.

We decided that the best way to solve the debate was by testing with users in real contexts and in real time. So we conducted a multivariate test of these two interfaces in our live environment.

To our surprise, the Google style interface produced the least business value (as measured by the number of pages consumed and number of leads generated to the advertiser) and that the hybrid version of keyword search box as well as drop downs of makes and models produced the best overall net revenue result.

We also conducted one-on-one usability testing to see what was going on here. We observed that the hybrid version is successful because it catered for users&#039; various levels of car knowledge and familiarity with a faceted search model.

I presented this as a case study at one of our industry conferences last year where I talked about user&#039;s readiness for faceted search. My slides from this conference are available here: 
http://www.slideshare.net/epek/are-users-really-ready-for-faceted-search-presentation

Just thought I&#039;d share this experience with you and your readers.

Cheers,
Elizabeth Pek
Head of User Experience
Fairfax Digital
Sydney, Australia</description>
		<content:encoded><![CDATA[<p>Hi Jared, I work at one of Australia&#8217;s leading media organisations. We&#8217;ve recently implemented faceted search through out our major websites including our rich information news sites (eg. <a href="http://www.smh.com.au" rel="nofollow">http://www.smh.com.au</a>) as well as our utility sites (eg. <a href="http://www.drive.com.au" rel="nofollow">http://www.drive.com.au</a>).</p>
<p>Your design dos and don&#8217;ts definitely resonated with us and definitely agreed that you need to build your taxonomy with faceted search in mind. One key learning that we&#8217;ve gained from the project on drive.com.au is that choosing the right interface for the search starting point is also very important in helping users discover the &#8216;right&#8217; content.</p>
<p>To help people find their dream car, we initially implemented a single keyword search interface (like Google) together with faceted navigation as our new search model on drive.com.au. We thought that the single keyword search interface would allow flexibility (eg. search for types such as &#8216;Sedan&#8217;, or by makes and models). A single keyword box was also considered by the team to be intuitive and familiar &#8211; given that it&#8217;s synonymous with Google&#8217;s search.</p>
<p>At the time of the project, there were much debate amongst the business owners whether this was a right decision. One group felt that this new &#8216;Google&#8217; style interface model was too different from the other search interfaces in the automotive category in Australia. They felt for the car category &#8211; giving users a more &#8216;structured&#8217; starting point such as drop downs of makes and models would be better.</p>
<p>We decided that the best way to solve the debate was by testing with users in real contexts and in real time. So we conducted a multivariate test of these two interfaces in our live environment.</p>
<p>To our surprise, the Google style interface produced the least business value (as measured by the number of pages consumed and number of leads generated to the advertiser) and that the hybrid version of keyword search box as well as drop downs of makes and models produced the best overall net revenue result.</p>
<p>We also conducted one-on-one usability testing to see what was going on here. We observed that the hybrid version is successful because it catered for users&#8217; various levels of car knowledge and familiarity with a faceted search model.</p>
<p>I presented this as a case study at one of our industry conferences last year where I talked about user&#8217;s readiness for faceted search. My slides from this conference are available here:<br />
<a href="http://www.slideshare.net/epek/are-users-really-ready-for-faceted-search-presentation" rel="nofollow">http://www.slideshare.net/epek/are-users-really-ready-for-faceted-search-presentation</a></p>
<p>Just thought I&#8217;d share this experience with you and your readers.</p>
<p>Cheers,<br />
Elizabeth Pek<br />
Head of User Experience<br />
Fairfax Digital<br />
Sydney, Australia</p>
]]></content:encoded>
	</item>
</channel>
</rss>
