Christopher gave us an overview of PBMA-KMS.
Technology as an enabler, not a driver.
Video Nuggets as a knowledge capture and sharing tools
Publicly (and freely) available (http://pbma.nasa.gov)
Knowledge Registry (Includes Competency management system)- find out who knows what and how to reach them
Secure workgroups - can host sensitive but not classified information
Real-time remote meeting and conferencing capabilities
[Look at his metrics slide to an example of how one might measure KM success.]
Key lesson learned:
KM Systems do not survive without a heavy does of the human element.
Programmers should not be driving the KM system. (Don't even let programmers suggest the tools. Instead, identify the problems and find the tools to match.)
Subject Matter Experts should be driving the system. (They want to share, but often don't have time. Find a moderator and make it fast and easy for them to do so.)
Don't buy a tool, buy what it does.
Don't buy the tool, buy what it does
- Don't get complacent with a vendor, continue to make the "build vs. buy" analysis as the system grows.
- Licensing can become prohibitive as the system grows.
- Don't let success be your undoing (success can kill the budget if proper planning isn't in place.)t
[My next actions, 1. Study the public components of PBMA, 2. Study his slide on successful KM implementation & metrics, 3. Attend Christopher's presentation tomorrow. 4 Pilot a "video nuggets of knowledge" database in Lotus Notes to share with eProductivity clients.]