- What is SharePoint 2010? Vision and Reality
view comments - Knowledge Management in 2012? Probably Dead
view comments - Myths & Realities of Drupal
view comments - iPad 3 vs. New Samsung Tablet: War Starts in February
view comments - 5 Signs Your Company Doesn't Get Social Business
view comments - 5 Critical Steps to SharePoint Information Architecture Planning
view comments - Is There A Business Case For Using SharePoint as an Enterprise CMS?
view comments - Alfresco Enterprise 4: Social, Collaborative, Mobile, Cloud Connected Content Management
view comments
Producing Great Search Results: Harder than It Looks (Part 2)
Creating an effective search results page takes hard work. In the first installment of this article, I introduced how designers need to understand the users' tasks and ensure every result delivers great scent. In this installment, I'll elaborate on the specific principles of the scent of information that play an important role when designing search results.
Prevent Pogosticking
The search results page is just a flavor of a gallery page — one produced dynamically from the query. One important property of gallery pages is they need to eliminate the need for the user to pogostick. This is just as true for search result pages.
Pogosticking is what happens when a user jumps from the gallery page to an individual content page and back, like a child on the spring-based toy of the same name — up and down, up and down. At first glance, letting a user bounce between the search results, to locate the specific content they seek, may seem like a good idea. After all, they can explore the offerings and find the one that best fits their needs.
However, our research has shown otherwise. When we've studied e-commerce sites, we found 66% of purchases on sites happened without any pogosticking at all. This meant that users were deciding what to purchase from the gallery page, and not clicking into the product detail page until after they'd decided what to buy.
In fact, the more they pogosticked, the less likely the session would result in a purchase. Pogosticking doesn't promote exploration of the offers — it gets in the way of it. We found the same behaviors when we studied non-e-commerce sites: the more pogosticking we observed, the less likely the user found content they were happy with.
The best search results pages will prevent pogosticking by providing the relevant content before the user chooses a specific result.
Most Relevant Links Should Be First
As we watched users interact with search results, we quickly noticed a recurring pattern. Users lose momentum as the apparent relevancy of the results go down.
They scan the results from top to bottom. As they encounter each result, they make an assessment on whether it's close to what they are looking for. As they encounter a result that seems less relevant, they start to slow down.
Then, an interesting thing happens. At some point, they start to look back up at the top of the results, only concentrating on that top area. This is when they've hit their relevancy threshold.
The best sites keep the most relevant results at the top. This is a challenge, as relevancy is very related to the task. If the relevancy depends on a sortable or filterable attribute, such as price or location, then providing tools to do that can be helpful. However, that means the tools themselves have to be easy to find and use.
For example, Kayak.com uses prominent sliders in their left margin to filter, and clearly displays sorting criteria at the top of the results listing. The efforts of skilled visual and interaction designers can make a big difference in the effectiveness of page.

Eliminate the Wacko Results
Nothing slows the user's scanning momentum more than encountering results that are irrelevant, or as we like to call them, "Wacko." (We started calling these wacko results when one of our test participants kept repeating, "I can't believe these wacko results." The name has just stuck with us.)
The problem with Wacko results is users can't understand why the system is presenting them. They don't realize that it's algorithmic. That the engine is using some magical formula to retrieve the results and, to the algorithm, these results seem very likely related.
Continue reading this article:
Featured Events View all
| Add event
|
RSS
- Feb 22, 2012 – Intelligent Content Palm Springs 2012
- Feb 26, 2012 – SPTechCon - Sharepoint Conference San Francisco 2012
- Feb 28, 2012 – (Webinar) How to Build Great Mobile Websites
- Mar 6, 2012 – Get Social with Microsoft & Telligent in Dallas
- Mar 8, 2012 – Get Social with Microsoft & Telligent in New York
Who's Hiring? View all
| Post a job
|
RSS
- Web Content Manager in Newport Beach at Orange County Museum of Art
- Principal Business Consultant in Paris at Saba
- Director of Customer Success Management in Nova Scotia at Radian6
- Software Engineer -- Media Solutions in Bucharest at Adobe
- Technical Writer in Charleston at Blackbaud
- Interaction Designer in Maryland at Inmedius
- Project Manager in London at Brandworkz
- Sales Director, Consumer Electronics at Synacor

Receive
the Free CMSWire Newsletter
Email It