| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Knowledge Management

Page history last edited by Dmitry PNGHS 2 months ago
Go:  Visual Taxonomy Links   Hide/Show:

Taxonomy Path

Top > Reference > Knowledge Management

https://en.wikipedia.org/wiki/Knowledge_management

Contents

Customer knowledge Ignorance management Not to be confused with Content management or Information management.

Knowledge management (KM) is the collection of methods relating to creating, sharing, using and managing the knowledge and information of an organization.[1] It refers to a multidisciplinary approach to achieve organisational objectives by making the best use of knowledge.[2]

An established discipline since 1991,[3] KM includes courses taught in the fields of business administration, information systems, management, library, and information science.[3][4] Other fields may contribute to KM research, including information and media, computer science, public health and public policy.[5] Several universities offer dedicated master's degrees in knowledge management.

Many large companies, public institutions and non-profit organisations have resources dedicated to internal KM efforts, often as a part of their business strategy, IT, or human resource management departments.[6] Several consulting companies provide advice regarding KM to these organizations.[6]

Knowledge management efforts typically focus on organisational objectives such as improved performance, competitive advantage, innovation, the sharing of lessons learned, integration and continuous improvement of the organisation.[7] These efforts overlap with organisational learning and may be distinguished from that by a greater focus on the management of knowledge as a strategic asset and on encouraging the sharing of knowledge.[2][8] KM is an enabler of organizational learning.[9][10]

The most complex scenario for knowledge management may be found in the context of supply chain as it involves multiple companies without an ownership relationship or hierarchy between them, being called by some authors as transorganizational or interorganizational knowledge. That complexity is additionally increased by industry 4.0 (or 4th industrial revolution) and digital transformation, as new challenges emerge from both the volume and speed of information flows and knowledge generation.[11]

History

Knowledge management efforts have a long history, including on-the-job discussions, formal apprenticeship, discussion forums, corporate libraries, professional training, and mentoring programs.[2][10] With increased use of computers in the second half of the 20th century, specific adaptations of technologies such as knowledge bases, expert systems, information repositories, group decision support systems, intranets, and computer-supported cooperative work have been introduced to further enhance such efforts.[2]

In 1999, the term personal knowledge management was introduced; it refers to the management of knowledge at the individual level.[12]

In the enterprise, early collections of case studies recognised the importance of knowledge management dimensions of strategy, process and measurement.[13][14] Key lessons learned include people and the cultural norms which influence their behaviors are the most critical resources for successful knowledge creation, dissemination and application; cognitive, social and organisational learning processes are essential to the success of a knowledge management strategy; and measurement, benchmarking and incentives are essential to accelerate the learning process and to drive cultural change.[14] In short, knowledge management programs can yield impressive benefits to individuals and organisations if they are purposeful, concrete and action-orientated.

Research

KM emerged as a scientific discipline in the early 1990s.[15] It was initially supported by individual practitioners, when Skandia hired Leif Edvinsson of Sweden as the world's first Chief Knowledge Officer (CKO).[16] Hubert Saint-Onge (formerly of CIBC, Canada), started investigating KM long before that.[2] The objective of CKOs is to manage and maximise the intangible assets of their organizations.[2] Gradually, CKOs became interested in practical and theoretical aspects of KM, and the new research field was formed.[17] The KM idea has been taken up by academics, such as Ikujiro Nonaka (Hitotsubashi University), Hirotaka Takeuchi (Hitotsubashi University), Thomas H. Davenport (Babson College) and Baruch Lev (New York University).[3][18]

In 2001, Thomas A. Stewart, former editor at Fortune magazine and subsequently the editor of Harvard Business Review, published a cover story highlighting the importance of intellectual capital in organizations.[19] The KM discipline has been gradually moving towards academic maturity.[2] First, is a trend toward higher cooperation among academics; single-author publications are less common. Second, the role of practitioners has changed.[17] Their contribution to academic research declined from 30% of overall contributions up to 2002, to only 10% by 2009.[20] Third, the number of academic knowledge management journals has been steadily growing, currently reaching 27 outlets.[21]

Multiple KM disciplines exist; approaches vary by author and school.[17][22] As the discipline matured, academic debates increased regarding theory and practice, including:

