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.
Subject:Re: metrics for good/bad usability dev. From:Daniel P Read <danielread -at- JUNO -dot- COM> Date:Thu, 2 Jan 1997 17:09:03 EST
>>Does anyone have any metrics or anecdotal info for the costs of:
>>1) Poor Usability design
>>2) Bad Information Development and Design (by which
>> I mean the design of all end-user info - GUI, Help,
>> documentation, training, CBT, etc?)
You should check out the book _Rapid Development_ by (I believe) Steve
McConnel (sp?). This is a wonderful book on best practices for software
development as a whole, with emphasis on how these practices affect
development schedules. The book dedicates a good deal of space to design
issues (and classic design mistakes) and uses lots of hard data,
anecdotes, and case studies. If the book does not get specific enough,
the author is thorough in his citations, so, if nothing else, the book
will be able to point you to a lot of its own primary sources. Good