FAQs: why we don’t have them
digital.cabinetoffice.gov.uk
digital.cabinetoffice.gov.uk
Here are a few examples of good software FAQs which are entertaining to read in themselves:
https://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_...
http://libguestfs.org/guestfs-faq.1.html (NB: I wrote this one)
Me too. I wonder if geeks (or their cousins "infovores") are more likely to read FAQs, and read them carefully, than the general public; if so, geeks might also be inclined to overestimate the importance of FAQs, or the willingness of non-geeks to read them.
But FAQs for a web application I think is a bad fit, it is generally more useful to have a forum (so you can get real feedback on what is frequently asked) where common questions will bubble to the top more often.
Or if you're big enough, a stackexchange which handles genuinely frequently asked questions better still.
(http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.forewor...)
| A bad [FAQ] sheet is one that is composed not of the questions people actually ask, but of the questions the FAQ's author wishes people would ask. Perhaps you've seen the type before:
Q: How can I use Glorbosoft XYZ to maximize team productivity?
A: Many of our customers want to know how they can maximize productivity through
our patented office groupware innovations. The answer is simple. First, click
on the File menu, scroll down to Increase Productivity, then…
| The problem with such FAQs is that they are not, in a literal sense, FAQs at all. No one ever called the tech support line and asked, “How can we maximize productivity?” [...] [It's] a lot easier to make up imaginary [FAQs] than it is to discover the real ones. Compiling a true FAQ sheet requires a sustained, organized effort [...] It calls for the patient, observant attitude of a field naturalist. No grand hypothesizing, no visionary pronouncements here — open eyes and accurate note-taking are what's needed most.The likelihood of building a site designed in such a way that my answer is immediately obvious within one or two clicks is a far reaching concept.
A recent example is the FAQ on the UK's Bike to Work Scheme website - http://www.bike2workscheme.co.uk/index.php/faqs
Rather than click through the site to find answers to specific questions I went directly to the FAQ and instantly spotted the questions I needed answered.
I get the whole concept of "if you've left questions unanswered from your users then you haven't done a good enough job" however I don't see how an FAQ page could be considered a lazy or ineffectual solution.
There are all sorts of pieces of useful information about a site/product/etc. that simply can't be structured well. That aren't important enough to belong on an about page, or whatever -- where each individual thing is something that only 0.5% of your users will care about, but each thing is a different 0.5%.
Implementing a FAQ cuts drastically on the number of e-mails you receive, which all keep asking the same rare questions -- the "long tail" of questions and content, which aren't important enough to users to be in the main about/etc content.
There's no reason your FAQ can't be structured -- it should have headings and subheadings. Although a lot of information really is just inherently one-off, and hard to structure. That's reality, not laziness.
There is very much a need for a kind of "miscellanea" long-tail about page, which is exactly what a FAQ is.
Plus, some people find the Q&A format to be extremely useful for locating information, much more so that structured product pages. I personally learn a lot from reading FAQ's from start to end.
"What content will I find browsing with att.net? att.net allows you to access the real Web by searching keywords or ..."
I just can't imagine anybody asking that question. Perhaps I lack empathy.
Did you notice "Why we don't have FAQs" starts with: "we're often asked ..."?
I guess my question to the author would be, why not both? Add an FAQ page for the people who prefer that format, while continuing to do what you do now.
You could argue that maybe they don't have time to write them, but then again, they did take the time to write this article. As someone else in this thread pointed out [1], they've already written the FAQ of why they don't have an FAQ, so start there.
However, dealing with complex datasets that can't be categorized well (like some data can exist in multiple categories), or dealing with multiple apps and multiple platforms, things goes chaos and the Gov.uk's design may not work at all.
As for folks who mentioned search, search technologies are not by default accurate like Google. They require a LOT of work to get it right and more likely to fail than work the more complex your datasets get.
To search, one needs some level of initial knowledge or inquiry, and in many realms people lack that initial seed of knowledge.
A search engine input gives you a blank slate. Sometimes you have a nebulous idea of what you need to know but don't know how that fits into the source, so blank slate searching becomes clumsy and hit & miss. FAQs conversely give direction and clarification so can run the dual role of guiding and forming what the user is trying to search as well as being an end point or gateway to the actual knowledge they seek.
This kind of orientation can be valuable if the language of a site is heavily domain based.
Sure, I could get that information other ways, but I don't see anything wrong with including a FAQ in your "about" section, or "tutorial" or "documentation" or wherever the rest of your information is, along with handy links to get more information. FAQ or no, you should have a starting point for people with zero information to learn more about what you're offering.
Still, I am not sure if you really can apply the same logic in a deeply technical document. I have yet to find something that validates that assertion but it is an interesting premise and it will be a welcome surprise.
How about a "FRI" - Frequently Requested Information, with useful content on a simple, well-organized page.
Her premise is that if someone is looking for information and has not found it - it prompts a question ie. "Where is the information I am looking for?" and that indicates your failure to successfully provide that information. Which is true.
However, often-times questions are a result of critical thinking, and their lack shows lack of true understanding of subject material. On other occasions questions are simply technical problems with edge cases of procedures outlined on the website. Such edge cases should not be part of procedures themselves because they would distract 99% of people who do not encounter them.
I maintain the open-source DBMS Firebird FAQ website at http://www.FirebirdFAQ.org. There are some users who browse the website and read the common issues (esp. Newbie section), but 98% of the traffic comes from Google Search. Just use proper page titles and headings and people who want something answered will type it in Google and get your page with an answer.
This works so well, that I even removed my custom search functionality and placed a Google site-search box right at the center of home page.
"That problem really shows in search, where you will end up with duplicate results competing for attention. You are fighting with your own content. That can’t be efficient for you or for users.
"This is actually a problem GOV.UK is experiencing. The content in our support pages is now appearing in search, so we’re stripping away all of the support content we don’t need and making it easier for users to get straight to the things they’re looking for."
The entire article seems like a written excuse explaining that they are not lazy, but have valid reasons not to write and maintain a FAQ section. I guess it was posted to get some mass approval here on HN and show that HN community supports their POV.
Having an FAQ allows you to let the user help themselves, which most are willing to. If not, you at least have an answer you can point them to.
~2 out of 10 users pick the FAQ instead of choosing support directly.
Really? I find them easy to scan -- hell, I prefer them.
That said they're probably not useful on a site with such a broad information base as gov.uk unless they're tagged and presented in an easily searchable manner or confined to specific areas.
A: It means that Twitter agrees.