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've search the archives, but couldn't find any posts that addressed what a
documentation cycle should be or what documentation cycles are really like
in different companies.
I'm new to the corporate world (graduated 1997) and have been working at my
first "experience" job for the last year. I find myself working under
incredible deadlines (for example, all the online help for a product in two
weeks) and I'm wondering if this is typical for software? Should I
specialize in another area (not software) if I expect a decent amount of
time to complete my documentation?
What is an ideal documentation cycle and what are the documentation cycles
like at your companies? I appreciate any advice you can give me.
Cassandra L.S. Lidgerding
clidgerding -at- premis -dot- com