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:Re: Outsourcing From:Chuck Banks <chuck -at- ASL -dot- DL -dot- NEC -dot- COM> Date:Sun, 2 Jan 1994 12:38:24 CST
Mark Levinson et al,
Outsourcing needn't be a disaster. The times when
I failed at a contract, it was due in large part to being
brought in too late in the development cycle. Many
employers don't understand that contract technical
communicators don't always work miracles.
At NECAM we have contracted both maintenance of
existing documents and development of new documents. We
don't bring in contractors to new projects a few months
before delivery. We do hire them to take up maintenance
slack when in house talent is more appropriate for new
projects (i.e., due to short learning curves).
When we have adequate lead time, we hire contractors
for new projects. We use Xerox GlobalView software which is
not as popular as other DTP packages. So we have to provide
lead time enough for contractors to learn the software and
the new product(s).
Therefore, we've had very good experiences with
ouside production companies and contract personnel.
Contractors and ousided production companies can be
godsends, but you have to give the Diety time to work the
chuck -at- asl -dot- dl -dot- nec -dot- com