Frequently Asked Questions (FAQs) are everywhere on the web, used on all kinds of sites and in all kinds of contexts. From their humble beginnings in the early days of Internet newsgroups, FAQs have become a standard way of providing end users with important information.
But there’s a problem: users don’t like FAQs, at least not the way they are presented on many web sites. In usability test sessions I have conducted over the years, test participants have repeatedly made the same two complaints about FAQs:
And sometimes, testers make a third complaint:
In his article, Are You Ready for the New Ruthless User? J. Hruby described the “new ruthless user” as impatient, laser-focused on their task, and looking for the quickest path to the target information. If you are thinking about adding FAQs to your site, it’s worth remembering this behavior.
Just as most users are unlikely to scan more than the first five or six items in a list of search results, they are just as unlikely to scan many more than five or six FAQs. When there are dozens or even hundreds of FAQs, the description “frequently asked” simply isn’t appropriate anymore.
For example, the US Government site for people with Medicare lists 390 FAQs (20 pages of questions), and although these have been categorized, there are 19 different categories to review, some that list 15 or more questions. The user still has to do a lot of work. (Yes, there’s an FAQ search function, but with scoped searches like this it’s easy for users to lose track of the category they are searching.)
Another common problem with FAQs is when the questions posted are not ones any real end users ever asked. Instead, the questions are presented simply to provide an opportunity for marketing happy talk. For example, real end users don’t ask questions like, “How does ABC Inc manage to deliver on time and under budget so consistently?” Or, “How can I use XYZ software to increase our profits and efficiency?”
These are propaganda FAQs, and users will actively avoid them. In contrast, end user FAQs are usually much more specific and focused on solving a particular problem.
Wordiness and other forms of sloppy writing afflict many FAQs, where either the question or the answer, or both, is unclear. The following is one example from a Twin Cities business:
Q. Security level?
A. Added security
Q. Cost during Winter?
A. Save on heating and cooling cost
The text may be mercifully short, but the questions aren’t questions and the answers aren’t answers. It isn’t even clear what the subject is. (This site’s design, unconventional scroll bar, and distracting Flash animation don’t help much either.)
So what are the guidelines for presenting better FAQs?
You can avoid FAQs and still help users find the answers to their questions with good topic-based navigation. Topic indexes work well, because users can simply scan for the keyword that is aligned with their task, and then navigate to the relevant topic page.
More site owners are recognizing that users consider search engines to be answer engines. E*Trade, for example, invites users to “Enter Questions or Keywords” in the Search field. Even if E*Trade is simply offering a good keyword search, they are using their search engine as an effective tool for dialogue with site visitors, allowing them to begin by asking a question, and avoiding a lengthy list of FAQs. (Yahoo Answers takes this a step further.)
Be sure to get user feedback on your FAQs, your navigation, and your search through usability testing. This is the best way to learn what your users really want from your site.