Even though you documented everything with pictures, annotations, and clear text, a common situation you will find is that end users don't reference your documentation.
All of that time invested in creating a knowledge base, yet you continue to waste time fielding the same questions about how to do something in Salesforce (or you get crummy results because folks aren't following directions).
One reason might be that your articles are too long, making it difficult to find relevant information or see important details. To solve this problem, I recommend breaking up long articles that cover a few topics and/or tasks, into mini articles that each answer one specific question.
Articles shouldn't be too long
This is not an everlasting truth - but it is best practice the majority of the time.
Here's an example of an article from my Salesforce knowledge base that was too long. When I wrote it, I figured I would cover adding, removing, and reorganizing the tabs in the top navigation of Salesforce. But after I read through it, I realized it covered too much.
How to Add, Remove, and Arrange Tabs (objects) in top navigation
The article is too long, a little confusing, and if an end user wanted to see just how to rearrange the tabs (not add or remove tabs), he/she would have to read through a lot of information that wasn't pertinent - which means he/she may never find the content. The result is that the end user will either ask me how to do it, or not do it at all.
Break the article up
I decided that this one article should really be three separate, shorter, more specific articles. So I broke them up into the following articles:
- How to add tabs to the top navigation
- How to remove tabs from the top navigation
- How to rearrange tabs in the top navigation
Below is a short video that shows how I did it using ScreenSteps. All I have to do is drag and drop the steps to new articles and my knowledge base is instantly updated.
So if your articles are getting a little long, think about breaking them up into miniature articles, each answering one specific question.
The key to useful documentation
The key to making documentation useful is to make it answer end users' questions - the more specific you can be, the better. In the past, documentation has been pretty general or all encompassing because it took too long to write a lot of little articles. But that's no longer the case.
Writing documentation is easy, so write as much of it as you can, be as specific as you can, and your end users will reference it much more often.