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.
I have, for the most part, specialized in end user documentation, though
I've written some functional specifications and design documents under a
very "hands on" manager.
Now I have a new opportunity! My current employer has asked me to help
move the company in a new direction. He'd like me to join the
development team in the beginning of the next project and write *all*
the documentation, including that which the programmers would otherwise
have written.
I really want to do a bang-up job at this, because I know it's the best
way for the team to produce the best possible results -- and the best
way for me to write truly top-notch user dox; but honestly I'm feeling
kind of "at sea" and I could use some guidelines and pointers. If any
of you can give me some ideas about how you handle these projects, I'd
really appreciate it!
Probably best to reply to only me unless someone else voices an
interest.
Technical Consultant/ Communication Specialist
Software Services Corporation
Ann Arbor, Michigan (800)
448-1568
*******************************************************************
My opinions do not in any way represent those of my employer.
