I have freelanced in the past with limited success, never able to do better than earn a bit of secondary spending money.
Right now, I know two things.
- In this market, I am going to have to do better than that to make a reasonable living.
- It’s a jungle out there.
There are job boards all over the place like Elance, Sologig, Guru and many others offering freelance projects for writers.
Most of those boards offer dozens — if not hundreds — of projects. You will also find hundreds — if not thousands — of writers scouring the boards looking for work. That means rarely, if ever, will you get paid full value for what the work should be worth. There are too many bidders, and almost always someone willing to do work for a ridiculously low price.
Another way to scour up project work is to use various recruiter or head hunters. If you meet a good one, let me know. I have dealt with too many fly-by-night recruiters who get a little of your money, send your resume one or two places and then forget about you. You know one who really, really gets out there and works for you I want to meet them.
So, how to make this work is the question.
All I can figure is keep beating the bushes in all sorts of boards, work whatever contacts I have and play to my strengths.
One of those is building Technical Documentation, specifically User Guides for customers. I am discovering it is a type of work many writers find boring or not creative enough. Not me. It’s a niche I enjoy, and have found I am good at. From what I can see out there it also looks like one that pays decently — provided you can land the work.
So, what is it that makes a good user guide? Here are some of my thoughts.
- Know your target audience and write to their level. Technical jargon and fancy, long-winded explanations are not important. Helping someone do their job is.
- You don’t need to be the expert. But, you do need to know who the experts are so you can get the information you need.
- Keep it lively. Page after page of documentation is boring. Use plenty of screenshots. If you can, use interactive simulations, demos or videos as well to illustrate functionality.
The ultimate test is handing a finished document to someone who has never seen it before, and possibly never seen the application it describes, and having them use the document to do the job. If they can, you have succeeded. That’s the reward.