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.
"Banging out a document" does not mean having no regard at all to
appearance, content, organization. What it means is getting the document out
as fast as possible while adhering to your best practices at the given time.
After the doc is done, then you can sit back and consider whether this or
that should have been different.
Of course, everyone has to learn how to do things better (I sound like an
add for Phillips Electronics). The trick is to learn and debate issues when
appropriate. When the deadline loometh, put aside your doubts as to whether
your current conventions are the right ones. Use what you got, be consistent
with it, and get the job done. Afterwards, hold meetings about the various
components of the process, but don't get to0 obsessed with those
ruminations. The next project will come up shortly. For that, you apply a
few of the changes you want to make to the process. When that project is
done, hold another meeting or two.
