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 would add one other thing. In most cases you should keep it under about three minutes. If you need more than that, consider creating multiple scripts/videos. Time your script against the action to see any glaring spots where there are more words than action (or vice versa)
On Wednesday, October 1, 2014 1:21 PM, kafkascampi <kafkascampi -at- gmail -dot- com> wrote:
When I do a script (as I am in fact procrastinating doing this very moment)
I make a table, with the left side Script and the right side Action. I put
one sentence in each row and usually (but not necessarily) an action to go
with it. This helps visualize how the video will go, what you'll be showing
on the screen at all times.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
