3 ms·
But by the same token, instead of having a FAQ with headings like, "What is the minimum setback for structures?" you could have had a simple document with headi
by thesuitonym 5y ago
But by the same token, instead of having a FAQ with headings like, "What is the minimum setback for structures?" you could have had a simple document with headings like, "Minimum Setbacks for Structures."
One of the points in the document was that you can still have a document that's structured like a FAQ, just don't make it questions, make it answers.
- asdff 5y agoI think part of the faq benefit is that its designed for people who hone in on faq pages already. Some people are not researchers. They are delegators. They'd rather come to your office and ask you "what is the minimum setback for structures" knowing full well its probably listed somewhere on your website/documents/etc, but they'd rather delegate the effort of looking up that information to you. A faq page attempts to catch these people, and say "hey delegators, check here if your question has already been answered first before you spam our customer support." In that case, a document that's like a faq but not a faq won't do you any good. These people will just ignore it like the primary document and pound your customer support resources.