We are currently using e-syn for project managment and time reporting. Now we want to start using it for true knowledge management. For us that means sharing explicit knowledge in document form and capturing tacit knowledge from "problem resolution".
1. Does anyone have what they believe are good document taxonomies (categories) to suggest? Our business provides hardware and software and related implementation services. I'd appreciate seeing any and all suggestions here.
2. Has anyone designed any requests to help capture knowledge as problems/issues are solved?
3. Is anyone actively using document types? They seem to be quite powerful and I'm looking for practical suggestions and where they have worked well.
Ann Roos Hayner
The administrator has disabled public write access.