• Save
Knowledge Management
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,296
On Slideshare
1,294
From Embeds
2
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
2

Embeds 2

http://www.linkedin.com 2

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Knowledge Engineering: The engineering discipline that involves integrating knowledge into computer systems in order to solve complex problems normally requiring a high level of human expertise. For example: mathematical logic, and artificial intelligence Agreed that IT is the biggest enabler of KM if used correctly; but Drucker warns that focusing on the “I” nit the “T” will deliver little. Intranets can be used as the front end for KM. Intranet is a part of equation that provides a stable messaging and collaborative platform Knowledge in its entirety can not be captured. An inevitable loss of context happens when documents are just codified for being used across organizations. Documentum example?????
  • Examples: Xerox PARC created a lot of knowledge bur Microsoft and Apple applied knowledge to make a difference. Create new markets, and generate economic value &0% of Ford’s cost are driven by it’s decisions made in the conceptual design stage, even though this stage accounts for 5% of the actual cost of a typical car. Most conceptual design and decision making are done by low technology media. By perfecting the design process Ford can ensure that the price tags on the cars remain competitive Page 84
  • Knowledge Centric awareness, distribution, application, creation, validation The failure of the companies knowing what they know The need to improve work processes thru improved distribution of knowledge The need for overcoming barriers to flow and retention of knowledge To unlearn what is no longer valid The culture of knowledge hoarding Technology Knowing how a type writer works does not turn someone into a writer. The companies that thrive are those that can use their IT assets to leverage their people’s knowledge in ways that are immediately applicable. the need for a perfect link between knowledge, biz strategy, and IT Organizational Structure functional convergence: assets, trust, ownership retaining project knowledge in a way to be reapplied Personnel need for improved knowledge transfer, sharing, and creation in cross-functional teams; reduce loss of organizational knowledge Process create process competence: avoid repeated mistake and unnecessary reinvention Economics knowing more about the same thing accelerate creation and application of knowledge Org the need to capture the decision-making process of your expert employees create a catalog of "explainable" decisions accumulate an auditable knowledge-base
  • Politically charged environment is ill suited for knowledge exchange and development
  • Knowledge creation process can be thought of those activities that surround the conversion of subjective tacit knowledge to objective explicit knowledge also called externalization. The key to knowledge creation lies in mobilization and conversion of the tacit knowledge –within and outside of the organization – to explicit knowledge Migratory knowledge is independent of its creator and owner. Movement of knowledge is the ability of transferring knowledge from one person or organization to another without losing it’s context and meaning
  • Know what to care why Knowledge involved in deliberation and alternate decisions that could have been made is generally lost in the process
  • Lack of support by the knowledge management system does not mean that a KM strategy con not support those levels. Know why is cause and effect; critical thinking, decision making
  • The colored boxes indicate the relative focus of the effort in each phase. In fact, every segment will receive some attention in every phase. There are three broad approaches to knowledge management. One is to create a system where all information goes to everybody, which is hugely inefficient; the second tells people what others think they need to know, which may not match their real needs; and the third enables them to find for themselves whatever they want to know. Companies like to say that they aim for the third approach, but they do not always find it easy.
  • Page 296
  • A standardized architecture will allow better inter-operability among online educational resources, cheaper and faster development of the resources, more robust indexing and searching, and the flexibility to share assets within and among .
  • Page 396 provide management flexibility to develop positions and employees and assign work through the development of broader, functionally-based classifications and broader, open salary ranges; create a pay-for-performance structure that allows managers to recognize and reward performance, development, and contribution; enhance employee opportunities for skill development, cross training, and promotion; and maintain a competitive job and salary structure to recruit and retain a highly qualified and productive work force.
  • The colored boxes indicate the relative focus of the effort in each phase. In fact, every segment will receive some attention in every phase.
  • Page 389 Rapid prototyping (results driven incremental methodology -- RDI) Series of non overlapping increments   Steps in RDI Methodology Business Release  (incremental segments of implementation) --Traps in release sequence --Process divisibility and RDI release RDI's Roles in Tool and Task Reinvention --Cross-functional synergy  (synergy between knowledge workers at different departments) --Complexities (cultural & technical) --Avoiding over-engineering ( functions & features that will never be used) --Developing of clear communication process  (maps) --Human barriers in technology design --An infinite loop
  • When the success factors are studied focus falls on the human aspects. A strong academic majority raises a big concern around this area. All agree that the intellectual assets of the employees are the foremost c r i t i c a l success factor. “Usually people begin a KM project by focusing on the technology needs. But the key is people and process.” (Shir Nir, 2002). The key to successful knowledge management (KM)‏ projects is focusing on people first, not cutting-edge technology. The biggest misconception that IT leaders make is that knowledge management is about technology," says Shir Nir, There is no "cookiecutter approach" to adopting knowledge management . http://hosteddocs.ittoolbox.com/KM21105.pdf Key Success Factors For Knowledge Management SUPERVISOR: PROF. DR. CHRISTOPH DESJARDINS INTERNATIONALES HOCHSCHULINSTITUT LINDAU, UNIVERSITY OF APPLIED SCIENCES/ FH KEMPTEN, GERMANY; DECEMBER 2004 SUPERVISOR: MR. STEFAN THEELEN, CIO METZELER GmbH, LINDAU, GERMANY; DECEMBER 2004

