IA Heuristics for Search Systems

Another day, another project, another set of IA heuristics. A client asked me to kick the tires of their search system, so I decided to expand on the search aspects of the information architecture heuristics that we came up with a couple weeks back.

This time, I tried to align and categorize these guidelines with some common steps users take when searching a site. This semi-sequence goes like this:

  1. Locating search: Where is it?
  2. Scoping search: What will be searched?
  3. Query entry: How can I search it?
  4. Retrieval results: What did I find?
  5. Query refinement: How can I search some more?
  6. Interaction with other IA components: Can I switch to browsing when search isn’t doing the trick?
  7. Finishing search: What can I do now that I’ve done searching?

It might go without saying that these search heuristics are really geared to semi-structured text, not data; looking for ideas and concepts is a different undertaking than hunting for facts and figures (more on why they’re different). Although there is definitely overlap, I’d love to see some references to data retrieval heuristics; if you know of any, or want to create your own set, please link to it in a comment below.

OK, without further ado…

Locating Search

  1. Is the search interface located where you’d expect it to be? (Top of the page, and/or with other site-wide navigation options.)
  2. Is the search interface always in that location? (It’s always available, and always in the same place.)
  3. Does the search interface behave consistently?

Scoping Search

  1. Does it communicate what content is being searched?
  2. Does it search what it should? (Users often assume that search covers all of an organization’s content.)
  3. Does it support search zones when appropriate? (Users may want the ability to search a specialized subset of content, such as products or a staff directory.)
  4. Does the interface make it easy to select search zone options? (Long pull-down menus and overwhelming arrays of checkboxes are both quite common.)
  5. Is contextual help with search zones available?

Query Entry

  1. Is it obvious where in the search interface to enter a query? (Multiple search boxes can be confusing.)
  2. Is it easy to enter a query? (Users can simply enter terms; more complex queries are addressed by showing examples or by allowing users to enter complex queries in syntaxes that may be familiar to them.)
  3. Is the search box long enough to handle common query lengths? (Search log analysis can tell you how long most queries are.)
  4. Are query builders used effectively (For example, spell-checking, stemming, concept searching, and thesaural searching; good choice of which builders are hidden, visible.)
  5. Are syntaxes available that are appropriate for this site’s users? (Certain groups of users may prefer to use wildcards, Boolean operators, proximity operators, etc.)
  6. Are stopwords–semantically poor search terms (e.g., “the,” “a,” “her”)–automatically removed from queries?
  7. Is it obvious how to submit a query for processing? (The “search” or “submit” button is easy to find and is labeled clearly.)
  8. Is contextual help with query entry available?

Retrieval Results

  1. Is it clear what the query just entered was? (Most search engines can repeat the original query.)
  2. Is it clear what was searched? (Especially important if your site employs search zones.)
  3. Is it clear how many results were retrieved?
  4. Can the number of results per page be configured by the user?
  5. If search zones or federated search is employed, is it clear which zones results came from?
  6. Are useful results available at the top of the list? (Wouldn’t that be nice? Hard to test though.)
  7. Do the most common queries produce useful results? (You can tell common queries from search log analysis; Best Bets are a great way to ensure useful results for those common queries.)
  8. Are useful components displayed per result that help users select a relevant result? (These should help users understand enough about a result to distinguish it from others; known-item searches may benefit from displaying different and fewer components than open-ended searches.)
  9. Are results listed in a useful way? (Sorting options might be quite helpful; listing each result’s relevance score might be confusing.)
  10. Are the results grouped in a useful way? (Usually results aren’t grouped at all, but clustered results are becoming more and more common.)
  11. Are categories for browsing displayed? (Yahoo is a great example of this practice.)
  12. Are duplicate results removed? (Especially an issue with federated search.)
  13. Is one result shown per document? (Often a document has been broken into separate files for display purposes; this floods result lists with duplicate results.)
  14. Is contextual help available to help users understand how their results were determined?

Query Refinement

  1. Is there a more powerful search interface available to help users refine their searches? (Often known as “Advanced Search,” but my plea: use “Refine Search” or “Revise Search”.)
  2. Does this interface display the original search and make it easy to edit?
  3. If a user chooses to narrow search results, are there easy and logical ways to do that? (The logical way to narrow may mean re-executing the query against only certain types of documents–“just technical specs please”), or searching within the current group of results; if so, is this easy to do?)
  4. If a user chooses to expand search results, are there easy and logical ways to do that?
  5. Is contextual help available to help users understand how to refine their query?

Interaction with Other IA Components

  1. Is a search interface available when and where other IA components fail? (For example, allow users switch to search when they’re about to give up on browsing.)
  2. Does the search system take advantage of document tagging (i.e., metadata) to improve the relevance of results?
  3. Does the search system take advantage of document tagging to improve the display of results? (Metadata can be used to display clustered results.)

Finishing Search

  1. Can the user easily leave search and start browsing for relevant content?
  2. Can a group of results be saved? (A group might be all of the results retrieved, or a subset that the user has selected.)
  3. Can a group of results be emailed?
  4. Can a query be saved for future use?
  5. Can a saved query be designed to be executed on a regular basis? (This is useful for keeping up with dynamic content, like news.)
  6. Is contextual help available to help users understand what they can do with the results they’ve retrieved?

Naturally, I’d love your comments/additions/deletions/etc.; I’m sure I’ve left out some obvious ones. Would you use a different set of categories than the sequential ones I’ve used here?

윗 글의 저자 사이트 : http://louisrosenfeld.com/

답글 남기기

이메일은 공개되지 않습니다. 필수 입력창은 * 로 표시되어 있습니다.