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.
The project managers have found it to be a good thing that tech writers
sit in on software analysis and design sessions--and take notes. While I
did graduate from high school and college, and did take notes much of the
time (when I wasn't sleeping), I am interested in hearing others'
insights into the note taking process.
<end with lots snipped>
I sit in on the software analysis and design but not as a techwriter but
as a full contributor over usability issues including screen design and
navigation. I often take notes BUT I only document important decisions
and any key controversies, I then attach any whiteboard printouts to
this. Now documenting this is useful for me, useful for the team but
because it is small it doesn't stop me contributing to the meeting. I
flatly refuse to document every bit of x said y etc. If I did that I
probably couldn't get up scribble on the whiteboard, disagree with the
team and all the other fun things that occur in meetings.
Seriously, I would suggest if they want full transcriptions then they
should get a secretary to do it, you're too expensive too waste. However
as you will probably need to note key decisions, problems, issues and any
screen decisions etc, there is no harm in the team using your notes :) I
will sometimes use a laptop to do this as it is quick. I would suggest
that you should be a contributing member of the team in the meeting not
the secretary :) Of course in my project I am the tech writer, usability
consultant, screen designer, usability designer, sometimes system tester
and even user spokesman, so I usually have plenty to contribute to these
meetings. It is important to speak up at these meetings because often key
decisions which affect the usability are made then and there.
dancer -dot- colleen -at- a2 -dot- abc -dot- net -dot- au
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-