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'm back with another question. My company is switching some engineering software so they can get better metrics and make 3D and 2D models more intelligent. It is a major philosophy shift. Key team members from each engineering discipline are going through different types of training. Out of that, we need to train the rest of the employees.
The person who is supposed to oversee training thinks video only is the way to go. You can find all kinds of documentation to support that but not much specific to software training (so far).
My position, as an experienced writer, is that you need a blended approach. Video is fine but have some written documentation to go along with it so that users have something to refer to later if they don't want to find or watch a video. Documentation can be in any format so don't get hung up on that. I also think videos should be no longer than 5 to 7 minutes not 15 or longer. Users also need someone available to ask questions and that should be part of the mix.
Based on your experience in the real world, what works for software training.
Ginger Stuckey
Technical Publications - Design
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
