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: Who "owns" design documentation? From:Sarah Lee Bihlmayer <sarahlee -at- CONTENTMANAGE -dot- COM> Date:Tue, 16 Jul 1996 17:34:27 -0700
Mike Wing quotes me and asks a very good question:
>>I agree to let the developers write changes to the design as they
>>occur--as long as
>>they let me do some of the development work also!
>What do you do if they agree to your terms?
This has actually happened twice. The first time, I got involved in the
development process and wound up designing the user interface--which is yet
another function I'm qualified to perform. The second time, the product
manager agreed but when the lead developer heard about it, he raised a major
stink with the PM's manager. The result? I won my point about ownership of
the design docs without shoveling any development tasks onto my
already-too-full plate. (Needless to say, this outcome was just fine with me!)
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-