Discussion Board posting: Instructional Video articles

The journal articles Eight Guidelines for the Design of Instructional Videos for Software
Training and New Modes of Help: Best Practices for Instructional Videos had different
audiences. Where the audience of the Eight Guidelines article was composed of people who are
seeking how to information about a wide variety of software tasks (206), the Best Practices
article was aimed at DIYers interested in a multitude of subjects (not limited to software
instruction), particularly those who resist using print instructions (196).
The videos in the Eight Guidelines article appear on company websites, such as Adobe, Apple,
HP, Microsoft, IBM and others (206). The article also indicated that users may publish
instructional videos to a variety of websites, such as Instructables, WikiHow, eHow, Howcast,
Videojug, Vimeo, and YouTube (206). The Best Practices video mentioned videos appearing on
company websites like Adobe and Techsmith, but mostly focused on videos on YouTube (196).
The Eight Guidelines article suggested that software instructional videos should consist of a
recorded demonstration of the software being used to accomplish a task, with a voice-over that
points out the software components (icons, menus, locations) and how the user interacts with the
computer (user input and system reaction) (206-207). The Best Practices article suggested that
DIY videos should include title slides, visual and verbal pointing (arrows, callouts, this and
that, zooms, pans) and that viewability should be good with video that is not shaky or blurry,
and audio that is not garbled, and that cues the visual elements to come by slightly preceding the
video. The Best Practices article also pointed out that content should be accurate and the video
should provide a preview so that viewers know the goal from the outset. Additionally, the Best
Practices article suggested some repetition to make sure important points are not missed (200201). Furthermore, the Best Practices article advised rehearsing the script to ensure a smooth
delivery (204).
The implications for my video are that it needs to be a recorded demonstration of the software
task I have written about (not a video about the software features, rather a video that shows how
to use the software to perform a specific task). It needs to show each step, as well as highlighting
where the user is going to find items on the screen and how the computer will respond as they
complete the steps. Im going to want to preview the task at the beginning of the video, complete
the steps in a logical order, keeping them short and easy to follow. My voice-over will need to
match whats happening on the screen. In addition to content and quality of the instructions, I
will want to focus on the technical aspects of creating quality video and audio. Im going to want
use the editing tools well to ensure I produce a quality end product. Im going to need to rehearse
my script and practice completing the instructional steps, so that I am not stumbling over my
words or suffering from awkward pauses.
I didnt really see contradictory advice between the two journal articles. Both articles touched on
previewing the task. The Eight Guidelines article really seemed to focus more on the nuts and
bolts of the content of the video, whereas the New Modes article seemed to have a greater focus
on the technical aspects of producing quality video and audio. One item that may have been
slightly contradictory between the two articles had to do with matching the audio to the onscreen action. Whereas the Eight Guidelines article advised that the audio and video needed to

match precisely, the New Modes article spoke of having the audio cue what is coming up next
before it appears on screen.
Works Cited
Swarts, J. "New Modes of Help: Best Practices for Instructional Video." Technical
Communication. 59.3 (2012): 195-206. Web.
van der Meij H., and van der Meij J. "Eight Guidelines for the Design of Instructional Videos for
Software Training." Technical Communication. 60.3 (2013): 205-228. Web.