Most Popular


Book Reviews

The Ultimate Guide to Electronic Marketing for Small Business
The Daily Drucker
Copy This! The Story of Kinko's
Presence: An Exploration of Profound Change in People, Organizations, and Society
How To Read A Book
Contempt: How the Right is Wronging American Justice
Classical Education at Home
Copy Fights: The Future of Intellectual Property In The Information Age
Flawless Consulting: How to Get Your Expertise Used

Recently


Theme Design
IT Support
Hosting

Tuesday, July 16, 2002

Start Small, Grow Right with KM for Projects

As Jim says, a nice little mini-case on KM -- how to start small and achieve success. This is important for those of us looking to get a company started on the right track. The case study talks about successfully applying KM practices to a single project as a way to embrace the principles. Among the key thoughts:
  • Start small and grow steadily over time.
  • Set the "rules of the road" up front and keep it simple.
  • Enforce the new culture.
  • Define standards but be reasonable.
  • Pilot a project.
  • Assign a KM owner.
  • Show everybody everything.
  • Management support.
  • Team feedback.
This is a useful 15-minute read for anyone getting ready to start or lead a new project.

Project Level Knowledge Management.
Project-level implementations of KM hold promise for one simple reason: They address real day-to-day problems that can only be solved with collaboration. Notice I didn't say collaboration tools. That's a very important distinction because this is where KM has traditionally gotten into trouble. The tools are enablers; collaboration is an interaction of people. If you use the tools right, you make the interaction easier; people see the value and buy into the concept. Once people buy into the concept, any initiative will grow and nurture itself.

This approach is exactly why we're having success with project-level KM. The ability to focus on core collaboration tasks and really get to the heart of what workers need is key to any KM initiative. [ADVANCE for Health Information Executives ]

Another example of some solid thinking about how to introduce KM into the organization. This article focuses primarily on how to support a transition from typical practices (e.g. e-mail and ad hoc documentation) to practices that will support improved knowledge management in the long run. If you look at the examples offered, it's clear that k-logs would be an ideal technology tool to meet KM needs at a project level.

A nice little mini-case. [McGee's Musings]

Posted by: Send an e-mail to Terry Frazier Terry Frazier at 12:00 AM  | Permanent Link  | Trackback URL | 
Categories: Collaboration


Terry W. Frazier
Search this site:
Advanced Search

Syndication

Add to any service
Get updates in your e-mail!

Contact

Click here to send an email to the editor of this weblog.
 
My PGP Key
My Linkedin Profile


Presence


 

 
 ICQ

 

 



 

www.flickr.com
GratefulZed's photos More of GratefulZed's photos