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.

Setting Objectives<br />

Connecting the Dots<br />

Building the Found<strong>at</strong>ion<br />

Growing a <strong>Knowledge</strong> Network<br />

Becoming a Change Agent<br />

After completion of the planning stage of a KM str<strong>at</strong>egy or initi<strong>at</strong>ive, <strong>at</strong>tention should be<br />

focused on preparing the Utility and the project team or individuals <strong>for</strong> implement<strong>at</strong>ion. A plan<br />

cannot succeed just because someone orders it to be done. Careful consider<strong>at</strong>ion needs to be<br />

given to the current st<strong>at</strong>e of the Utility, its culture, workload, competencies and outside demands<br />

on its time. Also, it is useful to get some key workers involved so th<strong>at</strong> the purpose, n<strong>at</strong>ure and<br />

value of the project is made visible in a way th<strong>at</strong> gives the Utility time to digest and understand<br />

its goals and impacts.<br />

Setting Objectives<br />

The project requirements must be made explicit <strong>for</strong> all personnel involved in the project.<br />

Project objectives are often defined in terms of being SMART: Specific, Measurable, Attainable,<br />

Realistic (and Relevant) and Time-based. While this approach works well <strong>for</strong> complic<strong>at</strong>ed<br />

systems such as building in<strong>for</strong>m<strong>at</strong>ion systems or developing KM Desk Guides, parts of SMART<br />

may have to be dropped or modified in a KM project where the desired outcome is an emergent<br />

phenomenon of a complex system (a community or team). See the MQI paper on systems and<br />

complexity.<br />

Closely linked to setting objectives are setting targets and developing milestones. Set<br />

targets which cre<strong>at</strong>e direction and opportunities <strong>for</strong> high per<strong>for</strong>mance. These targets are<br />

sometimes referred to as “stretch” goals. They are challenging but not so challenging th<strong>at</strong> they<br />

are viewed as non-achievable. Develop milestones to evalu<strong>at</strong>e per<strong>for</strong>mance by comparing<br />

planned results <strong>at</strong> a point in time to actual results. Milestones are usually significant events in<br />

the project, such as completion of on-time deliverables or successful completion of phases of<br />

the project. Milestone devi<strong>at</strong>ions should be monitored and carefully managed throughout the life<br />

of the project. There is little point of being in<strong>for</strong>med of a major cost overrun <strong>at</strong> the end of a<br />

project, or of ignoring a counter intuitive result th<strong>at</strong> cre<strong>at</strong>es unintended and harmful<br />

consequences to the project outcome. While knowledge projects are usually aimed <strong>at</strong> long-term<br />

results and may be difficult to evalu<strong>at</strong>e in the short-term, activity toward the anticip<strong>at</strong>ed outcome<br />

and emergent indic<strong>at</strong>ors can be reviewed and assessed.<br />

Connecting the Dots<br />

Any <strong>for</strong>ward movement requires both a starting point and a direction in which to move. A<br />

good way to understand the knowledge currently available in the Utility is through conducting a<br />

knowledge audit and cre<strong>at</strong>ing a knowledge map. A knowledge audit moves beyond identifying<br />

and mapping knowledge sources to evalu<strong>at</strong>ing the st<strong>at</strong>e of an organiz<strong>at</strong>ion’s technology, how<br />

well the organiz<strong>at</strong>ion’s processes support knowledge sharing, and the work styles and culture of<br />

the people within the organiz<strong>at</strong>ion. See Case Example #1 and Case Example #2. Wh<strong>at</strong> is<br />

learned from the knowledge audit can now be compared to wh<strong>at</strong> knowledge is needed in order<br />

to identify knowledge gaps. These gaps could be rel<strong>at</strong>ed to current knowledge, or potential<br />

gaps as identified employees move toward retirement or as demands of the environment<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!