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.

<strong>Knowledge</strong><br />

<strong>Knowledge</strong> <strong>Management</strong><br />

The Need <strong>for</strong> KM in the Drinking W<strong>at</strong>er Utilities<br />

Toolkit Resources<br />

Rel<strong>at</strong>ed W<strong>at</strong>erRF Research<br />

<strong>Knowledge</strong><br />

The decisions th<strong>at</strong> are made every day by every single person in your Utility determine the<br />

per<strong>for</strong>mance of the Utility th<strong>at</strong> day. <strong>Knowledge</strong> is about making good decisions and taking<br />

the best actions in a given situ<strong>at</strong>ion. This is why knowledge is defined as the capability<br />

(potential or actual) to take effective action. When you have good knowledge your decisions and<br />

actions will result in wh<strong>at</strong> you expect or plan to happen. Managing knowledge in an organiz<strong>at</strong>ion<br />

means ensuring decision-makers <strong>at</strong> all levels have the ability and the in<strong>for</strong>m<strong>at</strong>ion they need to<br />

make the best decisions and take the most effective actions.<br />

<strong>Knowledge</strong> can be thought about in many different ways. One way is to consider it in terms<br />

of explicit, implicit and tacit. Explicit knowledge is knowledge th<strong>at</strong> can be called up from memory<br />

and described in words or visuals such th<strong>at</strong> another person can comprehend wh<strong>at</strong> is expressed.<br />

Emotions can also be expressed as explicit knowledge in terms of changes in body st<strong>at</strong>e; <strong>for</strong><br />

example, when someone blushes. Implicit knowledge is a bit more complic<strong>at</strong>ed. It is knowledge<br />

stored in memory which you may not recall but can be triggered, usually by an external event.<br />

Examples of triggers are questions, dialogue and reflective thought. In other words, implicit<br />

knowledge is something you do not know you have but is self-discoverable. Tacit knowledge<br />

describes th<strong>at</strong> which cannot be recalled and put into words. It is a knowing or doing th<strong>at</strong> is<br />

known or acted upon but which cannot be articul<strong>at</strong>ed or explained. Examples range from<br />

intuitive feelings to bicycle riding.<br />

There are other ways to think about knowledge th<strong>at</strong> can be useful to individuals and<br />

organiz<strong>at</strong>ions. For example, thinking about knowledge in terms of surface knowledge, shallow<br />

knowledge and deep knowledge can help a manager ask relevant questions about specific<br />

levels of knowledge. It also helps us to recognize the scope and depth of knowledge available<br />

to maximize problem solving, decision-making and action in simple, complic<strong>at</strong>ed and complex<br />

situ<strong>at</strong>ions. Further, these three levels of knowledge help tailor learning and knowledge to<br />

improve knowledge sharing and retention. Another way to think about knowledge is in terms of<br />

types of knowledge grouped by similarities and differences, specifically, in terms of wh<strong>at</strong><br />

knowledge is needed to do a particular type of work or take a particular action. This is useful<br />

when considering the knowledge needs <strong>for</strong> specific jobs, and identifying knowledge gaps in a<br />

Utility. See the MQI paper on The Depth of KNOWLEDGE.<br />

Another way to think about knowledge is in terms of technical, social and structural.<br />

Technical knowledge applies to functional capabilities, and is typically demonstr<strong>at</strong>ed as a skill.<br />

Social knowledge is embedded in the exchanges individuals have among themselves, and is<br />

built on rel<strong>at</strong>ionships and culture. Structural knowledge is wh<strong>at</strong> is embedded in the Utility’s<br />

systems, processes, policies and procedures, and is usually rules-based. In Project Study<br />

#23, the Louisville W<strong>at</strong>er Company surveyed retiring managers to discover the technical, social,<br />

and structural knowledge needed to do their jobs.<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!