Re: Screen captures
If the only documentation available is a video, the person who created
it is lucky they're not nearby.
"As you can easily see, if we click here (WHERE THE HECK DID YOU CLICK?) we get this (WHAZZAT?) and then this (SHEESH YOU CLICKED INTO THE SECOND THING BEFORE I COULD SEE THE FIRST THING. WHAT IN BLOOMING BAZUNGOSTAN ARE WE SEEING, ANYWAY?)"
In my experience screen captures are needed when the product displays as output a complicated graph, where it's crucial to observe inflection points, outliers, changes in scale, or other minutiae. I've sometimes used a full screen shot with a call-out to the detail. I'm thinking of the situation where the user's actual experience may only vaguely resemble the example given. If you cannot click on the software's screen to get an interpretation of some messy part, then a good illustration can help.
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.
Learn more: http://bit.ly/12LyN2z
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
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
- Re: Screen captures, Laura Lemay
Previous by Author:
Re: Use fully-spelled numbers
Next by Author: Re: Deprecated (was When is it too much information?)
Previous by Thread: RE: Statistics (was Screen captures)
Next by Thread: Re: Screen captures
Search our Technical Writing Archives & Magazine