Regardless of the school of thought, core components of KM roughly include people/culture, processes/structure and technology. The details depend on the perspective.[27] KM perspectives include:

The practical relevance of academic research in KM has been questioned[34] with action research suggested as having more relevance[35] and the need to translate the findings presented in academic journals to a practice.[13]

Dimensions

Different frameworks for distinguishing between different 'types of' knowledge exist.[10] One proposed framework for categorising the dimensions of knowledge distinguishes tacit knowledge and explicit knowledge.[31] Tacit knowledge represents internalised knowledge that an individual may not be consciously aware of, such as to accomplish particular tasks. At the opposite end of the spectrum, explicit knowledge represents knowledge that the individual holds consciously in mental focus, in a form that can easily be communicated to others.[17][36]

The Knowledge Spiral as described by Nonaka & Takeuchi.

Ikujiro Nonaka proposed a model (SECI, for Socialisation, Externalisation, Combination, Internalisation) which considers a spiraling interaction between explicit knowledge and tacit knowledge.[37] In this model, knowledge follows a cycle in which implicit knowledge is 'extracted' to become explicit knowledge, and explicit knowledge is 're-internalised' into implicit knowledge.[37]

Hayes and Walsham (2003) describe knowledge and knowledge management as two different perspectives.[38] The content perspective suggests that knowledge is easily stored; because it may be codified, while the relational perspective recognises the contextual and relational aspects of knowledge which can make knowledge difficult to share outside the specific context in which it is developed.[38]

Early research suggested that KM needs to convert internalised tacit knowledge into explicit knowledge to share it, and the same effort must permit individuals to internalise and make personally meaningful any codified knowledge retrieved from the KM effort.[6][39]

Subsequent research suggested that a distinction between tacit knowledge and explicit knowledge represented an oversimplification and that the notion of explicit knowledge is self-contradictory.[12] Specifically, for knowledge to be made explicit, it must be translated into information (i.e., symbols outside our heads).[12][40] More recently, together with Georg von Krogh and Sven Voelpel, Nonaka returned to his earlier work in an attempt to move the debate about knowledge conversion forward.[4][41]

A second proposed framework for categorising knowledge dimensions distinguishes embedded knowledge of a system outside a human individual (e.g., an information system may have knowledge embedded into its design) from embodied knowledge representing a learned capability of a human body's nervous and endocrine systems.[42]

A third proposed framework distinguishes between the exploratory creation of "new knowledge" (i.e., innovation) vs. the transfer or exploitation of "established knowledge" within a group, organisation, or community.[38][43] Collaborative environments such as communities of practice or the use of social computing tools can be used for both knowledge creation and transfer.[43]

Strategies

Knowledge may be accessed at three stages: before, during, or after KM-related activities.[30] Organisations have tried knowledge capture incentives, including making content submission mandatory and incorporating rewards into performance measurement plans.[44] Considerable controversy exists over whether such incentives work and no consensus has emerged.[7]

One strategy to KM involves actively managing knowledge (push strategy).[7][45] In such an instance, individuals strive to explicitly encode their knowledge into a shared knowledge repository, such as a database, as well as retrieving knowledge they need that other individuals have provided (codification).[45] Another strategy involves individuals making knowledge requests of experts associated with a particular subject on an ad hoc basis (pull strategy).[7][45] In such an instance, expert individual(s) provide insights to requestor (personalisation).[31] When talking about strategic knowledge management, the form of the knowledge and activities to share it defines the concept between codification and personalization. [46] The form of the knowledge means that it’s either tacit or explicit. Data and information can be considered as explicit and know-how can be considered as tacit. [47]

Hansen et al. defined the two strategies (codification and personalisation).[48] Codification strategy is document-centered strategy, where knowledge is mainly codified as “people-to-document” method. Codification relies on information infrastructure, where explicit knowledge is carefully codified and stored.[48] Codification focuses on collecting and storing codified knowledge in electronic databases to make it accessible.[49] Codification can therefore refer to both tacit and explicit knowledge.[50] In contrast, personalisation encourages individuals to share their knowledge directly.[49] Information technology plays a less important role, as it only facilitates communication and knowledge sharing.

