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.
Re: Usability - any experiences or processes to share?
Subject:Re: Usability - any experiences or processes to share? From:<neilson -at- windstream -dot- net> To:<jlshaeffer -at- aol -dot- com>,<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Sun, 25 May 2008 23:37:55 -0400
Perhaps I should have spoken more at length. If all you do is test for usability after the fact, in an attempt to inject some usability, that is futile. Say that you've discovered the product you're about to ship ranks low on usability. Now what do you do? (a) Ignore the results? (b) Cancel the usability expert's contract? (c) Yell at someone? (d) Postpone FCS for a week while you redo a couple of screens? (e) Have four or five beers? And a couple more? (f) All of the above?
Usability studies must be involved at the outset, or fairly soon into the development activity. Iteration is a good idea if the process is designed to allow refactoring with feedback. A commitment from top management is helpful, because otherwise someone (not necessarily management) can scuttle the usability effort, perhaps to fulfill some private agenda.
--Peter Neilson
> Testing for usability
> may or may not be futile. The biggest improvements in usability that I
> have seen in real-world examples came from observing and reacting to
> the problems that actual users had. It was an iterative process.
>
>
> I have bookmarked the site that Peter referenced (usability-architects.com). It looks promising.
>
> Jim
>
>
> -----Original Message-----
>
> From: Peter Neilson <neilson -at- windstream -dot- net>
> wrote:
>
> Testing for usability is futile.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-