• Save
The Ivory Tower: The Knowledge Management Fable
Upcoming SlideShare
Loading in...5

The Ivory Tower: The Knowledge Management Fable



You can find the full story at http://delarue.net/blog/docs/ by Keith De La Rue. ...

You can find the full story at http://delarue.net/blog/docs/ by Keith De La Rue.

Presentation on Knowledge Management, Knowledge Creation, by studying the story of The Ivory Tower.



Total Views
Views on SlideShare
Embed Views



8 Embeds 51

http://www.slideshare.net 42
http://maurosuzuki.blogspot.com 3
http://www.lmodules.com 1
http://maurosuzuki.blogspot.com.br 1
http://www.docshut.com 1
https://drive.jolicloud.com 1
http://localhost 1
http://www.slideee.com 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.


15 of 6 Post a comment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Excelente!!! En nuestros proyectos de consultoría e implementación de Tecnologías siempre contemplamos el componente de comunicación organizacional. Una buena caracterización de las empresas desde el punto de vista de la Gestión del Conocimiento debe incluir al menos la evaluación de los medios de comunicación empleados, debe abarcar todos los componentes y actores del proceso comunicativo, emisor, receptor, canales, medios, mensaje, intensión, etc. sin olvidar los componentes típicos de la Teoría General de Sistemas los mecanismos de control y retroalimentación en el proceso comunicativo.
    Are you sure you want to
    Your message goes here
  • Good and simple - read Keith De La Rue story as well and this is very useful
    Are you sure you want to
    Your message goes here
  • OK.. looks like it's there.
    Are you sure you want to
    Your message goes here
  • No, I got the material from my Knowledge Management class. Not sure if my lecturer is a CPA member though. Trying to post your blog link to the description part above, but not sure why it is not displayed there.
    Are you sure you want to
    Your message goes here
  • Hey - nice slide pack. Did you pick this material up as a CPA member? Just thought you may like to add a link to the original story - it's on my blog at http://delarue.net/blog/docs/

    Keith De La Rue

    Author, 'The Ivory Tower'
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

The Ivory Tower: The Knowledge Management Fable The Ivory Tower: The Knowledge Management Fable Presentation Transcript

  • THE IVORY TOWER The Knowledge Management Fable By: June Mook Pol Priw KM: 2/ 2007
  • Agenda (Knowledge Creation Focus)
    • The Ivory Tower
      • Situation
      • Problems
      • Solutions
      • Benefits
    • Real Business
    • Lessons-learnt
  • Situation
    • Wizards lived in the Ivory Tower, and knew many things (Source of knowledge)
    • Serfs , farmers, had problems with their farms (Those who needed knowledge)
    • King asked Wizards to help (The person who wanted to see the available knowledge used)
    View slide
  • Problems
    • Serfs’ farming was still unsuccessful although Wizards claimed that they told what they knew.
    • Both Serfs and Wizards blamed each other.
      • Serfs said Wizards did not really help. What Wizards told were useless.
      • Wizards said Serfs understood something so hard that Serfs had to come back to see them again and again. They then could not do their work, while Serfs did not actually apply all knowledge from them for farming.
    View slide
  • Problems with Wizards
    • Used their own technical language (techknowspeak), while most Serfs understand only plain language.
    • Understood that only their techknowspeak could communicate their knowledge well and completely.
    • Not contributed themselves in sharing knowledge (time/ place)
    • Not concerned of Serfs’ environment, culture, and communication style while giving out knowledge (receivers)
  • Problems with Serfs
    • Did not share knowledge among themselves (Source of knowledge)
    • Did not understand jargons used by Wizards (Levels of language)
    • Hence, did not take any action (Unsuccessful)
  • Main Problems
    • Unclear concept/ vision of knowledge sharing
    • Communications break-down
    • Ineffective channels of knowledge distribution
    • Lack of knowledge filters
  • Solutions
    • King got Knowms to solve problems.
    • Knowms’ background
      • Be able to communicate
      • Understand the knowledge
    • Before knowledge management
      • Knowms talked with Wizards and took notes on method of transferring knowledge, Serfs’ problems, knowledge required by Serfs.
      • Knowms talked with different groups of Serfs about their problems and knowledge they needed.
  • Solutions
    • New motto ‘Sharing knowledge is power.’ (say, ‘ Effectively sharing knowledge is power,’ the vision .)
      • Set up vision, i.e. motto.
      • Developed and defined the vision (i.e. used common-tongue) .
    • Atmosphere and urge of knowledge sharing
    • Libraries, cities, meetings, farms, etc. (Ba)
    • Knowledge assets
      • Categorised knowledge into groups according to Serfs’ requirements
      • Used templates for different types of knowledge needed to be collected for each specific group of Serfs (acts as a filter)
    • SECI model
  • ‘ Sharing knowledge is power.’ E.g. common-tongue language Urge sharing activities, singing songs Categories of knowledge for each group of Serfs Libraries, cities, meetings SECI Lead SECI Knowledge-creating Process
  • SE..
    • S ocialisation Tacit-to-Tacit
    • Knowms observed how some skillful Serfs did farming.
    • Troubadours travelled around, and knew a lot about Serfs and environment outside (can be by observing as well) .
    • E xternalisation Tacit-to-Explicit
    • Knowms noted down what they had observed from Serfs.
    • Some successful Serfs, who could do the farming well, told other Serfs how to farm.
  • ..CI
    • C ombination Explicit-to-Explicit
    • Composing songs from the available knowledge.
    • Having discussions among Knowms and Wizards for additional knowledge
    • Knowms noted down knowledge told by Wizards.
    • I nternalisation Explicit-to-Tacit
    • Hearing the songs and could applying them to farming.
    • Putting parchments in libraries.
    • Troubadours travelled around and sang songs.
  • Solutions
    • Change Management
      • Competition of farming products
      • Rewarding
      • Reputation
      • Honours (from King to Wizards)
    • Monitoring
      • Meetings for improvements
      • Knowledge updates
  • Benefits
    • More time for Wizards to do something else, instead of re-telling the same information (time saving)
    • Wizards may even spend the available time to create more knowledge.
    • Accesses to knowledge are various and more convenient
    • Availability of environment and atmosphere of knowledge sharing
    • Finally, successful farming
  • Real Business Soft Square Group
    • King
    • CEO
  • Real Business Soft Square Group
    • Serfs
    • Junior Programmers
  • Real Business Soft Square Group
    • Wizards
    • Senior Programmers/ System Analysts
  • Real Business Soft Square Group
    • Knowms
    • Knowledge Management Team
  • Lessons-learnt
    • Should have CEO buy-in
    • Knowledge vision needs to clearly communicated.
    • Each person needs different knowledge (filters).
    • Each person can gain knowledge through different communication methods .
    • Those who will take care of knowledge management should understand and can communicate the problems, the required knowledge, and the source of knowledge.
    • Contribution is needed to do knowledge management.
    • Effective communication is an important factor to be successful in knowledge management.
    • Each organisation needs different knowledge; thus the same knowledge or methods of sharing knowledge in one organisation may not be applicable with others .
    • Resistance to change normally happens, so plan for managing it.
    • Improvements and monitoring the process should be done.
  • T H A N K Y O U !