Chief knowledge officer: Difference between revisions
Content deleted Content added
m →External links: minor using AWB |
m Reverted edit by 2A02:3037:403:462C:7432:159A:487E:A257 (talk) to last version by Biogeographist |
||
| (31 intermediate revisions by 26 users not shown) | |||
| Line 1: | Line 1: | ||
A '''chief knowledge officer''' ('''CKO''') is a loosely defined role in some organizations that achieved some prominence during the 1990s and 2000s that supervises [[knowledge management]]. In general, their duties involve [[intellectual capital]] and organizing preservation and distribution of knowledge in an organization.<ref>Dalkir, K, (2005). Knowledge Management in Theory and Practice. Jordan Hill, Oxford: Elsevier Inc. 330</ref> The position sometimes overlaps with the title of "[[chief information officer]]"; CIOs tend to be more focused on information technology within an organization (computer systems and the like), while CKOs have more nebulous portfolios including matters such as overseeing [[patent]] applications, internal training and documentation, [[knowledge sharing]], and promoting innovative research. |
|||
{{refimprove|date=January 2008}} |
|||
{{Buzzword|date=July 2011}} |
|||
CKOs are frequently directly appointed by the [[CEO]] given their broad domains, since their responsibilities generally cut across organizational boundaries.<ref name="sloan">[https://sloanreview.mit.edu/article/what-is-a-chief-knowledge-officer/ What Is a Chief Knowledge Officer?]</ref> As a result, exactly what a CKO works on can vary greatly from organization to organization. |
|||
A '''chief knowledge officer''' ('''CKO''') is an organizational leader, responsible for ensuring that the organization maximizes the value it achieves through "[[knowledge]]". The CKO is responsible for managing intellectual capital and the custodian of Knowledge Management practices in an organization.<ref>Dalkir, K, (2005). Knowledge Management in Theory and Practice. Jordan Hill, Oxford: Elsevier Inc. 330</ref> CKO is not just a relabelling of the title "[[chief information officer]]" - the CKO role is much broader. CKOs can help an organization maximize the returns on investment in knowledge (people, processes and [[intellectual capital]]), exploit their intangible assets (know-how, [[patent]]s, customer relationships), repeat successes, share [[best practices]], improve innovation, and avoid knowledge loss after organizational restructuring. |
|||
By the 2010s, the role became less common; while knowledge management programs are still an important part of corporations and other organizations, a direct officer called Chief Knowledge Officer has fallen out of favor somewhat.<ref>[https://www.kmworld.com/Articles/Editorial/ViewPoints/The-death-of-the-chief-knowledge-officer-106344.aspx The death of the chief knowledge officer]</ref> |
|||
CKO responsibilities include such things as: |
|||
*Collecting relevant data that is useful for the organization as knowledge |
|||
*Developing an overall framework that guides [[knowledge management]] |
|||
*Actively promoting the knowledge agenda within and beyond the company |
|||
*Overseeing the development of the knowledge infrastructure |
|||
*Facilitating connections, coordination and communications. |
|||
CKOs must have skills across a wide variety of areas. They must be good at developing/understanding the big picture, advocacy (articulation, promotion and justification of the knowledge agenda, sometimes against cynicism or even open hostility), project and people management (oversight of a variety of activities, attention to detail, ability to motivate), communications (communicating clearly the knowledge agenda, have good listening skills and be sensitive to organizational opportunities and obstacles), [[leadership]], [[teamwork]]ing, influencing, and [[interpersonal skills]]. The CKO who successfully combines these skills is well equipped as an excellent [[agent of change]] for their organization. |
|||
Other terms for CKO include knowledge manager, director intellectual capital (e.g. Scandia), director knowledge transfer (e.g. Buckman Laboratories), and knowledge asset manager (e.g. Dow Chemical). |
|||
==Knowledge Management Initiative== |
|||
Sunassee and Sewry<ref>Nakkiran N Sunassee and David A Sewry, “A Theoretical Framework for Knowledge Management Implementation”. ACM International Conference Proceeding Series; Vol. 30. Proceedings of the 2002 annual research conference of the South African institute of computer scientists and information technologists on Enablement through technology, Port Elizabeth, South Africa, p. 235 – 245. [http://portal.acm.org/citation.cfm?id=581539&coll=Portal&dl=ACM&CFID=60827173&CFTOKEN=60920289]</ref> argue that top management needs to create and share a vision for the knowledge management initiative. The vision is the long-term strategy that will drive the knowledge management initiative and provide the scope within which the knowledge management effort and the organization will grow. The vision should also encompass the core beliefs and values of the organization. |
|||
The creation of the vision can be done in two ways. Top management can either appoint a Chief Knowledge Officer (CKO), who will create the vision, or they can create a vision and entrust the CKO to carry it out. It is extremely important at this point that the employees of the organization are allowed to share in the making of vision of the organization. This will create a sense of belonging for the employees, and allow them to participate in the change process. It will also make them accept the change process more readily than if they were not allowed to participate in it. |
|||
The views of the employees in the organisations should be considered and there should be a proper system created to share the views. |
|||
| ⚫ | |||
Sunassee and Sewry propose a ''knowledge life-cycle'' in order to create and maintain individual and organizational learning in the organization: |
|||
#Create new knowledge |
|||
##Identify new knowledge |
|||
##Identify old and existing knowledge |
|||
#Identify knowledge relevant to organization |
|||
#Verify selected knowledge |
|||
#Capture and organize knowledge |
|||
#Disseminate and use knowledge |
|||
#Combine new knowledge and re-evaluate assumptions to create knowledge |
|||
The CKO should actively manage all stages of the ''knowledge life-cycle'', but most importantly encourage people to disseminate knowledge, and to use it. The last step of the cycle involves re-evaluating assumptions held by the organization and using these new assumptions with the knowledge created by the organization to create new knowledge. This process will generate innovative knowledge and allow the organization to produce innovative products and business processes. |
|||
==Other CKO tasks== |
|||
* Encourage individual learning and [[innovative]] thinking |
|||
* Implement reward plans and incentives |
|||
* Determine what technology is needed for the knowledge management effort and implement these technologies. |
|||
* Put processes in place in order to facilitate the creation of organizational learning. |
|||
* Measure the impact of knowledge management on the business. |
|||
==Roles a CKO must play== |
|||
<ref>Bontis, N, (2001). CKO Wanted — Evangelical Skills Necessary: A Review of the Chief Knowledge Officer Position. Knowledge and Process Management, Volume 8, Number 1. pp 29–38</ref> |
|||
* CKO as Knowledge-sharing Icon |
|||
* CKO as Trust Steward |
|||
* CKO as Total Trainer |
|||
* CKO as Techno Nerd |
|||
* CKO as Number-crunching Accountant |
|||
==References== |
==References== |
||
{{Reflist}} |
|||
<references /> |
|||
==External links== |
==External links== |
||
*[http://www.skyrme.com/insights/27cko.htm David Skyrme, Do you need a CKO] |
|||
* National Library for Health [http://www.library.nhs.uk/knowledgemanagement/SearchResults.aspx?searchText=chief&tabID=289 Knowledge Management Specialist Library] - collection of resources to support Chief Knowledge Officers. |
|||
* The US Army Knowledge Management CKO Resource Page [https://www.us.army.mil/suite/page/411380 Dr. Bob Nielson, Army Advisor to the CIO/CKO] - Website of resources to support Chief Knowledge Officers. |
|||
{{Corporate titles}} |
{{Corporate titles}} |
||
| ⚫ | |||
[[Category:Management occupations]] |
[[Category:Management occupations]] |
||
[[Category:Corporate executives]] |
|||
[[de:Chief Knowledge Officer]] |
|||
[[ko:최고지식책임자]] |
|||
[[ja:最高知識責任者]] |
|||
[[pt:Chief Knowledge Officer]] |
|||
Latest revision as of 10:41, 11 August 2024
A chief knowledge officer (CKO) is a loosely defined role in some organizations that achieved some prominence during the 1990s and 2000s that supervises knowledge management. In general, their duties involve intellectual capital and organizing preservation and distribution of knowledge in an organization.[1] The position sometimes overlaps with the title of "chief information officer"; CIOs tend to be more focused on information technology within an organization (computer systems and the like), while CKOs have more nebulous portfolios including matters such as overseeing patent applications, internal training and documentation, knowledge sharing, and promoting innovative research.
CKOs are frequently directly appointed by the CEO given their broad domains, since their responsibilities generally cut across organizational boundaries.[2] As a result, exactly what a CKO works on can vary greatly from organization to organization.
By the 2010s, the role became less common; while knowledge management programs are still an important part of corporations and other organizations, a direct officer called Chief Knowledge Officer has fallen out of favor somewhat.[3]
References
[edit]- ^ Dalkir, K, (2005). Knowledge Management in Theory and Practice. Jordan Hill, Oxford: Elsevier Inc. 330
- ^ What Is a Chief Knowledge Officer?
- ^ The death of the chief knowledge officer