Technical Writing

Lesson 1: Introduction to Becoming a Technical Writer

Who Should Become a Technical Writer?

Technical writers come in all shapes and sizes and with varying talents and interests. While an ability to write a decent sentence is certainly an important skill, an interest in technology is probably just as critical since you will be writing mostly about technology.

As a matter of fact, prior to the computer revolution that began in the 1980s most technical writers were scientists or engineers who also, had a flair for writing. Usually they wrote strictly for a technical audience. There are still many writing jobs available for those with a "techie" background, especially in writing for a highly technical audience, such as programmers, engineers or scientists.

With the computer and technical revolution of the past two decades, technical writers now come from many diverse backgrounds though the majority of them have degrees in English, journalism or (as is occurring more often) technical communication. However, I know tech writers who were bank tellers or employment counselors, and even one who worked for the IRS in a past "incarnation."

Of course, you must be able to write more than just a "decent" sentence. Being able to write concisely and accurately are two of the most important traits for a technical communicator. You are not writing a novel or short story where you must set the mood and generate character. You are writing to help the user of your documentation. That user must be able to find the answer to his question or concern easily, and that answer needs to be written as succinctly as possible.

Moreover, it helps if you are "quick study." Technical communicators are expected to learn quite rapidly new software, new industrial processes, or the operation of the latest equipment. Often times, you simply do not have time to master completely the new technological innovation and must "ramp up" as quickly as possible and learn as you write, often experimenting with that new technology along the way.

Additionally, please do not think that you are going to be able to sit in a corner cubicle somewhere, simply study new technology, and write your magnificent prose. Unfortunately or fortunately--depending on whether you are more introverted or extroverted--you will find that you cannot successfully function without attending project team meetings and interviewing the designers, engineers, programmers and others intimately involved in the production of the new product. Additionally, you will need to attend staff meetings where you must report your progress on the documentation to other team members as well as your writing colleagues and supervisors.

An eye for detail is also critical to any type of writing, and is particularly important for technical communication where the reader of your manual or help file may stumble over poor grammar, spelling or even worse technical inaccuracies or other inconsistencies. Poor, error-filled documentation reflects poorly on the product, the company, the other members of your team, and of course on yourself.

Recommended ReadingThe Complete Idiot's Guide To Technical Writing, Pages 5-8

  1  2  3  4  5