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: Writing Samples From:"Nina L. Panzica" <panin -at- MINDSPRING -dot- COM> Date:Tue, 24 Mar 1998 12:07:29 -0500
Penn Brumm wrote:
>Yves had some good ideas. However, if you're in high-tech and if you use
>one, I believe it shows you don't understand your environment. If you
work for a
>start-up or high-tech company, you might be writing highly confidential
>documentation for internal users, or for third-party users who have
>contracts or agreements. This material you write represents hundreds of
>R&D expenses for the company (mostly in salaries and overhead of engineers
>If you attempt to negotiate use of the material outside the company, you
>signals to those interviewing you that you don't have a clue as to the
>of the material or the basic "rules" of the industry. For example, I work on
>documenting software, APIs, and engineering methodologies that may never be
>"exposed" to the outside world. Even if some interface parameters are, the
>workings are not. It is simply not acceptable to "broadcast" what it is
that I am
>writing to other companies. In addition, modifying the material still
I haven't followed this entire thread, and so if I begin to confuse or
conflate something, please set me straight.
In your particular situation, Penn, your advice is right on. I couldn't
agree more. I'm mostly an end-user or interface documenter, however, and in
that sort of situation, there is far less actual "disclosure" at stake, far
fewer secrets to reveal (that the other company couldn't get in a much
easier fashion, for instance, by buying a copy of the competitor's
software). I don't think that negoitiating to get a generic and very strict
non-disclosure clause designed to protect the company from those who
document or design at your level to something more suitable to someone
documenting at a much more superficial and less serious level is the least
bit inappropriate or unprofessional.
I can think of few situations in which I would find it unreasonable for
someone in my situation to ask a client if the non-disclosure agreement can
be modified to allow me to show others the end-user manal after it is
published and easily available to anyone willing to purchase the product.
One of these is if this end-user manual is part of a very expensive product
that costs tens or hundreds of thousands of dollars per licence. But even
in this situation, I don't see a problem with asking permission to modify
the agreement so that I can, at minimum, show a few random or modified
pages from the documentation.