Other knowledge management strategies and instruments for companies include:[7][25][31]

  • Knowledge sharing (fostering a culture that encourages the sharing of information, based on the concept that knowledge is not irrevocable and should be shared and updated to remain relevant)
    • Make knowledge-sharing a key role in employees' job description
    • Inter-project knowledge transfer
    • Intra-organisational knowledge sharing
    • Inter-organisational knowledge sharing
    • Knowledge retention also known as Knowledge Continuation: activities addressing the challenge of knowledge loss as a result of people leaving[51][52][53]
    • Mapping knowledge competencies, roles and identifying current or future predicted gaps.
    • Defining for each chosen role the main knowledge that should be retained, and building rituals in which the knowledge is documented or transferred on, from the day they start their job.
    • Transfer of knowledge and information prior to employee departure by means of sharing documents, shadowing, mentoring, and more,
  • Proximity & architecture (the physical situation of employees can be either conducive or obstructive to knowledge sharing)
  • Storytelling (as a means of transferring tacit knowledge)
  • Cross-project learning
  • After-action reviews
  • Knowledge mapping (a map of knowledge repositories within a company accessible by all)
  • Communities of practice
  • Expert directories (to enable knowledge seeker to reach to the experts)
  • Expert systems (knowledge seeker responds to one or more specific questions to reach knowledge in a repository)
  • Best practice transfer
  • Knowledge fairs
  • Competency-based management (systematic evaluation and planning of knowledge related competences of individual organisation members)
  • Master–apprentice relationship, Mentor-mentee relationship, job shadowing
  • Collaborative software technologies (wikis, shared bookmarking, blogs, social software, etc.)
  • Knowledge repositories (databases, bookmarking engines, etc.)
  • Measuring and reporting intellectual capital (a way of making explicit knowledge for companies)
  • Knowledge brokers (some organisational members take on responsibility for a specific "field" and act as first reference on a specific subject)
  • Knowledge farming (Using note-taking software to cultivate a knowledge graph, part of Knowledge Agriculture)

Motivations

Multiple motivations lead organisations to undertake KM.[36] Typical considerations include:[31]

  • Making available increased knowledge content in the development and provision of products and services
  • Achieving shorter development cycles
  • Facilitating and managing innovation and organisational learning
  • Leveraging expertises across the organisation
  • Increasing network connectivity between internal and external individuals
  • Managing business environments and allowing employees to obtain relevant insights and ideas appropriate to their work
  • Solving intractable or wicked problems
  • Managing intellectual capital and assets in the workforce (such as the expertise and know-how possessed by key individuals or stored in repositories)

KM technologies

Knowledge management (KM) technology can be categorised:

  • Groupware—Software that facilitates collaboration and sharing of organisational information. Such applications provide tools for threaded discussions, document sharing, organisation-wide uniform email, and other collaboration-related features.
  • Workflow systems—Systems that allow the representation of processes associated with the creation, use and maintenance of organisational knowledge, such as the process to create and utilise forms and documents.
  • Content management and document management systems—Software systems that automate the process of creating web content and/or documents. Roles such as editors, graphic designers, writers and producers can be explicitly modeled along with the tasks in the process and validation criteria. Commercial vendors started either to support documents or to support web content but as the Internet grew these functions merged and vendors now perform both functions.
  • Enterprise portals—Software that aggregates information across the entire organisation or for groups such as project teams.
  • eLearning—Software that enables organisations to create customised training and education. This can include lesson plans, monitoring progress and online classes.
  • Planning and scheduling software—Software that automates schedule creation and maintenance. The planning aspect can integrate with project management software.[23]
  • Telepresence—Software that enables individuals to have virtual "face-to-face" meetings without assembling at one location. Videoconferencing is the most obvious example.
  • Semantic technology such as ontologies—Systems that encode meaning alongside data to give machines the ability to extract and infer information.[54]

These categories overlap. Workflow, for example, is a significant aspect of a content or document management systems, most of which have tools for developing enterprise portals.[7][55]

Proprietary KM technology products such as Lotus Notes defined proprietary formats for email, documents, forms, etc. The Internet drove most vendors to adopt Internet formats. Open-source and freeware tools for the creation of blogs and wikis now enable capabilities that used to require expensive commercial tools.[35][56]

KM is driving the adoption of tools that enable organisations to work at the semantic level,[57] as part of the Semantic Web.[58] Some commentators have argued that after many years the Semantic Web has failed to see widespread adoption,[59][60][61] while other commentators have argued that it has been a success.[62]

