Knowledge management

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found.


Knowledge management (KM) is the process of capturing, developing, sharing, and effectively using organizational knowledge.[1] It refers to a multi-disciplinary approach to achieving organizational objectives by making the best use of knowledge.[2]

An established discipline since 1991 (see Nonaka 1991), KM includes courses taught in the fields of business administration, information systems, management, and library and information sciences.[3][4] More recently, other fields have started contributing to KM research, including information and media, computer science, public health, and public policy.[5] Several Universities now offer dedicated Master of Science 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, information technology, or human resource management departments.[6] Several consulting companies provide strategy and advice regarding KM to these organisations.[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] KM 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 a focus on encouraging the sharing of knowledge.[2][8] It is an enabler of organisational learning.[9][10]

History

Knowledge management efforts have a long history, to include 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, knowledge 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.[11]

In the enterprise, early collections of case studies recognized the importance of knowledge management dimensions of strategy, process, and measurement.[12][13] 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 organizational 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.[13] In short, knowledge management programs can yield impressive benefits to individuals and organizations if they are purposeful, concrete, and action-orientated.

Research

KM emerged as a scientific discipline in the earlier 1990s.[14] It was initially supported solely by practitioners, when Skandia hired Leif Edvinsson of Sweden as the world's first Chief Knowledge Officer (CKO).[15] Hubert Saint-Onge (formerly of CIBC, Canada), started investigating KM long before that.[2] The objective of CKOs is to manage and maximize the intangible assets of their organisations.[2] Gradually, CKOs became interested in practical and theoretical aspects of KM, and the new research field was formed.[16] Discussion of 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][17] 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 organisations.[18] Since its establishment, the KM discipline has been gradually moving towards academic maturity.[2] First, there is a trend toward higher cooperation among academics; particularly, there has been a drop in single-authored publications. Second, the role of practitioners has changed.[16] Their contribution to academic research has been dramatically declining from 30% of overall contributions up to 2002, to only 10% by 2009 (Serenko et al. 2010).[19]

A broad range of thoughts on the KM discipline exist; approaches vary by author and school.[16][20] As the discipline matures, academic debates have increased regarding both the theory and practice of KM, to include the following perspectives:

Regardless of the school of thought, core components of KM include people, processes, technology (or) culture, structure, technology, depending on the specific perspective (Spender & Scherer 2007). Different KM schools of thought include lenses through which KM can be viewed and explained, to include:

The practical relevance of academic research in KM has been questioned (Ferguson 2005) with action research suggested as having more relevance (Andriessen 2004) and the need to translate the findings presented in academic journals to a practice (Booker, Bontis & Serenko 2008).[12][12][29][30]

Dimensions

Different frameworks for distinguishing between different 'types of' knowledge exist.[10] One proposed framework for categorizing the dimensions of knowledge distinguishes between tacit knowledge and explicit knowledge.[27] Tacit knowledge represents internalized knowledge that an individual may not be consciously aware of, such as how he or she accomplishes 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. (Alavi & Leidner 2001).[16] Similarly, Hayes and Walsham (2003) describe content and relational perspectives of knowledge and knowledge management as two fundamentally different epistemological perspectives.[31] The content perspective suggest that knowledge is easily stored because it may be codified, while the relational perspective recognizes the contextual and relational aspects of knowledge which can make knowledge difficult to share outside of the specific location where the knowledge is developed.[31]

The Knowledge Spiral as described by Nonaka & Takeuchi.

Early research suggested that a successful KM effort needs to convert internalized tacit knowledge into explicit knowledge to share it, and the same effort must permit individuals to internalize and make personally meaningful any codified knowledge retrieved from the KM effort.[6][32] Subsequent research into KM suggested that a distinction between tacit knowledge and explicit knowledge represented an oversimplification and that the notion of explicit knowledge is self-contradictory.[11] Specifically, for knowledge to be made explicit, it must be translated into information (i.e., symbols outside of our heads) (Serenko & Bontis 2004).[11] Later on, Ikujiro Nonaka proposed a model (SECI for Socialization, Externalization, Combination, Internalization) which considers a spiraling knowledge process interaction between explicit knowledge and tacit knowledge (Nonaka & Takeuchi 1995).[33] In this model, knowledge follows a cycle in which implicit knowledge is 'extracted' to become explicit knowledge, and explicit knowledge is 're-internalized' into implicit knowledge.[33] 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 forwards (Nonaka, von Krogh & Voelpel 2006);[34] (Nonaka, von Krogh & 2009).[4]

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

A third proposed framework for categorizing the dimensions of knowledge 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.[31][36] Collaborative environments such as communities of practice or the use of social computing tools can be used for both knowledge creation and transfer.[36]

Strategies

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

One strategy to KM involves actively managing knowledge (push strategy).[7][39] 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 to the repository.[39] This is commonly known as the Codification approach to KM.[39]

Another strategy to KM involves individuals making knowledge requests of experts associated with a particular subject on an ad hoc basis (pull strategy).[7][39] In such an instance, expert individual(s) can provide their insights to the particular person or people needing this (Snowden 2002).[27] This is commonly known as the Personalisation approach to KM.

Hansen et al. propose a simple framework, distinguishing two opposing KM strategies: codification and personalization.[40] Codification focuses on collecting and storing codified knowledge in previously designed electronic databases to make it accessible to the organisation.[41] Codification can therefore refer to both tacit and explicit knowledge.[42] In contrast, the personalization strategy aims at encouraging individuals to share their knowledge directly.[41] Information technology plays a less important role, as it is only supposed to facilitate communication and knowledge sharing among members of an organisation.

Other knowledge management strategies and instruments for companies include:[7][23][27]

  • 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)
  • 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
  • Competence management (systematic evaluation and planning of competences of individual organisation members)
  • Proximity & architecture (the physical situation of employees can be either conducive or obstructive to knowledge sharing)
  • Master-apprentice relationship
  • Collaborative technologies (groupware, etc.)
  • Knowledge repositories (databases, bookmarking engines, etc.)[43][44][45]
  • 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 whom to talk about a specific subject)
  • Social software (wikis, social bookmarking, blogs, etc.)
  • Inter-project knowledge transfer

Motivations

There are a number of claims as to the motivation leading organisations to undertake a KM effort.[46] Typical considerations driving a KM effort include:[27]

  • Making available increased knowledge content in the development and provision of products and services
  • Achieving shorter new product development cycles
  • Facilitating and managing innovation and organisational learning
  • Leveraging the expertise of people 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 intellectual assets in the workforce (such as the expertise and know-how possessed by key individuals or stored in repositories)

Debate exists whether KM is more than a passing fad, though increasing amount of research in this field may help to answer this question, as well as create consensus on what elements of KM help determine the success or failure of such efforts (Wilson 2002).[47] Knowledge sharing remains a challenging issue for knowledge management, while there is no clear agreement barriers may include time issues for knowledge works, the level of trust, lack of effective support technologies and culture (Jennex 2008).[48]

KM Technologies

Knowledge Management (KM) technology can be divided into the following general categories:

Groupware refers to technologies that facilitate collaboration and sharing of organizational information. One of the earliest very successful products in this category was Lotus Notes. Notes provided tools for threaded discussions, sharing of documents, organization wide uniform email, etc.
Workflow tools allow the representation of processes associated with the creation, use, and maintenance of organizational knowledge. For example the process to create and utilize forms and documents within an organization. For example, a workflow system can do things such as send notifications to appropriate supervisors when a new document has been produced and is waiting their approval.
Content/Document Management systems are systems designed to automate the process of creating web content and/or documents within an organization. The various roles required such as editors, graphic designers, writers, and producers can be explicitly modeled along with the various tasks in the process and validation criteria for moving from one step to another. All this information can be used to automate and control the process. Commercial vendors of these tools started to start either as tools to primarily support documents (e.g., Documentum) or as tools designed to support web content (e.g., Interwoven) but as the Internet grew these functions merged and most vendors now perform both functions, management of web content and of documents. As Internet standards became adopted within most organization Intranets and Extranets the distinction between the two essentially went away.
Enterprise Portals are web sites that aggregate information across the entire organization or for groups within the organization such as project teams.
eLearning technology enables organizations to create customized training and education software. This can include lesson plans, monitoring progress against learning goals, online classes, etc. eLearning technology enables organizations to significantly reduce the cost of training and educating their members. As with most KM technology in the business world this was most useful for companies that employ knowledge workers; highly trained staff with areas of deep expertise such as the staff of a consulting firm. Such firms spend a significant amount on the continuing education of their employees and even have their own internal full-time schools and internal education staff.
  • Scheduling and planning
Scheduling and planning tools automate the creation and maintenance of an organization's schedule: scheduling meetings,notifying people of a meeting, etc. An example of a well known scheduling tool is Microsoft Outlook. The planning aspect can integrate with project management tools such as Microsoft Project. Some of the earliest successful uses of KM technology in the business world were the development of these types of tools, for example online versions of corporate "yellow pages" with listing of contact info and relevant knowledge and work history.[21]
Telepresence technology enables individuals to have virtual meetings rather than having to be in the same place. Videoconferencing is the most obvious example.

These categories are neither rigidly defined nor exhaustive. Workflow for example is a significant aspect of a content or document management system and most content and document management systems have tools for developing enterprise portals.[7][49]

One of the most important trends in KM technology was the adoption of Internet standards. Original KM technology products such as Lotus Notes defined their own proprietary formats for email, documents, forms, etc. The explosive growth of the Internet drove most vendors to abandon proprietary formats and adopt Internet formats such as HTML, HTTP, and XML. In addition, open source and freeware tools for the creation of blogs and wikis now enable capabilities that used to require expensive commercial tools to be available for little or no cost.[30][50]

One of the most important ongoing developments in KM technology is adoption of tools that enable organizations to work at the semantic level.[51] Many of these tools are being developed as part of the Semantic Web.[52] For example, the Stanford Protege Ontology Editor.

See also

Journals

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 7.5 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Sanchez, R (1996) Strategic Learning and Knowledge Management, Wiley, Chichester
  10. 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 16.3 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 27.2 27.3 27.4 Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 31.2 Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. 33.0 33.1 Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 39.2 39.3 Lua error in package.lua at line 80: module 'strict' not found.
  40. Hansen et al., 1999
  41. 41.0 41.1 Smith (2004), p. 7
  42. Hall (2006), pp. 119f
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.

External links