Usability Testing--Interim (I hope) summary

Subject: Usability Testing--Interim (I hope) summary
From: Tom Murrell <trmurrell -at- yahoo -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Tue, 4 Jul 2000 07:36:50 -0700 (PDT)

Tim Altom suggests that
(a) only TWs can come up with the idea to do usability testing on their
documents, but
(b) TWs are too arrogant and set in their ways to either do so or accept
results that don't fit their preconceptions.
In a later post, Tim points the way to effective usability testing by defining
the object of such testing as, "to detect obvious problems in layout, word
choice, or organization."

Tom Johnson says that his documentation is all in maintenance mode, so they
don't do testing for minor changes. Tom does report a documentation problem,
but it turns out to have been a service rep. who arrogantly insisted that his
way was better than the documented way. So we conclude that the documents were
okay after all.

Dan Emory explains how he pulled his "90% of all an-line help produced since
1995 would fail a rigorous usability test" number out of thin air while
maintaining that it is probably a low number. Certainly Dan has not had good
experiences with on-line help, by his own admission. Not surprisingly, it turns
out to be Microsoft's fault.

Sandra Charker tells the sad story of usability testing that pointed up even
more flaws in a documentation set than were expected by the writers. Then she
goes on to inform us that the testing she did was a wasted exercise: "One sad
part of this is that there's very little we can do about it. Another sad part
is that this dismal documentation story comes from a very good software shop
that would smother its collective head in ashes if its software failed even
half as badly." (I might argue that if the software shop was so good, its
documentation would be better...or that testing without implementing a
correction plan is almost criminal negligence. Why bother with testing if
you're not going to respond to the results? You make A. Plato seem positively
brilliant.)

Forgive me for seeming so cynical, but if we are writing to meet the needs of
an audience, should we not be able to (a) define those needs, and (b) test our
documentation to determine how well we are meeting those needs with an eye
toward doing even better as we move forward?

Apparently, where usability testing IS occurring, it is a mere bureaucratic
exercise. You all have made me feel at least honest in not pushing it. It
sounds like a waste of time.

Does anyone have any success stories for usability testing?

=====
Tom Murrell
Senior Technical Writer
Alliance Data Systems
Columbus, Ohio
mailto:trmurrell -at- yahoo -dot- com
http://home.columbus.rr.com/murrell/

__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/




Previous by Author: Re: New TECHWR-L Poll Question
Next by Author: Re: SMEs and me
Previous by Thread: Thanks
Next by Thread: Re: Usability Testing--Interim (I hope) summary


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads