I was reminded recently about how much the successful management of remote writing projects relies on common sense, communications, and teamwork. Looking back over previous part-time remote projects I’ve worked on the lack of one of those elements usually made for a lot more difficult of a project.

However, I’m the first to say that communications are a two way street between the remote writer and the mother ship.

Here are three common sense tips for a successful remote writing project:

• Factor in time zones and people’s schedules. You might think working with offshore project members is the most difficult element with a remote writing project. Well, I am here to tell you that it can sometimes be somebody on the opposite coast getting it wrong. When you email somebody at 10 pm your time demanding an immediate response, it could be 1 AM their time. Allow for time upfront in the project planning to ensure that your project communications don’t fumble on such a simple step.
• Remember not everybody is a mind reader. If either party is unfamiliar with remote working, I always recommend in the beginning to factor in some extra lead-time to buffer against simple misunderstandings and give both parties a chance to learn how to work with each other.
• Make your edits and review comments self-standing. One of the more formative times in my technical communications career was freelancing as a computer book technical reviewer. Computer book publishing was and probably still is one of the few industries that gets remote workers especially those who are only doing it part-time. It was through this experience I learned how to make my edits and comments stand on their own. It is one thing to make comments on a document when a coworker can walk down to your cubicle with questions but it can be a completely different animal when other project team members have never met you in person. When working remotely, make the extra effort to make sure your edits, comments, and feedback are descriptive enough to stand on their own and other project team members can work through them with a minimum of questions back and forth.

It’s sometimes the simple things that can hobble a project so take the time upfront to build the working relationship and communications because either party can fumble.

An earlier version of this post appeared on my personal blog.

Will Kelly is a technical writer and analyst based in the Washington, DC area. His writing experience also includes writing technology articles for CNET TechRepublic and other sites. Will’s technology interests include collaboration platforms, enterprise mobility, Bring Your Own Device (BYOD), project management applications, and big data.

Today’s technical writer needs to a bit of an entrepreneur

My late father had a tireless work ethic. It set quite the example for me when I was growing up. He had his day job as a respiratory therapist and always picked up extra work. I must have been a teenager before realized everybody else’s father only had one employer. I carried

Since my September 2012 layoff, I had to readjust to a whole new way of working. My side projects became my primary projects. Here are six reasons why technical writers should be pursuing side writing projects:

1. Maintains alternative income streams. My side projects used to go into my savings or became fun money for luxuries. When I was laid off, those projects helped me transition back into freelancing so quickly that I left my last full-time employer’s office at 2:00 pm and I was back to working at 4:00 pm.

2. Keeps professional skills sharp. The definition and role of a technical writer in some organizations can go very stagnant. If a technical writer is pursuing writing projects on the side, their skills can remain sharp even if budgets and politics at their day job may shift them to a non-writing role. One of the worst things that can happen to a technical writer now in today’s tight economy is to let their skills go. It’s just too competitive out there.

3. Demonstrates a passion for the craft of writing. Writers should be writing. Writers should be enjoying writing. Writers pursuing writing projects outside their normal 9-5 show a passion for the craft.

4. Helps drive learning of new technology. My side freelance writing projects got me to thinking and (better yet) writing about technologies that I did not see during my day job. My entire experience writing about Bring Your Own Device (BYOD), enterprise mobility, and big data comes from side projects. I wouldn’t have a grounding in these subjects if it wasn’t for the projects I first started pursuing on the side.

5. Reinforces project and time management skills. To work on a part-time freelance project the right way you have to treat it as any other project. The part-time nature and off hours schedule make project and time management skills even more critical to the success of such projects

6. Reinforces client management skills. It’s one thing to manage a client you see face to face every day, but another to manage a client you work for part-time and virtually. Side freelance projects can help technical writers reinforce their client management and communications skills. There is a misperception in some circles that there has to be much face-to-face interaction with clients, but I am here to say that is not

As long as the technical writer avoids conflicts of interest, not using company equipment, and delivering on their day job then employers should see side projects as a differentiator not an issue.

An earlier version of this post appeared on my personal blog.

Will Kelly is a technical writer and analyst based in the Washington, DC area. His writing experience also includes writing technology articles for CNET TechRepublic and other sites. Will’s technology interests include collaboration platforms, enterprise mobility, Bring Your Own Device (BYOD), project management applications, and big data.