Modul 3 knowledge mapping

Knowledge ManagementStrategy & Program

Bandung, 10-11 April 2012

Moh. Haitan Rachman

E : [email protected]

[email protected]

W : haitanrachman.wordpress.com

FB: facebook.com/haitanrachman

T : twitter.com/haitanrachman

Agenda

1. Day – 1 Fundamental, Concept, Systems

a) Knowledge Management Fundamentals

b) Knowledge Management Tools

c) Knowledge Mapping

d) Knowledge Management System

2. Day – 2 Penyusunan KM Programs

a) KM Strategy

b) KM Roadmap

c) K-Map

d) KM Programs

www.mobileskycode.com www.multiforma.co.id

MODULE 3:Knowledge Mapping


Knowledge Mapping Overview

1. What is Knowledge Mapping?

2. Why Knowledge Mapping?

3. How to Map?


What Is Knowledge Mapping?

vIs a process of surveying, assessing and linking the information, knowledge, competencies and proficiencies held by individuals and groups within an organization (Dr Ann Hylton, KeKma-

Training2002)



v An ongoing quest within an organization (including its

supply and customer chain) to:

Ø Help discover the location, ownership, value and

use of knowledge artifacts,

Ø Learn the roles and expertise of people,

Ø Identify constraints to the flow of knowledge,

and

Ø Highlight opportunities to leverage existing

knowledge.

v It illustrates or "maps" how knowledge flows

throughout an organization.

(D. Grey, 2002 Smith Weaver Smith Inc)



v Knowledge mapping is a process by which organizations can identify and categorize knowledge assets within their organization –people, processes, content, and technology.

v It allows an organization to fully leverage the existing expertise resident in the company, as well as identify barriers and constraints to fulfilling strategic goals and objectives.

v It is constructing a roadmap to locate the information needed to make the best use of resources, independent of source or form.

(W. Vestal, APQC, 2002)



v A Knowledge Map describes what knowledge is used in a process, and how it flows around the process. It is the basis for determining knowledge commonality, or areas where similar knowledge is used across multiple processes.

v Fundamentally, a process knowledge map contains information about the organization’s knowledge. It describes who has what knowledge (tacit), where the knowledge resides (infrastructure), and how the knowledge is transferred or disseminated (social).

(IBM Global Services -Technique Paper, 2000)


Ø Organizations use knowledge maps for a number of different reasons. Some organizations compile company locators to find internal and external resources.

Ø Others use them to identify knowledge sharing opportunities or knowledge barriers within cross-functional work groups.

Ø Many companies use knowledge mapping before developing formal communities of practice or After-Action Reviews.

Why Map?


1. Compile company locators –internal and external resources -KM Yellow Pages

2. Identify opportunities to reuse information

3. Locate naturally-occurring know ledge stew ards

4. Identify knowledge dependencies w ithin cross-functional w ork groups

5. Categorize value-added information resident w ithin your organization

6. Identify knowledge sharing opportunities

7. Precursor to developing formal communities of practice (CoP)

8. Create a knowledge tool that helps users find w hat they need (e.g. Agricultural Trade Programming Tool).

Uses of Knowledge Maps

1. Identifies the core and contextualknowledge inside of an organization

2. How information and knowledge flows

3. What individual knowledge or expertise is critical to a process or focus area

What A Knowledge Map Reveals ...


Organizations should not design a KM approach without first mapping their knowledge.

Within the context of APQC’s Road Map to Knowledge Management, mapping knowledge is recommended in stage 2 (develop a strategy) or stage 3 (design and launch a knowledge management initiative).

When To Map

1. Enterprise Knowledge Map - level:

Ø Strategic business, technical, market knowledge

Ø Determine the organization’s “bench strength”

Ø Identify areas to focus KM efforts

2. Cross-functional Knowledge Map - between divisions/business groups level

Ø Operational assessment of working knowledge

1. Working group/process Knowledge Map:

Ø Tactical and operational knowledge applied to process excellence, innovation, customer relationship

STR

AT

EG

ICT

AC

TICKnowledge Mapping: Where to Focus?

Enterprise Knowledge Map(Strategic Level)

Cross-Functional Knowledge Map(Strategic Level)

Process Knowledge Map (Tactic Level)

Types of Knowledge Maps

Ø A method of analysis to define the know ledge needed and the know ledge available to support a business process.

Ø Knowledge Mapping identifies the:

§ Explicit knowledge(knowledge artifacts)

§ Tacit know ledge(undocumented information, expertise in people’s heads)

§ Infrastructure (w here does it the reside)

§ Organization ( w ho and w here are the people)

Ø In context of a specific business process

Process Knowledge Mapping

PROCESSWhat

Knowledge Is Needed?

Who Has It?

Who Needs

It?

Where Is It?

Is It Tacit Or Explicit?

Is It Routine Or Non-routine?

What Issue(s) Does It

Address?

System Analysis

Database Design

Layout Design

CodeProgram

Process-Knowledge Mapping Analysis Matrix


Knowledge Map Development and Tools


Knowledge Map Development and Tools

1. Diagram Flow: Microsoft Visio,

Microsoft Powerpoint, SmartDraw

2. E-R Diagram: Sybase Powerdesigner,

ER-Win, DbWrench

3. Mind Mapping: XMind, MindManager

4. Hierarchy Notes: Microsoft Notes

5. Content Management: Dotnetnuke,

Wordpress, Joomla, Drupal


(1) Diagram Flow

1. Competency Directory

2. Cycle Business Process


Competency-1 Competency-2 Competency-3 Competency-4 Competency-5 Competency-6

Competency Directory

Knowledge Directory

Competency Directory


Knowledge Directory

Phase

Objectives

Phase

Objectives

Phase

Objectives

Phase

Objectives

Cycle Business Process


(2) E-R Diagram

1. Simple E-R

2. Customer Relationship

Management (CRM)

3. Improvement and Problem

Handling


Simple E-R Diagram


Expert Skills

Category

ResourcesDiscussionNon-Experts

Customer Relationship Management

ProblemReport

Competitor

Employee

ContactPerson

Supplier

Product

Customer/Intermediary


Improvement and Problem Handling

ProblemReport

Employee

OrganizationalUnit

Product &Service

Practice

Customer Supplier Contact

SourceStakeholder

Process

Proof


(3) Mind Mapping


1. Skills Directory

2. Knowledge Management - Map

Skills Directory


KM System - Map


(4) Hierarchy Notes


1. Resources – Microsoft OneNotes

(5) Content Management System


1. Mobile Business

2. KM in KM Development

CM – Mobile Business

www.mobileskynet.com

CM – KM in KM Development

www.mobileskynet.com