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.
This discussion seems to have become very complicated. Rather than trying to
understand the position both of you are taling at this point, I'd like to put
forward my view on the subject.
The Technical Writer is a bridge between the technical knowledge of the
programmer, and the functionality knowledge of the user.
The user has a job to complete - they need the computer application to complete
the job. It is the Technical Writer's responsibility to understand enough of
the user's job to be able to tell the user how to complete all required tasks.
In the example of a broker, the Technical Writer needs to know the phases of
completing a deal, as these are the tasks that the end user will need to
complete. The Technical Writer does not need to know the details of how a deal
is completed. For example, the Technical Writer does not need to know how to
find the best source for the client, or what parameters make for a good deal,
but the Technical Writer does need to know that the end user will be looking to
source a deal.
Similarly the Technical Writer needs to understand enough of the programming to
understand how an application works, as this will at times make it easier to
explain to an end user how the application works. However, the Technical Writer
does not need to understand the full details of how the application works. For
example, a good Technical Writer does not need to know the technical details of
how the information is transferred from A to B. Generally it is enough to
understand that the information *is* transferred from A to B.
Please note that the Technical Writer is a bridge. A bridge joins two different
positions, and can be traveled both ways. The Technical Writer needs enough
technical knowledge to explain the application to the end user, but also the
Technical Writer should know and be able to explain the end user's business
requirements to the programmer, to increase the usefulness of the application.
This is not way that the Technical Writer replaces the Usability expert, only
that the Technical Writer has end user business requirement usability knowledge
that a systems usability expert would not have. This knowledge should be
utilised.
On my own behalf
Ceri Williams
Documentation and Training
Basis100
cwilliams -at- basis100 -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
