Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A When is a screenshot really useful in training documentation?

It all comes down to the familiarity of the audience with the interface. The words of a procedure describe parts of the interface. Will the audience immediately recognize which parts of the interfa...

posted 8y ago by Mark Baker‭  ·  last activity 5y ago by System‭

Answer
#4: Attribution notice removed by user avatar System‭ · 2020-01-03T20:41:49Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/23390
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added by user avatar System‭ · 2019-12-08T03:27:17Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/23390
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar System‭ · 2019-12-08T03:27:17Z (almost 5 years ago)
It all comes down to the familiarity of the audience with the interface. The words of a procedure describe parts of the interface. Will the audience immediately recognize which parts of the interface those words refer to? If yes, then screenshots are unnecessary and will simply slow the reader down. If no, then you need a way to show the reader which part of the interface the words refer to, and a screenshot is one way to do that.

As computers have become more ubiquitous, interfaces have become more standardized, and people do more and more activities on the computer, people have become more familiar with interfaces and thus more likely to recognize what the words in the procedure refer to. Thus we have more shortcuts like File \> Print, because people now know what that means.

There is a universal phenomena here: as products become ubiquitous and users become experienced with them, the need for documentation diminishes, and may eventually disappear altogether. Thousands of products ship with no documentation other than that demanded by lawyers. It is all about where your product fits on the familiarity scale with its intended audience. This affects far more than just the decision about screenshots.

But there are still specific cases in which the audience may not know what the words in the procedure mean. If the audience is inexperienced or the interface is non-standard, the reader may not recognize what the words mean and you should use screen shots.

In some cases, there may be small parts of the interface that are non-standard, meaning you should use screenshots for those parts and not for others.

In short, therefore, use them where you anticipate that a significant portion of you audience may need them, and otherwise not.

#1: Imported from external source by user avatar System‭ · 2016-06-16T13:27:50Z (over 8 years ago)
Original score: 5