Reality Check


Today’s post on the blog “On Writing Well” gives a rude awakening to aspiring technical writers or junior technical writers (like myself).

The phrase that stuck with me the most:

Merely documenting procedures is NOT technical writing.

You know what? He’s right. 

When people ask me what I do, I tell them I’m a technical writer. When they give me that all-too-familiar blank stare, I explain that I write procedures and Web content and other things to make sure my customers do their work safely and legally.

Most of the time they respond, “Oh I’ve written procedures before. I can be a technical writer! Are you hiring?” *facepalm*

I used to think that because I wrote procedure manuals for my jobs in college that I indeed was already a technical writer. I’ve only been doing this for a few years, but many times I smile at my fresh-faced naïvité. Some days I wonder how hard I’ll be laughing at myself in five years.

The writer of this post gives sound advice that may be a little hard to take. If you don’t like reading boring technical documents, dealing with really busy weeks (or months) and really slow weeks (or months), and interviewing the experts (who can be arrogant, pushy, and sometimes downright mean), then this profession is not for you.

They don’t talk about this in your theory classes. In fact, many of my professors never had to deal with the nitty-gritty, down-and-dirty aspects of technical writing. They never had to go through a year’s worth of writing and then only get a few thank you’s and a “small token of appreciation” but in the end realize that it doesn’t matter because they love what they do.

And I love what I do. I may not be the best at it. I may not be up-to-date with all the single sourcing and e-booking out there, but taking complex information and turning it into something usable and readable is a challenge I really enjoy.

Keep writing and take care,


I’m Back


I doubt any of you have been checking recently since I’ve been MIA since March. Anyway, since a blog I co-author refers to this site, I decided I should pick it up again.

As an update, I still work for the same company and lots of changes are happening, and pretty rapidly. I’m starting a post on lessons learned, as I just finished writing and editing 30 documents in six weeks. I had authorial help, but I ended up having to do more than four passes for each, which took a lot of time because I wasn’t prepared.

Check back in a few days for some new content!

Keep writing and take care,

I am adding links to technical writing books, articles, and educational programs on the Resources page. If you are looking for something specific (such as a good style guide) be sure to add a comment and I will do my best to help you!

Writing for Purpose is not just another technical writing blog. It was created for technical, science, business, healthcare, and other professional communicators. I currently write and edit technical publications, policies, work instructions, marketing materials, presentations, and so much more.

With this blog I hope to provide:

  • A chronicle of my life as a technical writer with practical tricks and tips for everyday technical writing
  • Answers to the question, “What is technical writing?”, along with resources for aspiring technical writers
  • Details on the Customer Empathy Project and how you can join in

Please explore and enjoy your stay!

%d bloggers like this: