|
Services: Knowledge Portals · Knowledge Map · Knowledge Network · Book of Knowledge · NEWS· INFORMATION
Channels: General Business · Business Technology · E-Business · Knowledge Management Community: Join the Network! · Global Network · Events Calendar · Executive Jobs |
|
Posted by Denham on September 02, 2002 at 16:46:30:
In Reply to: Documentation Methods and Procedures posted by Macheck on September 02, 2002 at 15:16:44:
Greetings Machek,
I guess it depends on what aspects you wish to document and the types of projects you are dealing with!. Documentation for a movie project would be quite different to that for constructing a nuclear power station. Documentation for knowledge transfer is different to capturing setup & compliance data for the FDA or EPA. Documentation for charting medical symptoms or tracking medical trials and efficiacy is different to projects looking at tax audit compliance.
- Learning histories and AARs (after action reviews) are great ways to capture reviews, to avoid repetition of past mistakes, to gather suggestions for improvements.
- Roles, activities, flows, rules, ontologies... A good place to start is the IDEF methodology
- PMBOK is another very useful source.
More context on the nature of the projects would help.
Click Here to Post Follow Up in New Forums
Download Our Articles and Interviews
[Guru Interviews] [Real Time Business Processes] [IT Adoption and Utilization] [Managing and Measuring Knowledge Assets] [The Real Competitive Advantage] [Why IT and KM Systems Fail] [Myths About Expertise Management]
[How 'Best Practices' Become 'Worst Practices'] [Beyond Information Ecology to Knowledge Ecosystems] [Knowledge Exchanges and Social Networks] [Why Expert Systems Aren't Enough]
[KM for E-Business Performance]
[Does KM=IT? Not!]
[Other Articles and Interviews]
About BRINT | News About BRINT | Help & FAQs | Users Guide | Advertise
Make BRINT your Start Page | | Link to BRINT | Submit Articles
Terms of Use | Privacy | © Copyright 1994-2007, BRINT Institute, New York, USA