We introduce a new guest blogger today, Bill Leavitt of the Chicago Chapter. If you’ve been to an STC Summit you likely already know Bill. This year marks his 50th year as an STC member, so we asked Bill to provide some stories from his 50 years as a technical communicator. He’ll be blogging regularly under the title “Fifty Years with Bill” with thoughts, reminiscings, advice, and more.
Over my 50 years in technical communication I have been in many discussions about how to define our profession. Like many of you, I have my own definition. Thus far, however, no one has suggested a better definition that fits all our members.
There are three considerations in developing an all-encompassing definition. First, it should cover nearly all our members. Second, it should reflect the qualities that successful technical communicators have. And third, it should separate us from all other types of writing.
In my case, I have done five different types of technical writing during my career, and I must make sure that they all fit my definition. I started out as a technical writer in the field of chemicals and liquefaction of the elements of air (oxygen, nitrogen, carbon dioxide, argon, hydrogen and neon). That was really chemical or engineering writing. Then I worked in the space program doing scientific or engineering writing. Then I worked for a building materials manufacturing company doing what I would call construction and architectural writing. As a retiree, I worked for a while doing software documentation for a medical company; that could also be considered medical writing. Finally, I wrote a book that helps people figure out how to plan a happy, healthy, and fulfilling retirement; and that was still another type of technical writing.
So how can I make all these fit my definition? Well, they are all types of writing or communication that help someone to do something. In the final evaluation, that is what we do that is different from any other type of writing. Our job is successfully telling people how to do something that they need to be able to do. No other kind of writing that I know of does this (except possibly some types of educational writing, although I would say people who do educational writing to help someone do something are actually doing technical writing). Thus, there are many types of technical writing, but the common thread is that they all are intended to help someone do something.
So what are the characteristics of all technical writers or technical communicators? First and foremost, they are generally caring people who have a strong desire to help others. They have the ability of understand technical concepts and are able to clearly communicate information so that others can do what they want to learn how to do.
What do you think?
It all boils down to simple things, really, doesn’t it?
Loved the last para; this resonated with me: First and foremost, they are generally caring people who have a strong desire to help others.
This is what I essentially keep saying each time someone asks me about the requirements for this profession: They have the ability to understand technical concepts and are able to clearly communicate information so that others can do what they want to learn how to do.
Thank you, Bill!
Great post, Bill! You’re right on the mark: we technical writers explain how to do things. That is pretty much the long and short of it! As Nathaniel Hawthorne said, “Easy reading is damned hard writing.” Thanks a lot!!