TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I know it's been discussed before, but the archives don't provide an answer
that I can sink my teeth into . . . perhaps there isn't one.
In what ways can I find out how readers use my books, what helps, what turns
them off, what additional info they need, and what is superfluous? It's a
My company provides free phone support. Our customer base is continuously
growing. Our support staff is stretched pretty thin. I can think of no easy
way to track which tech calls could have and could not have been resolved by
reading the book. Similarly, I can think of no way to measure a relative
increase or decrease in support calls resulting from a change in
documentation, and isolating other variables, like more intuitive GUI.
Since before I got here, software comment forms are included in all books.
They don't get filled out. If they did, I'm not sure where they'd go. I'm
also unsure what and how to ask for information, such that the information
is useful. Also, how do I ensure that the reader does not fill it out on the
first day, before they use the book, or that the reader's boss, who does not
use the software, doesn't fill it out? Our customer base is pretty small. A
good number of responses would be no more than a few hundred.