We’re Not Robots

Professional technical communicators are not automatons. Neither our profession nor our professional associations are monolithic in nature. Just as engineering embraces a wide variety of specialization, so does the field of technical communication. Our specializations tend to be broader in scope: a technical writer rarely, for example, writes only design specifications or testing documentation. Rather, that writer, if he or she is a member of a professional association, is usually well-versed in all phases of system development documentation as well as with marketing or training, for example.

More Than a Writer or Editor

My strong suit is my ability to quickly identify your documentation requirements and do the job as quickly and efficiently as possible. Yes, I am a master of the written word and how and where that word is published. Technical Communicators tend to be well-read and confident in our ability to work with anyone, anywhere, at any time.

What Value Do We Add?

Technical Communicators see the trees, the forest, and the fires that often occur during the development of a project. Why? Because technical communication is more than organizing and laying out information attractively. It’s more than being able to read a schematic or data flow diagram. We understand engineers and programmers and, of equal importance, we understand those who will use your product. We work with those users, or consumers, of your products and can tell you, in your language, of their needs and issues.

The most important value we add is communication!