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.
A>> At what point in the fabled software lifecycle do most of you
A>> beginning creating documentation?
A>All of us who have been there (and we are legion) empathize
A>with your situation. However, I believe it is absolutely
A>vital that pubs folk be part of the initial design team,
A>and have their hands on the product from the word go.
I agree whole heartedly...
What's a writer to do when the software organization is very secretive (and
adamantly so) until well after initial design? I have such a situation. By
the time any "outsiders" were brought into the loop, many features and
characteristics were already written in stone.
When we tried to challenge this, the impression was that we were just
responsible for documentation and not design... after all, what could a bunch
of writers know about software architecture.
It's too late for this product, but some advice would be appreciated for the
next product.
"I personally think we developed language because of our
deep inner need to complain." -- Jane Wagner/Lily Tomlin
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
