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.

68 | <strong>Organiz<strong>at</strong>ional</strong> <strong>Development</strong> <strong>for</strong> <strong>Knowledge</strong> <strong>Management</strong> <strong>at</strong> W<strong>at</strong>er Utilities<br />

Sharing<br />

<strong>Knowledge</strong> sharing is not merely a transfer of in<strong>for</strong>m<strong>at</strong>ion; it is bringing people together to<br />

interact and exchange different experiences and share understanding. Any time two or more utility<br />

employees engage dialogue this is occurring. Through dialogue an individual’s context can be<br />

conveyed, allowing each participant to gain the explicit knowledge shared by the other and to cre<strong>at</strong>e<br />

new knowledge through a mutual learning process. For example, mentoring—a rel<strong>at</strong>ionship<br />

between an experienced utility and a younger professional—can facilit<strong>at</strong>e the sharing of shallow<br />

and deep knowledge.<br />

<strong>Knowledge</strong> is one of those rare things you can give away and still have. In the past, knowledge<br />

was used in organiz<strong>at</strong>ions to control others and maintain power. Today, knowledge hoarders<br />

have limited value to their organiz<strong>at</strong>ions and often cre<strong>at</strong>e cultural barriers to learning. Wherever<br />

possible, it is best to develop and share as much knowledge as possible so th<strong>at</strong> others can act independently<br />

and develop their own internally and situ<strong>at</strong>ion-driven behavior. Through reciprocal<br />

sharing, innov<strong>at</strong>ion springs into being.<br />

While a necessary first step, simply having access to knowledge does not constitute sharing.<br />

For example, many organiz<strong>at</strong>ions make in<strong>for</strong>m<strong>at</strong>ion available through technology systems,<br />

but fail to incorpor<strong>at</strong>e knowledge maps or guides <strong>for</strong> users so they can find wh<strong>at</strong> they need and put<br />

it to use. Yet, as The World Bank discovered, knowledge sharing has become a str<strong>at</strong>egic necessity<br />

to survival. A growing number of organiz<strong>at</strong>ions are recognizing the need <strong>for</strong> collabor<strong>at</strong>ion across<br />

organiz<strong>at</strong>ional boundaries.<br />

Ideally, knowledge sharing emerges as part of the culture. Some examples th<strong>at</strong> facilit<strong>at</strong>e<br />

knowledge sharing are: the support and use of teams and communities as part of the everyday work<br />

process, the example of openness and integrity set by senior leadership; and an awards program<br />

th<strong>at</strong> rewards knowledge sharing.<br />

Evalu<strong>at</strong>ing and Measuring<br />

While there is a need to measure expenses, schedule, scope, and quality, there are also subjective<br />

measures <strong>for</strong> things like your team’s rel<strong>at</strong>ionship with stakeholders, knowledge sharing,<br />

innov<strong>at</strong>ive ideas emerging, etc. Any measure is appropri<strong>at</strong>e if it helps ensure the project is on track<br />

with its str<strong>at</strong>egic intent. When picking metrics, ensure th<strong>at</strong> you are measuring <strong>for</strong> the future.<br />

Because wh<strong>at</strong> gets measured is wh<strong>at</strong> gets <strong>at</strong>tention, it is important to think <strong>for</strong>ward to the desired<br />

end st<strong>at</strong>e and identify per<strong>for</strong>mance measures th<strong>at</strong> move beyond specific goals to serving as part of<br />

the implement<strong>at</strong>ion change str<strong>at</strong>egy. The knowledge centric organiz<strong>at</strong>ion model designed by the<br />

Department of the Navy uses three types of metrics to assess different levels of KM impact, namely<br />

outcome (enterprise or overall value), output (project or task), and system (technology tool).<br />

The perspectives of the customer, department, organiz<strong>at</strong>ion, and individual are critical to<br />

the project’s success and, as appropri<strong>at</strong>e, need to be incorpor<strong>at</strong>ed into its evolution. The implic<strong>at</strong>ion<br />

<strong>for</strong> KM metrics is th<strong>at</strong> it is important to identify who is likely to use the per<strong>for</strong>mance measurement<br />

in<strong>for</strong>m<strong>at</strong>ion. Potential users include str<strong>at</strong>egic decision makers, special project decision makers,<br />

funding and approval stakeholders, government agencies involved in approval or regul<strong>at</strong>ion, or<br />

customers. Measures should be in terms th<strong>at</strong> are familiar to the stakeholder, there may be several<br />

different metrics th<strong>at</strong> need to be captured <strong>for</strong> an initi<strong>at</strong>ive. There is no one “right” set of measures<br />

<strong>for</strong> KM, and most initi<strong>at</strong>ives will require a combin<strong>at</strong>ion of measurement types and classes to reflect<br />

the overall mission and str<strong>at</strong>egy of the utility and effectively communic<strong>at</strong>e with key individuals.<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!