National Conference Recap
by Susan Harlan, East Bay Chapter

The 2003 STC Annual Conference in Dallas, Texas offered new insights into the current state of technical communications worldwide. We're in a time of rapid change and new demands, so it was important to hear the speakers and talk with other chapter leaders about our profession.

The conference noted the evolution of our role-we're now calling ourselves "technical communicators" instead of just "technical writers." In the near future, we may refer to ourselves as "communicators" and omit "technical" because it will become redundant: in today's technical world, everything we write about will be technical-if not the product, then the medium. Bits of Wisdom

A panel session titled "If I'd Known Then What I Know Now" provided excellent information. Our Region 8 Director Sponsor Bonni Graham, and Lance Gelein, past president of STC and member of the Sacramento Chapter, were among the panelists.

The panel provided the following bits of wisdom:

If you want work samples, include a statement to this effect in your contractor's agreement.

When a work environment with document reviewers is out of control, consider various options:

• Create a documentation plan. Be sure there is agreement on the document reviewers, time frame, and review criteria.
• Send the document to the reviewers with a cover letter stating your expectations.
• Find out who will serve as the point of contact, the one who will make the decision when six edits come in with different technical answers.

  When the deadline is impossible to meet, provide some alternatives:

• Calculate the full-time equivalent (FTE) or number of hours to do a job.
• Use metrics and be wary of using standard numbers. You must know your customer's industry because writing times vary.
• For example, writing procedures for aviation requires 13 hours per page while software requires 4 to 8 hours per page. Be sure to add a little extra for unforeseen circumstances.

  In making career choices:

• Don't be afraid to try something that's not safe.
• Golden handcuffs are still handcuffs.
• Be proactive! Know what you're good at, and do what you love to do.
• You learn more when you screw up. It's OK to take chances!
• Learn your tools at a technical level. For example, know how fonts work.
• ROI is more difficult to prove than cost avoidance.
• Build great relationships with the people, and then call instead of email.
• Always get it in writing!
• Treat people right.
• When a door closes, go through the window.

Looking Towards Our Future
The Conference offered a number of sessions about job searches and career options. Topics ranged from "Control Your Destiny" to "Exploring Our Future: Technical Communications in the Year 2013."

One issue critical to a writer's survival in this year of increased "offshoring" is how we define our job. The forecast is that the title Technical Writer will disappear. The news may be frightening if you're hearing this for the first time, but it doesn't mean we have to give up or jump ship. Instead, we need to understand the changes and how they affect us, and then survey the options for the future.

Several speakers noted that in the future there will be more positions with job titles such as Information Architect, Editor, and Documentation Manager. Opportunities and Challenges

STC, as a professional organization for writers, has the opportunity to provide tremendous benefit to its members. From the society level to the chapter level we are aware of the changes and are working together to create a strategic response and outline for possible future career directions.

This fall, a committee will be formed to address "Writing Now and in the Future." Your input is welcome throughout the year.