Box 6.2 Challenges of KM Implementation
Not Having a Specific Business Goal
A KM program should not be divorced from a business goal. While
sharing best practices is a commendable idea, there must be an
underlying business reason to do so. Without a solid business case,
KM is a futile exercise.
KM is Not Static
As with many physical assets, the value of knowledge can erode
over time. Since knowledge can get stale fast, the content in a KM
program should be constantly updated, amended and deleted.
What’s more, the relevance of knowledge at any given time changes,
as do the skills of employees. Therefore, there is no endpoint to a KM
program. Like product development, marketing and R&D, KM is a
constantly evolving business practice.
Not All Information is Knowledge
Companies diligently need to be on the lookout for information
overload. Quantity rarely equals quality, and KM is no exception.
Indeed, the point of a KM program is to identify and disseminate
knowledge gems from a sea of information.
Who should lead KM efforts?
Since KM is not a technology-based concept but a business practice,
enterprise-wide KM efforts should not be led by the CIO. (The CIO is a
suitable choice to lead KM efforts within the IT department, however.)
Some companies have dedicated KM staff headed by a chief knowledge
officer or other high-profile executive. Other companies rely on an
executive sponsor in the functional area where KM is implemented.
What technologies can support KM?
KM tools run the gamut from standard, off-the-shelf e-mail packages
to sophisticated collaboration tools designed specifically to support
community building and identity. Generally, tools fall into one or
more of the following categories: knowledge repositories, expertise
access tools, e-learning applications, discussion and chat technologies,
synchronous interaction tools, and search and data mining tools.
Source: Santosus, M. and Surmacz, J., “The ABCs of Knowledge Management”,
,
(accessed 24/09/04).