Have you ever wondered why there are so many contract gigs in technical writing and so few full-time positions? It’s challenging to find qualified people and bringing in temp contractors is one way to do it, but that’s not what I’m talking about. What I’m talking about is situations like the one below, described by a technical writer friend of mine.
“Every team I have ever been a part of has either been working overtime while trying to hire two people, or has been trying to work while looking over our shoulders and wondering which of us was next to go.”
In my experience, the nature of most technical writing work—from software to aerospace—is the source of the problem that is causing so many writers to look for full-time gigs and only come up with temp work. The majority of the needed writing is smashed between design completion and product release. It creates a short window where writers are desperately needed, but then it’s followed by a long window where they’re not seen as necessary. Now, in a mature agile environment writers work closely and concurrently with engineers and/or developers, which generally requires a full-time writer or two (or more, depending on the size of the job), but the rest of the writers are brought in as needed as contract workers.
The simple fact is, most companies aren’t running in an agile framework and even those that do are thinking of their technical writing needs as a single point in the product release cycle. This happens most often in manufacturing. That 2020 car model? The new system install on an aircraft? Those updated processors in next year’s Chromebooks? All of them need technical writers to complete the delivery. But once that’s done, the work slows down, and having a technical writer (or a team) on the books full-time doesn’t look like it makes good business sense. It makes sense—in the short-term—to grab those writers on an as-needed basis. They come in, they do the work, and they leave when it’s done. But in the long-term, those short-term writers are a bad fit. Every time a new product gets prepped for release, new writers have to come in, learn the product and the company standards, and start from scratch. This costs time, and time costs money. In the long-term, it makes more sense to keep on full-time technical writers who are well-versed in the product from start to finish and who know the company standards, but downtime also costs money. How does a company keep its writers and stay competitive?
The answer is to find an effective staffing strategy that recognizes downtime will happen but keeps resources focused on core competencies and values. The default of regular full-time 9-5 Mon-Fri may work for some, but in most cases won’t cut it. This is especially true in situations where there’s fluctuation in the demand for a highly skilled function like technical writing. Strategies are needed for dealing with fluctuating demand. Here are a few that have been used by AEC:
I believe the first choice is always to cover the need internally with trusted, connected people you already have. However, each of the internal measures come with cautions.
I understand that “Outsourcing” may send chills up the spines of many tech writers. In the last decade, countless tech writing teams in the US have been decimated by cost cutting efforts which involved sending entire programs overseas. Let’s look at it from a wider perspective.
At AEC Inc., we believe the best approaches to managing the fluctuating demand that occurs in many technical functions are #1, (Cross-training) and #4 (Relief valve). We are dedicated to being a trusted relief valve to our customers and helping them to develop the most effective strategies for managing their technical writing and modeling and drafting demands. It is through our own internal cross-training that we are able to provide a deep well of service to our clients and full time commitment for our team.