Transcript

  • 1. Workshop Knowledge Management
  • 2. Knowledge Management
    • Knowledge:
      • framed experience, values, contextual information, expert insight, grounded intuition
      • embedded in documents, repositories, routines, processes, practices, and norms
    • Knowledge Management:
      • systematic processes by which knowledge needed for an organization to succeed is created, captured, shared, and leveraged
  • 3. Focus of KM
    • Knowledge management is NOT about
      • knowledge engineering
      • digital networks; it’s about process
      • building a smarter intranet
      • knowledge capture
    • The primary focus of knowledge Management is on
      • creating, getting, importing, delivering, and most importantly helping the right people apply the righ t knowledge at the right time
  • 4. Value Proposition
    • W ithout effective mechanisms in place to capture and utilize knowledge of experienced employees, organizations make costly mistakes or have to pay again for knowledge they once had on tap
    • Organizations have saved significant resources a year by taking the knowledge from their best performers and applying it in similar situations elsewhere
      • KM can make a difference when it enables the application of knowledge
    • Organizations applying knowledge management methods have found that through knowledge networking they can create new products and services faster and better
      • integrated cross functional approach
  • 5. Knowledge Management Drivers
    • The failure of organizations to know what they already know
    • The need for smart knowledge distribution
    • High dependence on the know-how of walkouts
    • The need to support cross functional collaboration
    • The need to deal with complex expectations
    • The need to avoid repeated mistakes
    • The need to avoid reinvention
    • T he need to capture the decision-making process of your expert employees
    • Create a catalog of decision processes
    • Accumulate an auditable knowledge-base of decision-making and best practices
  • 6. Difficulties with KM
    • Lack of tangible outcome -- selling the idea to senior management
    • Building people to work around technology mentality
      • knowledge management is not a technology problem; it’s a process problem
    • Lack of incentives for knowledge contribution
    • Knowledge access is only the beginning of knowledge management
    • Knowledge management is an infinite loop that never ends
    • Organizational policies come into play when knowledge exists, is used, and is exchanged
      • ownership, changing user need, biz climate,
  • 7. Key Concepts
    • Categories of Knowledge
      • tacit
      • explicit
    • Components of Knowledge
      • emphasis on conversation and discussion
      • judgment
      • experiential knowledge
      • values, assumptions, and beliefs
      • intelligence
  • 8. The Three Fundamental Steps
    • Knowledge acquisition
      • process of development and creation of insights, skills, and relationships
    • Knowledge sharing
      • disseminating and making available what is already known
      • collaborative problem solving, conversations, teamwork generates knowledge assets
    • Knowledge utilization
      • available knowledge can be generalized and applied
  • 9. Knowledge Strategy
    • Knowledge drives strategy and strategy drives knowledge management
      • plan of action
      • one size does not fit all
      • don’t lock yourself in
    • Knowledge management strategy supports four levels of knowledge:
      • know-what
      • know-how
      • know-why
      • care-why
  • 10. Knowledge Map
    • A knowledge map is a graphic representation of the scope and structure of knowledge
    • Why Knowledge Mapping?
      • shared perception of gaps in critical knowledge
      • focus on the important knowledge
      • manage important information
      • understand the cause and effect relationships behind behavior
      • identify critical actions to take
      • defining critical thinking and decisions for getting the job done
      • needed information for making the decisions
      • keeps all the players on the same page
      • makes discussions more effective
  • 11. Our KM Approach Identify Map Capture Store Share Apply Create Prototyping Pilot Implementation Examples, experiments, case studies Full range of identified knowledge Live on HSA servers The relative emphasis shifts; all segments are relevant in all the phases, but the focus is stronger on some segments during each phase. Knowledge Process
  • 12. People,Process,Technology Leveraged Investment   Phase 1 Prototype Phase 2 Pilot Phase 3 Implementation   People   Developing KM strategy. approach HSA Team SMC-HSA Personnel   Process   Assessing Planning Design Test Full-scale Production   Technology   Enabling Tools Test Environment Integrated Platform with HSA IT System
  • 13. Maximizing the Use of Technology
    • Content Strategy
      • structure
      • metadata
        • tagging knowledge elements with attributes
    • System Components
      • repositories (knowledge servers)‏
      • collaborative platforms
      • networks
    • Adhering to Standards
      • fit into overall information technology architecture
      • interoperability
  • 14. Access, Share, Apply Users need a quick, easy and secure way to document, organize, classify, categorize, share, and track information
    • Communication
    • Collaboration
    • Teamwork
    Writing Proposals How to Use Mock Claim Researching Funds Know What Know How Know Why
  • 15. Knowledge Sharing Portal
  • 16. Assembling The Correct Tools
    • Knowledge mapping and related tools
    • Content management tools
    • Collaborative technologies
    • Process modeler tools
    • Content creation tools
  • 17. Knowledge Culture
    • Integrate knowledge sharing into daily work
    • Consistent and continual leadership
    • Visibility to top management
    • Rich collaborative environment for knowledge sharing and transfer
    • Time to engage in knowledge sharing
    • Systems are in place for capture through reuse of information
    • Supportive reward system
    • Organizational life-long learning
  • 18. Deployment Identify Map Capture Store Share Apply Create Prototyping Pilot Implementation Examples, experiments, case studies Full range of identified knowledge Live on HSA servers The relative emphasis shifts; all segments are relevant in all the phases, but the focus is stronger on some segments during each phase.
  • 19. Deployment Plan
    • Rapid prototyping  
      • Iterative process
      • instant feedback and modification
      • low risk
    • Pilot Deployment
      • small-scale implementation
      • culture (rubber meets the road)‏
      • identifying requirements for fitting into the existing information technology architecture
    • Implementation
      • live on HSA IT infrastructure
  • 20. Case Study
    • Case Study at Cisco
      • estimating time frame for implementing KM projects
      • approach
      • lessons learned - common mistakes
        • compensation systems that don’t support knowledge sharing and teamwork
        • building a “Grand Database in the Sky”
        • allowing technology to dictate development
        • failure to coordinate and involve top management and the users
      • success factors
        • focus on people and process