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: Tech Writers and Consulting Firms From:Marcia Coulter <NOTJUST -at- IX -dot- NETCOM -dot- COM> Date:Mon, 13 Mar 1995 20:29:47 -0800
Dennis Brandt <maudlin -at- chopin -dot- udel -dot- edu> wrote:
> I am an undergrad of English/Tech Writing at the U of Delaware, and I
>am writing to ask for your help with some questions I have. I read
>your message on the Techwr-l newsgroup, and I thought you would be >
willing to take a stab at a few of my questions.
I have been investigating the role of technical writers in consulting
firms, tech writing groups, and tech writers as freelancers. My
questions are as follows:
>1. Define your understanding of the technical writing consulting firm
>and how it differs (if it does) from a freelancer.
I've been free-lancing for the past five years. Before that I worked for
a tech writing consulting company (Orr and Associates, by name.) In the
past five years, I've subcontracted from my old employer a number of
times.
There are at least three distinctions to make, not two. These are:
1. working as a (regular) employee of a consulting firm
2. working as a subcontractor of a consulting firm (sometimes as a temp
employee)
3. working directly for the client
Re 1:
This is much like working for any employer. They do all the non-tech
writing work. For example, finding clients, billing and collecting for
the work that you do, doing all the bookkeeping associated with running
a business, maintaining an office staff (receptionist or whatever), etc.
Don't ever underestimate the worth of all that. *Many* fine writers
can't sell their services. Others can do that; they just can't deal with
the bookkeeping required by the federal and state governments.
Working for a consulting company can -- at least potentially -- give you
the opportunity to work on more different kinds of things than you would
see working for a regular software company.
Re 2:
Working as a subcontractor for a consulting company. More money, no
benefits (usually), more freedom. The consulting company still does all
the non-tech writing work.
Re 3:
Working directly for a client. Still more money (no need to share with
the consulting company), still no benfits (except the ones you buy for
yourself), still more freedom. And *lots* of responsibility; you do all
the work.
>2. Have you seen an increase in consulting/freelancing as corporations
>down size?
Yes, but there's nearly always a reason for companies to "outsource".
>3. What are the benefits/disadvatages of in-house and consulting
>firm/freelance writing?
See #1. Also, diversity: I have a very low threshhold of boredom. The
thought of having to write on the same topic for a couple of year at a
time just gives me the willies.
A few examples of what I've done the last 5 years:
* Write manuals and produce training materials for a telecommunications
company.
* Conducted a training needs analysis for a 500-member MIS division of a
major utility
* Manage a team of writers and trainers producing training materials for
a company standardizing on OS/2 and selected Windows programs.
* Help write macros (and accompanying doc) that automate the production
of printed manuals in Word 2.0 and 6.0
* Design and conduct a class (called "Not Just the Facts") to help
people learn skills needed to conduct an information-gathering
interview.
Please feel free to contact me for more info or clarification.