About 40% of the assets of a company are knowledge.
The number of knowledge workplaces is increasing (in some companies might be about 60%).
Managment has not only to support knowlegemanagment, but to live it.
But: the implementation without involving the staff will not succeed, too.

Some aspects to be considered:

How to recognise the value of knowledge and how to utilize for the company?
How to acquire knowledge, how to classify, how to share/distribute?
How to motify the "owners of knowledge" to share it?
How to create a "culture of knowledge"?
What do qualitymanagement and knowledgemanagement have in common? Reassuring message to the NON-TECHNICHANS:
"Only 20% of knowledgemanagement is technology. There are also implementations without it".

How to interpret "Knowledge"? (my own interpretation, by purpose no "definition")

Data are elementsof analysis. Information is data with context. Knowledge is information with meaning. Wisdom is knowledge plus insight and sound judgement.

Knowledge is everything I need to succeed in my job (of course there is an analogy to leasure time but nobody will invest time or money there). Not only "brainwork", but also handicraft.
CKM(CustomerKnowledgeManagement) ist not knowledge about the customer, but the knowledge from the customer. CKM vs WM vs CRM 5 styles of CKM (source: "Strategic Management in the Knowledge Economy" (Leibold, Probst, Gibbert))

Especially intuitiv (better known as implicit) knowledge is worth to be circulated (oraly/written/electronically (knowledge database)).
Only as example, analogies in all jobs:
Why to use especially this tool, if I could choose among several? Intuition which has become routine.
Otherwise the colleague has to "reinvent the wheel" or he has introduced an improved version, and does not know the problem is common and the solution is (hidden) company knowledge and will hide it again.
Non intuitive/implicit knowledge may be read somewhere (at least mostly)("Da.., where did I read?"). So at least keywords and source should be stored (paper file, knowledge database, .. (wherever, but ever the same)).
Also traditional knowledge should be stored (in above meaning) otherwise it could be forgotten totally or partially.

More official definition:

external knowledge (about externals: customers, competitors, competing products, market per se)
internal knowledge (about internal business processes, production, company)
explicit knowledge (stored wherever, known to more than one person)
implicit knowledge ("in the brain" of the "knowledgeable"; not all suitable to be stored, but all to be told)

Reassuring message to all Non-technicians:
"Only about 20% of Knowledgemanagament is technical, but there are examples of knowledgemanagemnt without it".

Any question or request for an offer (details of your requirements needed) please mail me .

Several aspects, which have to be taken into consideration
How to assess the value of knowledge and where to use?
Acquisition, classification, distribution, evaluation of usage of knowledge.
How to motivate the knowledgeable to share their knowledge?
Building of a "culture of knowledge", including a terminology used by the whole company.
What has knowledgemanagement in common with Quality Management?
What has knowledgemanagement in common with Process Management?

Decisions to be made
Definition of the process for gaining knowledge
Make knowledgemanagement part of the confidential talk between manager and staff-member
Definition of knowledge-processes (knowledge-processes show the flow of knowledge within business-processes)
Check implementation of "Bilancing of intangible assets" (e.g.Balanced ScoreCard,
IC(Intellectual Capital)-Assessment, -Reporting)

How to implement (my proposal, main steps only)

analysis of the company

goals and "non-goals" of knowledgemanagement and feasibility

management style of the company

Does the company treasure knowledge?

Does the staff treasure knowledge?

Is knowledge in possesision of the sole member or is the value of knowledge honored?

Who are the "knowledgeable", who the "hidders of knowledge"?

concept (based on interviews in the company)

assessment of the knowledgeof the company

Are there incentives for "knowledge sharing"? Motivation of "the hidders of knowledge"

Decision on the tools and methods to be used

Building of the "culture of knowledge"

Who needs which knowledge? In which detail? For his/her work or information only?

Who is entitled to deliver knowledge? Only the specialists ("Who is specialist?") or everybody?

Projectmanagement: timeframe, teammembers (permanent and/or temporarily, chosen or voluntarily)

Getting in sync with CRM (if installed). CRM is to be considered "external knowledge" (knowledge about: customers, competitors, ..)

Integration into QM-system

Keep in mind:

Hierarchy

Structures

have a big influence on the success of the project. The "unwritten laws" of the company have to be obeyed, too.

Technologies used for gaining of knowledge, protection of knowledge:

Interpersonal communication Creativity

Quality circles (Community of Practise), Conferences, Community of experts Brainstorming

Story Telling 6-5-3 method

"knowledge fair" (rolls: "knowledge brokers" whose task is to
ensure the "knowledge seekers" met with the "knowledge holders") MindMap

Workshops Open Space conference

AAR (AfterActionReply (developed by US-military)) Future Search conference

Lessons learned, Best practises "Prouds and Sorries"

Mentors, Job rotation, incentives WorldCafe

company TV / newspaper, video conferencing

former employees (Consulting company, meetings, ...)

special company meetings (e.g. "breakfast for all"(includes CEO and "cleaning personel"))

(have a look at KS-Toolbox (Knowledge Sharing))

Electronic Tools

Yellow pages, (Knowledge)DataBase Search machines

(Knowledge)DataBase Agents

Computer bulletin boards Personalized function

Employee suggestion system

NewsLetter, Communities

Knowledge marketplace

Microarticle, Libraries, Blogs

DocumentManagementSystem (DMS)

PodCast

Knowledge Management Maturity Model (KMMM) (developed by Siemens)

Function type Coordination Attention Recall Motivation Elaboration New insight	Knowledge type Know-what Know-how Know-why Know-where Know-who	Recipient type Individual Group Organization Network	Visualization type Sketch Diagram Image Map Object Interactive visualization Story
	knowledge visualization as MindMap
(This visualisation is the result of the JR(working group) "To order knowledge and make it visible" (Sept. 2005 - May 2006) of PWM (Platform knowledgemanagement in Vienna) which I attended.)

Interpersonal communication		Creativity
Quality circles (Community of Practise), Conferences, Community of experts		Brainstorming
Story Telling		6-5-3 method
"knowledge fair" (rolls: "knowledge brokers" whose task is to ensure the "knowledge seekers" met with the "knowledge holders")		MindMap
Workshops		Open Space conference
AAR (AfterActionReply (developed by US-military))		Future Search conference
Lessons learned, Best practises		"Prouds and Sorries"
Mentors, Job rotation, incentives		WorldCafe
company TV / newspaper, video conferencing
former employees (Consulting company, meetings, ...)
special company meetings (e.g. "breakfast for all"(includes CEO and "cleaning personel"))
(have a look at KS-Toolbox (Knowledge Sharing))

Electronic		Tools
Yellow pages, (Knowledge)DataBase		Search machines
(Knowledge)DataBase		Agents
Computer bulletin boards		Personalized function
Employee suggestion system
NewsLetter, Communities
Knowledge marketplace
Microarticle, Libraries, Blogs
DocumentManagementSystem (DMS)
PodCast
Knowledge Management Maturity Model (KMMM) (developed by Siemens)