4. Knowledge Creation & Architecture

8/14/2019 4. Knowledge Creation & Architecture

1/17

KNOWLEDGE CREATION& ARCHITECTURE


2/17

Knowledge Acquisition and KnowledgeCreation

is an on-going exercise

todays knowledge may or may not solve

tomorrows problems knowledge needs to be updated all the time

an activity enabled by technology and producedby people


3/17

Knowledge Creation & Transfer Througha Team

InitialKnowled

ge

TeamPerforms

a Job

New KnowledgeReusable bySame Teamon Next Job

OutcomeRealized

Knowledgecaptured

and codified in aform

usable by others

Outcome

comparedto Action

NewExperience/

KnowledgeGained


4/17

Conversion of Knowledge b/w Tacit& Explicit

Tacit to Tacit(Socialization)

Team Meetingsand Discussions

Explicit to Explicit(Communication)

E-mail a Report

Tacit to Explicit(Externalization)

Dialog within TeamAnswer Questions

Explicit to Tacit(Internalization)

Learn from Report


5/17

Processes and Activities

Gathering Data entryOCR and scanning Voice input

Pulling information from various sources includingInternet


6/17


OrganizingCataloging

Indexing Filtering

Linking


7/17


RefiningContextualizing

Collaborating

CompactingProjecting

Mining


8/17


Disseminating Flow

Sharing Alert

Push


9/17

Knowledge Architecture

a pre-requisite toknowledge sharing

infrastructure consists ofpeople, content andtechnology

are interdependent andinseparable

People having knowledge

provide content , relyingon technology to transferand share theknowledge.

People

Content

Technology


10/17

People

Knowledge workers, managers, customers,suppliers

Evaluate current information & documents used

by peopleApplications they need

People they contact for solution

Associates they collaborate with

Emails they send & receiveDatabase they use


11/17

Knowledge Network

mapped in such a way as to assign peopleauthority and responsibilities for specific kind ofknowledge content

Identifying Knowledge centers e.g. Sales,Products or Marketing etc.

Activating knowledge content satellite lowerlevel knowledge centers that hierarchically fall

under higher level centers Staffing/deploying proper experts at each of

these knowledge centers


12/17

Technical Core

encompasses the Hardware, Software and thespecialized human core

the speed, accuracy, reliability and of course

integrity is bound to be there In designing a KM system, it is prudent to tie

what is already available


13/17

Technical Core

Focus on real knowledge of people rather thanartificial intelligence

Finding the sources of know-how, not just the

know-how Tagged to collaboration

Concentrate on realism not perfection


14/17

Capturing Tacit Knowledge

Extract problem solving knowledge from humanexpert

Experts should give relevant information

All levels of experts should be used Single or multiple expert Interviews expert cannot convey the knowledge in

spite of being competent

Content of questions in an interview Interpret the experts answers correctly


15/17

Knowledge Codification

Knowledge maps, storyboarding knowledge etc.

is organizing and representing knowledge beforeit is accessed by the authorized person

converting tacit knowledge to explicit knowledgein a usable form

Converting undocumented to documentedinformation


16/17

Knowledge Codification

Tacit knowledge such as human expertise is identified and leveraged through a form that

delivers the highest return to the business

Explicit knowledge should be organized,categorized, indexed and accessed via thecompanys intranet or some other means tomake it visible, accessible and usable.


17/17

Knowledge Maps

visual representationYou cant verbalize unless you visualize way to codify the knowledge is to visualize tools to transform employees into knowledge

partners for effective decision making

Documents

4. Knowledge Creation & Architecture