I received this note from a friend of mine who works in the same industry as I do:
The stereotypical technical writer sits in a cube all day and writes manuals, online help, or some combination thereof.
I work for a company that produces a complicated product everyone uses that requires no user manual: electricity.
So why would they need me?
Because they need good technical communication for software implementations, for technical training, for employee communications, and for IT presentations to upper management.
As the STC continues its quest to “tell our powerful story” it’s worth looking at this role. I don’t think I’m unique, but this approach to the profession is not widely promoted. Can you discuss this topic and solicit feedback from your readers?
We might even consider presenting on it at the STC conference in Philadelphia.
Tech Comm Generalist
Dear Tech Comm Generalist,
Thanks for your note. Your description of your work sounds familiar.
I bet there are a lot of technical communicators out there who play a similar role in their organizations.
We face some different challenges than others in our profession.
I will devote a few blog posts to this and maybe we can come up with a proposal.
PS. If a book written via a blog is a “blook,” is a proposal written via a blog a “bloprosal?”
Next: “Where do TCGs draw the line?” or “I don’t do windows”