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 am responsible for user tests (all levels) as well as creating the
documentation. I don't think it will ever be possible to "wean" the user off
documentation, HOWEVER... It is important to listen to the user. If, during a
user test, a request to change the UI arises, it probably should be done.
Especially if it mentioned in all levels of user testing.
I am especially fortunate, because I get to make first call on the problems
arising from the user tests. I determine if the problem fits into one of the
following categories:
Program Problem (bug)
Program Design Issue
User Interface Issue
Enhancement Request
Documentation Issue
Believe it or not, I quite often assign things to Documentation Issue. But UI
is a separate issue.
My $0.02.
Suzette Seveny
Markham, Ontario, Canada
sseveny -at- petvalu -dot- com or suzette -at- yesic -dot- com
------------------------------------------------------------------
DISCLAIMER:
Any opinions expressed are MY opinions.
Feel free to have your own.
Let's agree to disagree
But Please - Don't Flame Me.
Laugh and the world laughs with you;
Snore and you sleep alone.
On Monday, June 07, 1999 4:24 PM, Peterson Karen [SMTP:Peterson_Karen -at- PRC -dot- COM]
wrote:
> I am helping to design bug tracking software for our office. As a result of
> usability testing, I recommended that a certain function be changed, because
> the users consistently did not understand it. The overwhelming response from
> the developers was that it's impossible to create software that's completely
> intuitive; the user must read the manual.
>
> It was my impression that the current tech-writer-favored trends were to
> make the software functionality and the UI as intuitive as possible, weaning
> the user off documentation. Was I wrong?
>
> I'm not debating whether or not we should have manuals or anything like
> that. I was just trying to get the project lead to make changes to the
> interface rather than always saying, "Just explain it in the manual" or
> "Once they do it wrong, they'll learn not to do it that way again."
>
