TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:FWD: RE: Merging marketing pubs with tech pubs From:"Eric J. Ray" <ejray -at- RAYCOMM -dot- COM> Date:Fri, 28 Aug 1998 13:52:51 -0600
Name withheld upon request. Please reply on list.
*************************************************
We've got a similar situation here. I'd like to find a way to solve my
dilemma, too! Currently we have technical documentation in Research and
Development, and marketing communications exclusively in Marketing. The
problem is that our company has grown large enough that there are all sorts
of other communications activities that need doing, and Marketing wants to
handle them all. This includes the website, intranet as well as Internet,
corporate communications, internal communications, employee newsletters, and
so on. Someone has to take these on, simply from a Quality Assurance
perspective. (Makes me crazy to see newsletters with major typos going to
customers!) BUT, Marketing doesn't have the staff, and those they do have
are not skilled in many of these areas, or have very junior skills.
Techpubs, on the other hand, has senior writers and editors. In order for me
to have a career path at this company, I'll need to supervise more staff and
larger projects. That isn't likely to occur in R&D for quite a while.
Like Beth, I really enjoy the technical side, even though I've done lots of
"the other stuff". My proposed solution is to create an Information
Development department, under R&D, where we'll continue to handle techdocs,
usability, interface design, as well as take on the website, internal
communications, and anything else that seems appropriate. Does that make
sense to anyone?