Seriously, do we spend too much time worrying about this? What do we get paid for after all, to write documentation, so that’s what we should concentrate on doing. So what if no-one reads it, as long as I’ve done my job I’ll get paid.
And no, I don’t care if they don’t understand how to use the product properly, if they choose not to read the documentation then there isn’t much more I can do, is there? Yeah, they might get stuck but if I can learn it, so can they. If not then maybe they shouldn’t
Pander, pander, pander. I’m sick of it. The documentation is perfectly good and until people learn to read it then they really should stop complaining. Ohh and if they choose to look on the internet for an answer to their question, good luck! We all know that those bloggering things are a lot of rubbish and no, I don’t use that Twatting thing either, what a waste of time. Don’t even start me on Facebooks.
I’m perfectly busy enough, doing the job I was paid for, so yes, they should RTFM and it’s not my fault if they don’t.
…
Obviously I’m jesting, but this seems to be a bit of a hot topic right now, and rather than rehash what has already been said, I’d highly recommend you spend 10 minutes of your day reading the following:
- If no-one reads the manual, then why bother?
- If No One Reads the Manual, That’s Okay
- If no one reads the manual, that’s NOT okay
- Getting users to read the documentation
I guess it’s safe to say there are challenges ahead but hey, it’s a new year, what better time to start tackling them.