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.

The paragraphs th<strong>at</strong> are covered in this section on execution are specifically concerned with the<br />

implement<strong>at</strong>ion of KM str<strong>at</strong>egies and initi<strong>at</strong>ives.<br />

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

Wh<strong>at</strong> we refer to as knowledge capture is actually the capturing of in<strong>for</strong>m<strong>at</strong>ion th<strong>at</strong> can then<br />

be used by decision-makers to cre<strong>at</strong>e knowledge. In<strong>for</strong>m<strong>at</strong>ion can be captured in many ways.<br />

For example, every time utility workers develop white papers, research papers and reports they<br />

are capturing their knowledge in the <strong>for</strong>m of in<strong>for</strong>m<strong>at</strong>ion which others can read and hopefully<br />

understand. A large part of how well this in<strong>for</strong>m<strong>at</strong>ion is understood is based on context and a<br />

common language. These documents are then stored in in<strong>for</strong>m<strong>at</strong>ion systems (with contact<br />

in<strong>for</strong>m<strong>at</strong>ion <strong>for</strong> the origin<strong>at</strong>ors), and connected to similar and complementary in<strong>for</strong>m<strong>at</strong>ion th<strong>at</strong><br />

can help build a deeper understanding of when and how to use this in<strong>for</strong>m<strong>at</strong>ion in future<br />

situ<strong>at</strong>ions. As an example, see the Lehigh County Authority Work<strong>for</strong>ce Plan (page 21) <strong>for</strong> their<br />

approach to knowledge capture.<br />

An approach to capturing lessons learned is after action reviews, real-time communic<strong>at</strong>ion<br />

vehicles th<strong>at</strong> share understanding across the implement<strong>at</strong>ion team while also serving as<br />

lessons learned <strong>for</strong> those who l<strong>at</strong>er read them, and assessment instruments <strong>for</strong> those who l<strong>at</strong>er<br />

analyze them. After action reviews are held immedi<strong>at</strong>ely after an event has occurred while the<br />

details are fresh in the minds of participants. The actual outcome of the event is compared with<br />

the intended outcome to discover wh<strong>at</strong> went right and why, and wh<strong>at</strong> went wrong and why in a<br />

candid, open discussion. There must be sufficient detail and clarity to ensure everyone<br />

understands wh<strong>at</strong> did and did not occur (and why) so th<strong>at</strong> lessons can be understood and<br />

applied to future actions. Many organiz<strong>at</strong>ions also hold pre-event and during-event reviews. The<br />

pre-action review brings an implement<strong>at</strong>ion team together to focus on the direction ahead, how<br />

progress will be assessed, and sharing lessons learned from previous projects or rel<strong>at</strong>ed<br />

events. The during-action review provides the opportunity to assess progress and adjust<br />

actions underway accordingly. See also the peer view process.<br />

The learning history is a structured process <strong>for</strong> g<strong>at</strong>hering in<strong>for</strong>m<strong>at</strong>ion rel<strong>at</strong>ed to a project,<br />

mission or initi<strong>at</strong>ive. It is a retrospective history of significant events in an organiz<strong>at</strong>ion’s recent<br />

past described in the voices of people who took part in those events. Researched through a<br />

series of debriefings or reflective interviews, the learning history uses feedback from employees<br />

<strong>at</strong> all levels to help an organiz<strong>at</strong>ional evalu<strong>at</strong>e its progress and provide in<strong>for</strong>m<strong>at</strong>ion <strong>for</strong> future<br />

decisions. In Project Study #1 teams are used to capture field and employee knowledge in a<br />

written, usable <strong>for</strong>m<strong>at</strong> to cre<strong>at</strong>e a complete training program. In Project Study #8, standard<br />

oper<strong>at</strong>ing procedures are being developed to cre<strong>at</strong>e a more knowledgeable staff. Another<br />

example of knowledge capture is the use of upd<strong>at</strong>ed oper<strong>at</strong>ions and maintenance manuals (see<br />

Project Study #2).<br />

The KM desk guide is a document residing on the desk (or virtually within the system<br />

supporting th<strong>at</strong> desk) th<strong>at</strong> contains the specific in<strong>for</strong>m<strong>at</strong>ion needed to successfully accomplish<br />

the job of the individual who works from th<strong>at</strong> desk. Each desk guide is upd<strong>at</strong>ed annually, as<br />

changes occur, or as an individual is preparing to leave a position to ensure ease of job<br />

transition. The KM desk guide also serves as a resource <strong>for</strong> temporary employees and<br />

development of an expertise loc<strong>at</strong>or. A vari<strong>at</strong>ion of the KM desk guide is the leave a legacy<br />

approach developed by the Department of the Army.<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!