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.
We do some informal usability testing where I work. Our documentation is
mostly in a maintenance state right now, so changes are irregular and
usually minor. Because of the minor changes, we normally don't bother with
formal testing.
Our latest test was rather interesting. We had a complaint from a customer
saying a certain procedure was unclear. This procedure has been in use for
about three years and we've made some minor changes along the way. Word
came to us through one of our service reps that the customer was confused
and couldn't get through the procedure.
So, we gave the procedure to several people with experience similar to our
typical customer. They tested it and had no trouble whatsoever. It turns
out the same service rep had trained this customer how to perform this
procedure HIS WAY and told them the procedure in the book was wrong and not
to follow it. Why our service rep is undermining the manuals remains to be
seen. Maybe he is trying to make himself look good in some weird convoluted
way. Maybe his way is easier or better, but he hasn't given us anything to
chew on yet.
So what does this say about usability testing? Some people will find
something wrong even if hundreds of people use it with no problem. Can you
come up with a document that will make everyone happy? Maybe, maybe not.
Can an employee single-handedly make a document (or a company) look
foolish? Most definitely.
On Monday, July 03, 2000 3:13 PM, Tom Murrell [SMTP:trmurrell -at- yahoo -dot- com]
wrote:
> Of course, I realize that there are many among us who will say that there
is no
> reason for usability testing. I can just hear them saying, "Just cram all
the
> information between the covers of the documentation and let the user sort
it
> out. We don't need testing; we need results!"
>
> However, I don't count myself among those sorts.
>
> I'd also be interested in hearing from those who do manage some usability
> testing about how they balance that need with deadlines and other
deliverables.
>
> =====
> Tom Murrell
> Senior Technical Writer
> Alliance Data Systems
> Columbus, Ohio
>
Tom Johnson
Technical Writer
