Notes on Knowledge Management

-
 

Knowledge transfer

  • Tacit – Tacit: conversation, dialogue & meetings
  • Tacit – Explicit: creation of documents, messages, memos & reports
  • Explicit – Explicit: creation of directories, maps
  • Explicit – Tacit: documents & data

 

Benefits of Knowledge Transfer & Sharing

  1. transfer problem-solving skills (reuse of)
  2. induction
  3. training & sharing of war-stories
  4. adopting best practices

What is?

  • Data – raw information & material
  • Knowledge – information interpreted & put within context

 

To Instill Changes

  1. introduce management initiatives (e.g. TQM)
  2. focus on the customer
  3. re-engineer the business
  4. empower the workers
  5. create cross-functional teams

Extent of Cultural Shift & Changes

Conflict – coexistence – cooperative – collaborative

 

Innovation Teams Needs

  1. autonomy
  2. to be multi-disciplinary
  3. connection to learning networks (IHL, vendors, R&D)
  4. connection to customers
  5. connection to value-web
  6. to be skilled in innovation disciplines
  7. to be incentivised (reward both failures & successes)
  8. to be measured
  9. to be sponsored/ supported

Knowledge-Innovation Cycle

  1. knowledge creation
  2. knowledge application
  3. invention
  4. invention diffusion
  5. innovation
  6. new knowledge sources
  7. application of new knowledge

Disciplines of a Learning Organisation

  • personal mastery – continuously developing oneself
  • metal models – of the organisation, linear or lateral thinking
  • shared vision – with the rest of the staff/ organisation
  • team learning
  • systems thinking – integrate the above 4

Comments

Post a Comment

Popular posts from this blog

Understanding ITIL Service Management the UML way…

-
Image
I originally had a great deal of difficult reconciling the differences amongst ITIL Change Management, Incident Management, and Problem Management. Having researched on the subjects and understanding them better now, I’ve tried to put the concepts together using a UML class diagram to capture my understanding and to keep it imprinted. Similarly, I wanted to differentiate the various categories of changes (Standard, Emergency, Normal) using an easy to understand & self-explanatory manner – a UML Activity Diagram!
Read more

How to depict (Professional-Looking) Logical Network Diagrams in Astah

-
Image
I have always had to create (professional-looking) UML diagrams using Visio-like icons. You’ve got to admit that showing a bunch of boring UML boxes hardly interests anyone less technical (like anyone whose designation has the words “manager” or “director”). This is actually possible in Astah! I’ve created a template for future projects that allows me to produce logical network diagrams that look like the following: To create this diagram, you need to do the following: Assign various icons to stereotypes. I created the following for my use: Create a new UML Deployment Diagram Every element in the diagram is created as a Node The nodes are subsequently assigned the appropriate <<stereotype>>. E.g. Internet is <<internet>>, WebZone FW is <<firewall>>, Web LB is <<loadBalancer>> Ensure the “Icon Notation” is set to “Customized Icon” for each node Instead of the boring boxes, the corresponding icons automatically gets displayed!
Read more