19.11.2014 Views

Organizational Development for Knowledge Management at Water ...

Organizational Development for Knowledge Management at Water ...

Organizational Development for Knowledge Management at Water ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Affinity Diagram 2<br />

A process <strong>for</strong> c<strong>at</strong>egorizing Utility knowledge needs in a diagram <strong>for</strong>m<strong>at</strong> to exhibit differences<br />

and rel<strong>at</strong>ionships.<br />

Supports: group learning, knowledge audit<br />

LEVEL OF EFFORT<br />

SIZE OF UTILITY<br />

SCOPE OF WORK<br />

LOW<br />

SCALABLE<br />

NARROW<br />

The Affinity Diagram can be used to take specific knowledge needs, group them, and cre<strong>at</strong>e<br />

represent<strong>at</strong>ive c<strong>at</strong>egories called content centers. The Affinity Diagram is a simple tool th<strong>at</strong><br />

enables the user to enter the knowledge requirements of some process, issue, or situ<strong>at</strong>ion;<br />

g<strong>at</strong>her similar requirements together into small groups; evalu<strong>at</strong>e those groups; and decide on a<br />

c<strong>at</strong>egory name <strong>for</strong> each grouping. The groups you will develop will serve as content centers <strong>for</strong><br />

the development of communities of practice as part of the knowledge management system.<br />

Constructing an Affinity Diagram<br />

The most effective group to do an Affinity Diagram is one th<strong>at</strong> has the necessary knowledge<br />

to uncover the various dimensions of the issue, process, etc. This works best when the group or<br />

team is accustomed to working together and there is represent<strong>at</strong>ion from all departments<br />

involved in this area of knowledge. This enables team members to communic<strong>at</strong>e clearly<br />

because of their rel<strong>at</strong>ionship and common experiences. Personnel should be included th<strong>at</strong><br />

have valuable input and who may not have been involved in the past. Also, keep the team fluid;<br />

bringing in resource people as needed. There should be a maximum of five to six members on<br />

the team. Since the team will explore the c<strong>at</strong>egoriz<strong>at</strong>ion of drinking w<strong>at</strong>er utility knowledge<br />

needs, it should also ensure th<strong>at</strong> the team members are personally aware of user knowledge<br />

requirements.<br />

1. Phrase the issue <strong>for</strong> discussion:<br />

The issue seems to work best when vaguely st<strong>at</strong>ed. For example, ―Wh<strong>at</strong> are the main<br />

communities of practice needed to help the Utility become more valuable and effective?‖ To<br />

review, communities of practice are groups of people whose responsibilities require access to<br />

similar in<strong>for</strong>m<strong>at</strong>ion. Once everyone agrees on the question, place it <strong>at</strong> the top of the diagram.<br />

2. List and Display all your knowledge requirements.<br />

To begin this exercise, refer to your knowledge requirements. All of these should be transcribed<br />

so th<strong>at</strong> the team can see them clearly. Enter all the knowledge requirements onto the small<br />

note cards, one idea per card. Whenever possible the knowledge requirement should have a<br />

noun and a verb (i.e., complete st<strong>at</strong>us report). This tends to make the st<strong>at</strong>ements clearer to<br />

understand.<br />

2 Adapted from the Department of the Navy <strong>Knowledge</strong> Centric Organiz<strong>at</strong>ion Toolkit.<br />

C-6<br />

©2011 W<strong>at</strong>er Research Found<strong>at</strong>ion. ALL RIGHTS RESERVED.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!