For a long time, I looked at help authoring tools in terms of their single sourcing ability -- creating the source material in the tool, and then outputting to online help, print, and other targets. However, I've given up on the ideal, at least for now. I'm convinced that the new vernacular, as a SXSW podcast called it, is audio and video.
If faced with a decision between learning via written instructions or audiovisual screen demos, which would you prefer? In most situations, I prefer the audiovisual. When learning software, most users want someone to show them how, to sit beside them and walk me through the steps in a lively, dynamic way.
If audiovisual is the new vernacular (look at the proliferation of online videos, podcasts, gaming, webinars, etc.), why are we wasting so much time trying to single source between online help and printed manuals, confining ourselves to the written medium? Instead, the following deliverables might yield better user results:
For too long I've minimized the importance of the audiovisual. Captivate -- the industry standard tool for creating screen demos -- is actually a relatively simple application. Mastering it and integrating audiovisual into user help will take it to the next level.
Get new posts delivered straight to your inbox.
I'm a technical writer based in the San Francisco Bay area of California. Topics I write about on this blog include technical writing, authoring and publishing tools, API documentation, tech comm trends, visual communication, technical writing career advice, information architecture and findability, developer documentation, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here.