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.
>What I'm looking for now is a sort of high-level, philosophical
>discussion (or resource) on document management. What should our goals
>be? What are the hallmarks of a good/bad/indifferent documentation
Document Management means you have a process for producing your documents,
tracking their progress through the production process, a process for
updating documents, and a process for tracking all updates. The processes
should include documentation requirements, document design decisions,
distribution/format, information gathering, drafting, editing, document
review, testing, and approval for release. There should be a formal release
procedure. If your documents are related to a product that is under
development or revision, then document production should be integrated into
product production. Once you figure out how you're going to keep everything
controlled and on track, you'll be in a position to consider tools.