Re: Screen captures

Subject: Re: Screen captures
From: "Weissman, Jessica" <WeissmanJ -at- abacustech -dot- com>
Date: Sun, 10 Feb 2013 12:20:32 -0500

My personal view is that screen captures generally add little IF the manual is intended for use while the reader is looking at the screen.

Reviewers are often tempted to ask for them because they are using them to visualize the software.

However, if your manual requires some kind of general explanation or if the division of fields into chunks on the screen is conceptually important, a screen shot makes sense.

Full disclosure: I'm one of those people who'd always rather have the 1000 words a picture is worth than the picture itself.

The problem with doing two versions is that there's more work to do than just removing the pictures. All those "as shown in Figure 4" phrases need to be removed, and you may want to be more specific in describing a control or field if there is no screen shot to refer to.

- Jessica
STC Vice President Nicky Bleiel is giving a free webinar on best practices
for creating mobile help.

Learn more:


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


Screen captures: From: Anonymous

Previous by Author: Does anybody else support Serena Business Mashups / Business Manager or other Serena solutions?
Next by Author: RE: Recruiting dilemma
Previous by Thread: Screen captures
Next by Thread: Re: Screen captures

What this post helpful? Share it with friends and colleagues:

Sponsored Ads