The following are the steps I follow to create a video:

1. Plan
   1. Understand the requirement
   2. Identify the audience
   3. Create a storyboard
   4. Write the script
   5. Validate the “story” with the customer before getting into execution mode
2. Execute
   1. Shoot the video using a screen capture / recording tool
   2. Create animation slide (if applicable)
   3. Create Title and Summary screens
   4. Convert raw footage into a video project
   5. Record voiceover
   6. Edit and sync audio – this could be voiceover or background score or both
   7. Publish video in suitable format
3. Deliver
   1. Obtain feedback
   2. Develop final version

I use Camtasia from TechSmith to create my videos. So some of the steps or terms (like project) I use may be specific to Camtasia. However, irrespective of the tool you use, you will definitely have to complete the steps explained above. The terminology and sometimes the order in which you approach them perhaps may change depending on the tool(s) you use. For example, if you use a stand-alone application to record voice, you may not necessarily have to do that after creating the raw footage of the video as I have stated.
I will talk about each of these steps in greater detail in the posts to come.

In my last post I talked about how videos can add a whole new dimension to your documentation efforts and help you connect with customers, users, and prospects. If you think making videos is difficult, I want you to think again. Yes, making videos requires skill, creativity, and of course proficiency in using tools of the trade. But it’s no rocket science.

I made my first corporate video about 5 years ago. It was a marketing-cum-training video for a suite of products developed by my then-employer. I then went on to create a range of short How-To training videos that in essence covered all aspects of working with the products. It took a lot of time to get them done, particularly the first one. I think I spent almost a month on it.

I guess it took that long because that was the first time somebody was trying to make a video in the organization. I had nobody to look up to for guidance and more importantly, I did it as an “initiative” – not part of my regular appraisable tasks for the quarter.

Over the years, I have made several videos and have learnt to avoid mistakes that I used to make in the past. The quality of both the visuals and the audio is improving; and I must confess that I still have a long way to go. There is nothing like attaining perfection and you will always find somebody who can do it better than you. But that doesn’t deter me and I don’t want it to deter you either.

In my next post, I will share with you the steps I usually follow while creating videos. Do come back and read on.

TechWritingLabs is on YouTube.

http://www.youtube.com/user/TechWritingLabs.

I plan to post videos at regular intervals. I am also planning to continue the Tutorial series – first for MS Word and then for other tools relevant to technical writing as well.

Do check out the videos and let me know if you like them..

Videos have gained unprecedented popularity. I am not talking about the entertainment videos. I am talking about corporate videos – product videos, training videos, company profile videos, company presentations in video format.

Is this craze for videos just another passing phase or are they here to stay?

I believe in the latter – in fact I think this is just the beginning and that videos are soon going to take the domain of documentation and training by a storm. Of course, I don’t agree with those who say that videos will soon replace “written documentation”; I think videos and written documentation (in print or online format) will co-exist with videos being the primary touch point for user seeking help / information.

Perhaps a couple of years ago, when you needed help using a product, you would turn to the user manual for help. Today, if I were to purchase some product, I am quite likely to search sites like YouTube to see if I can “see the solution” to the problem rather than read it in the manual.

For example, I recently bought a new cell phone and found that it was so hip that I couldn’t even figure out how to open it to put the battery inside (It takes all kinds of stupid people, like me, to make the world!) I was too scared to try anything rash with the expensive piece and the 2D picture in the user manual didn’t help much really. So, all I did was log on to YouTube to see how someone else somewhere else in the world had solved the problem I was having. In less than 4 minutes I had found my solution!

This example applies to companies too. When looking for information about companies, we all gravitate towards their websites. A couple of years ago, I would have been happy to read about the company and its products / services. But today, when I see that the company has put up some video on their website (especially if it a short one), I almost never leave the page without seeing at least the first few minutes of the video. Videos are crowd-pullers and they definitely ensure that visitors spend more time at your website.

Think about a scenario:

1. You put up your product / company video for free on YouTube.
2. Somebody stumbles upon your video while searching for some keyword and likes what you’ve put up there.
3. He then visits your website to know more about your company and your product.

You have just landed a prospective, interested customer on your website – practically for free.

So you see? Videos don’t hurt. Spend some time and add some to your communication arsenal.

Google is today the undisputed leader of the internet. People all over the world are figuring out means to get noticed by Google because it’s almost like you don’t exist unless Google say you do!

