I have always wanted to enahnce our product documentation by including a a series of short (1-2 minute) how-to videos using Captivate. However, the primary user interface for our product is the command line (CLI.) It obviously does not lend itself very well to how-to videos. Or maybe I am limited in my imagination as to how I show our product users as to what to do with our product. In any case, it is a dream, and I hope that one day it will come true.
In the meantime, here are some problems that people face when creating videos, and a list of tips that folks have shared to be kept in mind when creating videos to improve their usability:
A video set is not seen as an effective help-system because the user/learner will have to manually hunt through dozens and dozens of videos to find what they want. The idea is to have a more genuine help system that's easy to use and easy tosearch.
One can combine the power of videos with that of an organized help system by creating a basic HTMLHelp help system or even a simple collection of interlinked HTML pages, with each topic having one or more "click here to watch a video of how this works" links. This provides a structure to turn a random collection of video clips into an integrated, organized help system.
The biggest problem with videos is that they typically run too fast, particularly for long procedures, so one is forced to view and review and re-review the video multiple times.
To avoid this, here are a couple of tips:
First, include a written summary of the steps before the link to provide an overview of the procedure that "primes" the viewers so they know what they'll be seeing.
Second, make sure to record the video at a slower rate than you'd actually do the work.
If you are recording voice narration* (or text subtitles), make sure to stop at least briefly after each step (or provide video controls that let viewers do this themselves) so viewers can perform that step before continuing.
If you do use voice, add subtitles too or make this an optional setting. Some of your audience will be deaf or hearing impaired, will lack speakers on their computer, or won't be able to hear the narration over the noise in their office.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment