Re: Building a documentation knowledgebase

["Gene Kim-Eng" <techwr -at- genek -dot- com>]

It occurs to me that depending on the degree of anarchy in your current
process, getting eveyone to use the same template could very well be
the first step in developing the necessary discipline for a knowledgebase,
or at least a cheap way of finding out if your organization is capable of 
working with one.  If you can't get even your information developers to 
standardize on one bloody template and make document content more
consistent, your chances of getting them to do all the things they'll need 
to do for a kb, like checking things in and out and entering key search 
words in meta data for every piece of information they upload, will be 
nil and investing in a kb will be time and money thrown down a rathole.

Gene Kim-Eng

 
----- Original Message ----- 
From: <chevotilburg -at- postmaster -dot- co -dot- uk>

> Privately- we writers would like to see a knowledgebase happen. Would
> anyone know how to start a plan for a knowledgebase that includes all
> areas - just as a starting point?
> 
> Everyone wants a change in the documentation area - however - i think
> starting with a template that serves all - is not exactly the first step.



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.588 / Virus Database: 372 - Release Date: 2/13/2004