Michelle Despres
How did you get your start as a technical communicator?
About ten years ago, I was working at NASDAQ when the company introduced their first technical writer position and offered it to me. My educational background in English and logic proved to be a perfect combination for the role. I joined STC, subscribed to electronic mailing lists, and read books to learn more about the profession, methodologies, and tools and to begin creating a network of fellow professionals. It was the first of my three positions as a lone writer. While at NASDAQ, I went back to graduate school for my MA. My specialization in composition and rhetoric focused on technical communication.
What was your first or favorite technical writing project? Describe some of the challenges you faced and successes realized as you completed it.
I’ve always worked in software and for companies that support traders and analysts. After NASDAQ, I was hired by a Manhattan equities firm that had no technical writer and no software documentation. I started with a blank page on the screen. In three months, I went through every window, field, task, and option to create the company’s first software manual, which was well-received.
My subject matter experts were traders, who were busy on the floor most of the day. I learned to schedule meetings after market close (when it’s best for the SME, not me), to be prepared with thoughtful questions, and to get to the point during interviews. Almost anyone is willing to help if you respect the process.
What tools do you use to do your job?
I write in Word and produce help with Doc-to-Help. Most of my customers prefer guides and manuals that they can easily print. Using Acrobat, I produce PDFs of everything I write. I use Snagit for screen captures and editing. I also use Excel and Visio. I’m hoping to start using Captivate more.
What do you feel is the most important skill for a technical communicator?
I might be biased, and I am sure it’s up for a healthy debate, but I say writing.
What is your favorite thing about being a technical communicator?
Besides writing, customer service. I’ve always had some contact with customers and have been fortunate to receive direct feedback about my work. When my (internal and external) customers are happy, then I am happy.
What advice would you give to people who want to begin a technical communication career?
Don’t limit the scope of what you think a technical communicator can be. I tend to meet people who are technical writers for technology companies, but this field is so much more. You can work in a variety of industries (education, medicine, manufacturing, government, energy, finance), for a variety of companies (international, small, private, non-profit, your own), in a variety of circumstances (overseas, part-time, telecommuting) to produce a variety of user assistance and technical communication products (manuals, video tutorials, help systems).
Also, join a professional community, and use social networks to build relationships.
If you weren’t in the technical communication profession, what would you be?
A forensic linguist. My dream is to go back to school for my PhD in linguistics. I thought about data mining, but I’d miss working in words.