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:Writing Test? From:"Anthony Markatos" <tonymar -at- hotmail -dot- com> To:Mpschiesl -at- ra -dot- rockwell -dot- com, techwr-l -at- lists -dot- raycomm -dot- com Date:Thu, 18 Nov 1999 07:01:53 PST
Tony Markatos says:
The problem with writing tests is that they are based on the assumption that
the major task of a Technical Writer is the drafting of text. Nonsense.
The major tasks of TW are properly performing analysis (of tasks, end user,
and environment) and then - based upon this analysis - properly organizing
the material for high usability.
Oh sure, there would be some analysis and organization involved in a test;
however, the skills required to perform a larger scale analysis/organization
are entirely different than those involved in performing an hour-or-so
analysis/orgainzation.
For example, the major skill required to perform a larger scale
analysis/organization is the ability to "switch mental gears" from
performing (often heavy) analysis work, to becoming a
"lean-mean-people-oriented-machine". There is NO way to even begin to
determine this during an hour-or-so test.
The idea of testing TWs is but another unfortunate example of what happens
when we loose are proper focus. Oh well, back to basics.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