Knowledge barriers

Just like knowledge transfer and knowledge sharing, the term "knowledge barriers" is not a uniformly defined term and differs in its meaning depending on the author.[63] Knowledge barriers can be associated with high costs for both companies and individuals.[64][65][66]

Knowledge retention

Knowledge retention is part of knowledge management. Knowledge retention is needed when expert knowledge workers leave the organization after a long career. [67] Retaining knowledge prevents losing intellectual capital. [68]

Knowledge retention projects are usually introduced in three stages: decision making, planning and implementation. There are differences among researchers on the terms of the stages. For example, Dalkir talks about knowledge capture, sharing and acquisition and Doan et al. introduces initiation, implementation and evaluation. [69][70] Furthermore, Levy introduces three steps (scope, transfer, integration) but also recognizes a “zero stage” for initiation of the project.[67]

See also

References

  1. "A Reference Model for Knowledge Retention within Small and Medium-Sized Enterprises". Proceedings of the International Conference on Knowledge Management and Information Sharing. Paris, France: SciTePress - Science and Technology Publications: 306–311. 2011. doi:10.5220/0003632003060311. ISBN 978-989-8425-81-2. 

External links

Wikiquote has quotations related to: Knowledge management
Wikimedia Commons has media related to Knowledge management.

 

Knowledge management

 

Management

 

Semantic Web

Authority control: National libraries Edit this at Wikidata

Knowing vs Understanding


Links  

https://en.wikipedia.org/wiki/Category:Knowledge_management

http://www.dmoz.org/Reference/Knowledge_Management/

Subcategories``ёёё]]]

 

`0-9`A

Informatio­n Assets

Informatio­n Architectu­re

`B

Business and Companies

`C

Case Studies

Knowledge Creation

` Customer knowledge

`D

Directorie­s

Knowledge Discovery

`E

► Evidence-based practices (4 C, 35 P)

Education

Employment

Events

`F

Knowledge Flow

`G

`H`I

`J

► Knowledge management journals (12 P)

`K

`L

`M

`N

`O

Organizati­ons

Online Teaching and Learning

Informatio­n Overload

`P

Publicatio­ns

`Q`R

Knowledge Representa­tion

Knowledge Retrieval

`S

Software

`T

`U

`V`W

Weblogs

`X`Y`Z

 

```ёёё[[[

 

``0-9``A

` ApexKB

``B

` Battle command

``C

` Cognitive assets

Corporate amnesia

Corporate history

CSHALS

Cynefin framework

``D

` Digital collaboration

DIKW pyramid

Duality (CoPs)

``E

` Eclipse (software suite)

``F

` Flow (software)

``G``H

` Human Terrain System

``I

` I-Space

Bell Ihua

Integration Objects

International Aging Research Portfolio

IT Resource Performance Management

ITRPM

``J

` Anthony Judge

``K

` Knowledge broker

Knowledge café

Knowledge inertia

Knowledge balance sheet

Knowledge management software

Knowledge market

Knowledge organization (management)

Knowledge Plaza

Knowledge policy

Knowledge spillover

Knowledge value

Knowledge-based engineering

KnowledgeBase Manager Pro

``L

` Legal case management

Legal matter management

``M

` List of knowledge management concepts

Battle command knowledge system

Mindbreeze

Oge Modie

Multiple-classification ripple-down rules

``N

` Narrative inquiry

National Centre for Science Information

NGenera CIM

Nuclear Knowledge Management

``O

` Open Semantic Framework

Oral debriefing

Organizational memory

``P

` Personal knowledge management

Process development execution system

Project blog

``Q

` Quality engineering

Question Manager

``R

Records Management Taxonomy

RIBA Knowledge Communities

Ripple-down rules

``S

` SECI model of knowledge dimensions

Semantic heterogeneity

Smartlogic

Dave Snowden

` USU Software

``T

` Tag management

Tephritid Workers Database

Teragram Corporation

``U

` USU Software

``V``W

Wellsprings of Knowledge

``X``Y``Z

Pages in Other Languages

Russian: управление знаниями

Categories:

Information systems

Groupware

Business terms

Hypertext

Comments (0)

You don't have permission to comment on this page.