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: What else to tech. communicators do? From:Romay Jean Sitze <rositze -at- NMSU -dot- EDU> Date:Fri, 18 Nov 1994 11:40:22 -0700
On Thu, 17 Nov 1994, Doug, Data Librarian at Ext 4225 wrote:
> An important role I have often played, both formally and informally, is to
> make the decisions of the design team explicit so they can talk about
> them; both to each other and to future users. There are good ways and bad
> ways to do this.
I believe this to be an important aspect of our roles as communicators.
(And BTW, I see myself in the broader category of communicator, not just
as a technical writer/communicator.) I find that frequently my very
infamiliarity with the topic helps me to see inconsistencies and holes in
what others are saying about it.
> The good way to do this is to be involved in facilitated design sessions as
> the "scribe."
> Anyway, the scribe furiously records all this activity, court-reporter
> style, during the meeting, and then creates a document that succinctly and
> clearly describes what the group decided, how the group decided it, and
> what the remaining issues are.
I should think that we ought to be considering the use of a tape
recorder--at least to supplement our notes. (I find that taping the
conversation allows more freedom to jot down questions as they occur to me
without being afraid that I will miss getting something important written...