It is strange – and true – that technical communicators, like you and I, are into a profession that most others care a damn about… unless, of course, they are in dire need. No wonder most of the users yearn for the documentation only for troubleshooting their stuff. “I want to somehow get through this”, they intend. So, for the most part of their exploring the product, the users are busy finding answers to their how-does-this-damned-thing-works questions. Why is it still that we are unable to design formats that can make the users’ troubleshooting pursuits easy and manageable?
If I think about this whole thing as a user, it seems a daunting task for me to search for something I am not sure about; All I want is to solve my problem. But, how do I go about the help? How do I know where exactly to look for? How do I make sure to turn all the stones before I take a step further? How do I know how much information is sufficient? How, just how?
The users, I find as a technical communicator, use the following justifications for sending verbal curses to our so called “Help”:
- Can I search for pictures? Does your help contain data/metadata to support searching for pictures?
- I am lost. Where am I? What was I searching for? Is this what I was looking for?
- I am tired. I’ll rather sleep.
- I believe the reviews on the Internet provide more information than you can possibly cover in your next ten iterations. Sorry, I prefer the reviews.
- I got the Internet; I will Google things up! I don’t need you.
- I have other, better things to do.
- I want a PDF. Do you take orders?
- Is that a Help? Almighty, help me!
- That many pages… are you kidding me!
- The help only answers questions on information that is otherwise obvious and easy to locate and resolve. Why would I need answers to such simple things?
- This help is outdated. Is there a new version?
- This isn’t what I was looking for.
- What I read partly solved my problem. What about the issues that remain? And, where can I find information about how to resolve those issues? Hello, are you listening?
- Why aren’t there any graphics? Your writing sucks!
- You call those graphics? I am better off with the written text.
- You can’t expect me to read 20-odd pages just to look for a one-line information tidbit.
- Your help does not contain the keywords that I am searching for. Why?
Sadly, this isn’t any one-person opinion. Most of them have equally creative, purposeful, and heartfelt verbal abuses for the help texts we share with them. Fact of the matter? The help isn’t helpful enough. Yes, it is true that a product is like a shrine with a thousand doors, and that the devotees can enter from anywhere. Yes, it is true that each devotee has a story to tell and a prayer that they want heard. And, Yes, it is true that it is close to impossible to predict the needs of each devotee. But, hey, isn’t that what we do every day as technical communicators? Just some food for thought.