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.
> What role do you actively play in managing either customer
> or management expectations for web sites, doc sets, help,
> or whatever?
It's part of the discussion prior to the contract and it's part of the
status reports that get generated during the project. One of the most
important questions a writer can ask prior to starting the project is
"What do you want this [whatever] to accomplish?" At that point, you can
get some idea of just how unrealistic the customer's expectations are,
and do some modification.
Also during the discussion I usually bring up the possibility of having
a designated "naive user" go through the manual or the Help system or
web pages, and try to be productive. I must admit that I usually get
only lip service from customers when I suggest this - their people are
*much* too busy to test-drive the docs, of course.
> Do you tell management that,
> despite a million dollar investment in documentation,
> many people won't read it and they'll still have to pay
> customer support people to read the documentation on the
I use an example from a company where we watched how people used - or
rather DIDN'T use - the docs. Among other things, the story helps the
client understand that we want to help their customers get productive,
and that we're trying to deal with the realities of people not having
enough time to read the manual. It usually doesn't change their minds
about what they want, but it does help make expectations more realistic.
Los Trancos Systems
Or, how do you explain to customers that, although
> the new documentation, Web site, and product are pretty
> darn good, nobody will really be 1000% more productive
> than they were with the old stuff.