Ever noticed how many people offer tips, trick, and even paid classes / presentations to increase your online presence – read Google page rank? Well, its certainly not a bad thing to have high visibility on the internet, what do I feel opposed to the extent to which businesses are willing to go to increase their page ranks.

Here are some bizarre internet marketing practices that make me wonder if Google is in fact proliferating junk content on the internet:

• Posting 5-10 articles per day on portals that publish them for free. I am not talking about news website here. Originality, relevance, be damned; key words zindabaad.
• Posting 3-5 press releases per day on free portals for press releases. Can any company realistically generate so much newsworthy content on a daily basis?
• Leaving irrelevant comments on a blog posts. Like leaving a comment on a blog post that provides tips on using RoboHelp that says “Great post. I sell a great CADD / CAM product. Drop me a line if you are interested.”
• Choking website content with keywords (sometimes as much as 2-3 keywords per line of text) to attain the required keyword density. Whatever happened to the concept of beautiful content that appealed to the reader / visitor rather than to the search engine?

I’m sure you too must have come across many such practices. Why don’t you share your thoughts / experiences?

Lets shun these “shortcuts” and concentrate instead on improving page rank completely on the basis of superior products, customer satisfaction, and though leadership.

Here is a quick recap of what I think are the 7 most important ingredients of good documentation:

• Logical flow of information
• Simple language
• Intelligent Content for the Intelligent User
• Judicious use of Screenshots
• Hierarchical Table of Contents
• Links
• Accurate Information

You can, of course, read a more detailed explanation of each of these points in my earlier posts.

Accurate Information
The one reason why technical writing is considered different from creative writing is that as a technical writer you must not get “creative”. You have to write about what your product / service does and not what you would ideally have liked it to do.

• Make sure to provide technically accurate information.
• Watch out for grammatical errors. Always run a spelling and grammar check.
• Don’t gloss over known issues and bugs; not mentioning them is akin to misleading users.
• Provide notes wherever necessary to highlight important information. Caution notes must appear right at the beginning of the topic, preferably using a different font size and color to catch the readers’ attention.

Links
Links are perhaps the single most important differentiator of online content. It’s, therefore, imperative that you make liberal use of them in your documentation. Use links to:

• Provide logical navigation to the reader. (Read Next, Related Links, Back, Home, etc.)
• Maintain focus on one topic and direct readers to relevant pages for associated information
• Keep your pages short and to-the-point
• Improve readability
• Break up complex content into smaller chunks
• Avoid repetition of content / steps explained in detail elsewhere in the document

Hierarchical Table of Contents

After Search, the Table of Contents (TOC), is perhaps the one element of help manuals that is used most often by readers. The importance of a good TOC is, therefore, hard to overlook.

I have seen several user guides that have long TOCs. Almost every second topic makes its way to the top-level TOC. So why are many technical writers tempted to add as many topics as possible onto the first-level TOC? Here are some common reasons:

•  To (supposedly) make it easier for the reader to quickly find what they are looking for
• For want to complete understanding of the product / subject

The first line of reasoning is absolutely baseless. A long TOC only adds to the clutter. Why do all help authoring tools (like RoboHelp and Flare) support hierarchical TOCs? Simply because they are an important ingredient of good documentation!

This brings us to the second point. The work of a technical writer is not merely that of a writer. A technical writer must be a product expert and an end-user rolled into one. If you, as a technical writer, do not understand the subject you are dealing with, how can you possible expect to make your reader understand it?

So, technical writing is not about writing alone. The truth is that a technical writer must do a lot more things apart from writing. You can read my earlier post on this topic here.

Judicious use of Screenshots

Screenshots are images; and images, as we all know, are bulky. How many of us prefer bulky documentation folders that eat away into our disk space and slow down the response time of programs? So, the question you need to ask is this – are screenshots necessary?

Screenshots are a must in printed user manuals. But do you really need them in your online help? First, let’s try and understand how an online help is used, specifically in the case of software applications. The application is running on one window and the help file is open in another window. The user is probably just tabbing between the 2 open windows. Given that the user is already seeing the screen on one active window, does your guide really need to show static images of the same screen?

The obvious answer is no!

Screenshots, however, are not totally redundant. They are especially useful while explaining dynamic screens whose appearance changes based on user input – a configuration screen, for example.

Choose the Multiple Equipment option to enter details of several equipments together. The displayed screen looks as shown below. (Place a screenshot)

This example probably warrants a screenshot. Not only does the screenshot help the user verify that he has reached the correct screen, but it also provides context for the steps that ensue.