Being a writer for hire opens a world of opportunity. There are many places that need good writers. I’ve written about it before. But within those vast opportunities, there is a clear divide between technical and non-technical writing. Choosing between them is a tough decision. Should you follow the emotion or the facts? The story or the money?
Technical writing is a lucrative. It pays much more than traditional freelance jobs. It is also challenging and demanding. Not many writers can convert technical information into meaningful text for a technical audience. Those who can are in demand.
But opportunities in technical writing are not for everyone.
They are not for me. And here is why:
Reason One: I Am Not a Technical Person
I don’t enjoy learning technical things beyond how to work the universal remote, play a video game or run Scrivener. And while I can use various software programs, I learned them out of necessity, not fascination. Even when I am fascinated by a subject, I prefer my reference sources be books and articles written in an accessible (i.e., non-technical) way if possible. I have to be invested in a topic to delve into technically written articles. And even then, I prefer converting that information into conversational copy in my head. I am clearly not a technical writer.
Reason Two: I Fall Asleep
Technical writing bores me. It solves all sorts of insomnia issues, unless I am already taken by the subject and willing to do a deeper dive. It is not the information that turns me off, but the way the information is written. Technical writing is formal and stark. It eschews anything but logic and comes off stilted and convoluted to my mind. Not to those who in the field. If the same information was written with story in mind or in accessible language, it would be more enjoyable for me. Luckily, there are many who do not feel this way. They love the packed sentences, the stripped down facts and scholarly tone. They are the ones who should write technical pieces. Not me. My heart’s not in it and it’s never a good idea to write something that puts you to sleep.
Reason Three: My Boredom Shows
The few times I have taken a technical writing job, my disinterest showed on the page. You can’t write something well if you it bores you or puts you to sleep. It will be obvious in the copy. That is not fair to the client or the reader.
Reason Four: I Don’t Trust Myself to Get It Right
Technical writing is important. It needs to be right every time. One mistake could lead to more egregious errors down the road. I remember a story my father told me about a company that built jet engines. The engineers asked the technical writers to come up with instructions for installing the engine they’d designed and then tested those directions. They followed the instructions exactly and ended up building the engine upside down. One incorrect line early in the instructions changed everything. Getting it right in writing requires a technical mind and specialized skills. It has to be right. If you can’t deliver that, choose another field.
It all comes down to choice. When deciding what jobs to go after, consider your skills and interests. They matter. You will write better in fields that interest you and in styles that suit you. It’s not enough to chase the money.
Technical writing appeals to a lot of people because it pays more, but that’s not a good enough reason to choose it as your focus. Know what you can write and what you can write well. Technical writing is not for everyone. Those who are good at it know it.
If you are interested in technical writing, do your research. Find your niche. Choose it out of passion for that style of writing and love of the work. Otherwise, choose one of the many other types of writing opportunities out there. Leave the technical writing to those who can make it interesting and right.