About three years ago, after working in journalism and finding it not my style, I took a technical writing class on a whim during my Masters studies and fell in love with it. So three years later, here I am, two years into my technical writing job with a software company. As much as I love my job, there is much that also frustrates me.

When I first came on board, the need for documentation was so great, I was busy from day one. It's been non-stop ever since, for which I'm grateful (job security!) I've accomplished a lot, released many manuals, and have a lot to be proud of. But there is one thing that remains a constant downer: no one seems to read anything I write.

Despite being told over and over that I'm doing a great job, I constantly get questions from our customers via the support team about something that is clearly outlined in the manual. It's not a "further understanding," it's a "how-to" in the first place. How do I change skins on the Web product? Read the manual. How do I add programming to a transmitter? Read the manual. How do I add an account, a customer, customization, etc.? Read the manual. It's all there. I promise you.

At a certain point, I become frustrated and think, why bother? Why am I even doing this if no one reads the manual? Is it me, or is it them? Am I just not explaining things clearly enough, or are they too lazy to look it up?

Does anyone else deal with the pressure to release documentation (especially manuals) and then find out that no one reads it? What is the point? I'm told over and over again that I'm valuable to the company, and certainly I feel I have job security, but if no one reads the freakin' manual, why even bother?