TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I am no longer sure whether screen shots in manuals are useful enough to be worth the trouble of creating them and keeping them up to date. If the reader is in front of the actual screen, the picture in the manual is redundant.
I can think of a few reasons screen shots mght be useful:
- to help readers be sure they're following directions for the right screen
- to help reviewers figure out whether the manual is correct and useful - reviewers usually look at the document in isolation, not in front of the app
- to make the manual more visually attractive
Manuals do look incomplete without the screen shots, but that may just be because we're used to seeing them.
Of course I may be smarting from having to update a whole bunch of screen shots because the developers changed the capitalization on two field labels that appear on a lot of screens. The sharp-eyed reviewer thought it was important enough for me to fix.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-