![]() ![]() When your end users don't quite know what to search for, they can browse your documentation to find an answer. It's when you have over 20 or 30 articles that you really want to make a nice Table of Contents - especially if your documentation is online. If you only have 10-20 articles, then you don't really need to make them easy to browse. Otherwise, end users waste time searching for what you just referenced. When you reference another action, product, workflow, or term, it always helps to include a link to the related article. The step-by-step instructions are great for the quick reminder. But after the initial training, end users don't need to watch the entire video again - they just need a quick reminder of what to do. The video acts as a teacher to explain an overall process and provide some initial training. This is a great way to do end user documentation. If you have the budget, the patience, and the time, you can do what Wistia does - create a video explanation, then include step-by-step instructions underneath the video. Adding an arrow, a circle, or number sequences can make end user documentation completely dummy proof, and save end users from having to figure out what to do.Įven if it seems obvious to you where to click, including a few simple annotations will go a long way in removing confusion. The majority of end user documentation should have screenshots, and those screenshots should include some sort of annotation. Plus, you can always combine a lot of little articles into a larger workflow and organize them into a chapter or a manual. These are so much easier to write, and your end users will find them much more useful because they can quickly search for, and find, answers to their specific questions (end users need specifics). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |