3-00 (September 2000) by Carmel Priore-Garlock Special Aspects Australia

(Reprinted with kind permission from Shenouda News, June 2000)

Have you ever wondered what it is like to be a contracting technical communicator? What is a typical day like? What background brings someone to technical communication, and how does that experience play out on a daily basis? Here are some glimpses into the professional lives of Shenouda associates Beetsy Christiansen (BC), Van Kurtz (VK), Lisa Syed (LS), and Charles Wilkinson (CW).

CPG: Can you describe a typical day in the work life of a technical communicator? BC: Gathering information by researching and interviewing Subject Matter Experts (SMEs), then writing. editing, incorporating feedback. and desktop publishing.

VK: Typically, I spend most of any given day on a single project. While I may be working on more than one project, I do not devote some time to each project every day. A typical day is spent at a computer, doing whatever is necessary to complete the project, whether it is drawing, capturing screens, or putting it all together with a page layout program.

LS: I'm probably not a typical technical communicator these days. I work from home because I want to stay with my toddler. When I have work to do, I schedule it around my daughter's sleep times.

CW: Working for Shenouda Associates Inc. means, typically, each day is different. I may draft or edit a manual (operator, installation, service), procedures (operating or service), a guide (style or business),a training program, or desk-edit product localization (translation) material. Typically, I do any fun project Judy has accepted for the business.

CPG: What part of your background most closely relates to what you do on a daily basis?

BC: I have always loved reading and writing. I discovered I'm not a creative writer; my strength is in taking facts and making them understandable to many people. This led me into journalism in high school and college. I didn't know technical writing even existed! I worked in business communications for 10 years before switching to technical writing.

VK: My background is science, and I have been using computers, in one way or another, since college 31 years ago. Therefore, I am very comfortable using a computer and can easily learn new applications. 0ver the years as a technical writer, I have had to learn several programs in order to get the job done.

LS: My background as an educator helps me most. This background includes knowing how to assess the reading audience and select appropriate format and terminology, organize information in a logical way, edit, speak and write several languages, and learn from and enjoy other cultures.

CW: The ability to use both my graphics and writing experience to create an efficient communications package; not just chunking text and drawings. I am accustomed to being an advocate, and sometimes the only advocate for the audience!

CPG: What would you have done differently to prepare for a career as a technical communicator?

BC: I probably would have taken a computer science course.

LS: I can transfer a lot of the skills I've learned while teaching adults in North America and abroad and those I learned about planning and writing while working on my M.Ed. However, for work as a technical writer, I'd have taken courses in using the various writing tools.

CW: I would have a more formal education in communication, although having worked through the ranks may give me a different viewpoint regarding technical communication.

CPG: What aspect of your work day do you like the most?

BC: Once I have the information in hand, I like it when I get in a good writing groove and the words just flow. Unfortunately, this doesn't happen every day!

VK: I like learning new things. Working freelance provides me with a variety of projects, some interesting some not so. I like the change.

LS: I like it when I need to think about how to improve the way the material is presented. I love finishing a document, doing the last spell-check, and getting it sent off to where it needs to be.

CPG: How does your work make an impact?

BC: I hope that end users are able to understand the technology I have documented and consequently are more productive.

VK: When I do the job right, it helps those who use my products learn their tasks quickly and easier.

CPG: How many hours do you work on a typical day? In a typical week?

BC: Six hours in a typical day, 25 to 30 hours per week.

VK: Six to eight hours per day. In a typical week? 30 to 45 hours.

LS: I like to work 2-3 hours per day. I can manage 10-15 hours a week, but I've done 20 when needed.

CW: Some weeks can be long when working on several projects for several clients. You've heard of "we need it yesterday"?

CPG: With what subjects or content are you typically working?

BC: In the past year, healthcare telecommunications, photographic equipment, and information technology for the most part. I have written a newsletter, software user guides, and training manuals. I have delivered training on Microsoft Office products- Word and Outlook, primarily.

VK: The subjects vary enough so that nothing is typical. Most of my work is writing user manuals for various types of users.

LS: Lately, I've been working with content that is aimed at international audiences. Sometimes the material will undergo translation and other times it will be used by speakers of English abroad. This group includes non-US speakers of English as well as speakers of English as a foreign language. One client converts material I've edited in Word into multimedia format for Internet-based self-instruction.

CW: My Shenouda portfolio indicates my specialty is operating and maintenance procedures, process guides and training programs.

CPG: What tools do you typically use?

BC: Gateway computer and Xerox printer. Microsoft Word, AOL, Adobe Acrobat and FrameMaker.

VK: Word, FrameMaker, FreeHand, Photoshop, Acrobat, and PageMaker.

LS: Lately, I've been using Word and PowerPoint.

CW: MS Word, MS Excel, Visio Technical, and Lotus Notes.  

"transline Deutschland - Übersetzungsdienst für technische Übersetzung"