Professional Documents
Culture Documents
Digital Assignment 1 Case Study 1 KM: Process of Documenting and Sharing Knowledge in Organizations
Digital Assignment 1 Case Study 1 KM: Process of Documenting and Sharing Knowledge in Organizations
Digital Assignment 1 Case Study 1 KM: Process of Documenting and Sharing Knowledge in Organizations
Case study 1
KM: Process of documenting and sharing knowledge in organizations
As part of the implementation of knowledge management (KM) strategy, a
global leadership programme was introduced in Marshal Limited, a European
based company operating in different locations. The programme targets high-
performing, high-potential colleagues with people management responsibility.
It is a three-day off-site event, titled “Managing Essentials,” it was launched in
the spring of 2002. An external provider was used to deliver the programme
across the globe with a core team of dynamic and experienced facilitators. This
strategic decision has another challenge so that there is no misinterpretation of
message across employees. The audience for the programme is diverse in years
within the organisation and in the industry, time in a management role,
geography, and first language. The Learning and Development (L&D) network of
colleagues managing the programme at the local level across the globe is also
diverse. Technology has played a key role in communicating across geographies
with both the delegate and the L&D communities by way of the telephone,
internet, email, various global software platforms, and even camera. The
ultimate KM strategy is to improve organisational capability and capacity
through knowledge sharing. In order to sustain the learning among employees,
three cycle stage of the actions are taken for the programme.
Sustaining the Learning
Pre Event
High-performing, high-potential colleagues were the target audience for
“Managing Essentials”. To ensure appropriate employees with this skill set,
employees could not self-register for the programme but had to be nominated
by a senior colleague in their business. To combat cultural issues that historically
reinforced silos within the business and across geographies, “Managing
Essentials” is delivered at a pan-European level as opposed to local country level.
Nominations are managed by the Programme Manager through the database to
ensure a 50/50 split of participants from the UK and continental Europe. The
deliberate mix of delegates on each event, sharing and cascading knowledge and
breaking down business segment and geographical boundaries, has been
recognised by delegates as a core strength of the programme.
Post Event
The Marsh internal Learning and Development team developed a sustainability
timetable post programme using a variety of KM tools. A summary of activity is
noted in Table 1.
Months three, six, and 12 of the post-programme plan were proposed in the first
quarter 2003, but have not yet been fully implemented. Europe has consistently
implemented up to the three-week stage in this timeline and has sporadically
implemented the six-week and onwards activities. Each of the KM tools and
practices used in the above timeline has its pros and cons. The objective of using
this range of tools and methods is to provide an overall synergy to all the
learners involved, appreciating different learning styles. The feedback the team
has had is that the facilitated conference call is useful for reminding delegates
of their learning and bringing the “community” back together again. The
conference call does not, however, lend itself to support those colleagues who
speak English as a second language and the transcript of the call, while a valuable
record of verbatim comments and stories, is detailed and time consuming to
analyse at a later date.
As the networking opportunity of the event holds such great wealth for the
participants and lends itself to the transfer of knowledge both to the network
after the event and to their colleagues back in the office, a digital photo is now
taken on site on the last day of the programme and circulated to the delegates
approximately two weeks afterwards via e-mail. For those people who learn
more effectively in a group and through visual stimulus (as opposed to audio or
kinesthetic), the photo provides a reminder of the experience and the learning.
The A5 laminate needs no translation, it’s colourful, and delegates do not need
to actually “do” anything with it other than hang it somewhere prominent on
their desk as a reminder. When walking around the offices, these laminates are
becoming more and more visible with the numbers of colleagues attending the
programme. This is a simple way to cascade the message as yet other colleagues
ask questions about the laminate on the desk and the explanation cascades the
learning.
-
KNOWLEDGE MANAGEMENT Dr. Sumathi G N Page 4
Case study 2
Building knowledge management system
A large commercial bank made a decision to build a knowledge management
auditing system to advise the bank on compliance with the federal bank
examiners who audit the bank on a quarterly basis. The office of the Comptroller
of the Currency (OCC), a bureau of the U.S. Treasury, is the regulator of the
national banking system. To oversee this systems of 4,500 banks, OCC
administers 125 offices across the country are staffed by 2,500 bank examiners.
These examiners range from 25 years veterans to novice assistants.
To create a bank knowledge management auditor, BANKOR, the bank’s
president formed a knowledge management team consisting of the bank’s
audit, a representative from each major department and a member of the board
of directors to launch the project. The senior vice president of the loan
department chaired through extensive interviews with six federal examiners
over a 15-month period. Fortunately, one knowledge developer was an
examiner, and the other was an IT expert in knowledge management system
design.
Interviewing the examiners: Given the serious nature of bank auditing and
solvency, six seasoned examiners were chosen for the job. With each examiner
coming from different states where the bank does business, this strategy helped
BANKOR address everyone’s concerns and made it easier to gain universal
acceptance. Once selected, the knowledge developers scheduled a weeklong
session with each examiner. They held the first interview not really knowing
what to expect. They had selected several case studies for the examiners to
analyze the cases and reach conclusions. So, in preparation for the succeeding
interviews the developers selected more complex cases that would require the
examiners to wrestle with their own decision-making process and apply true
expertise.
Following the first interview, it took 3 months to assemble and collate the
captured notes. The developers reduced the notes for an individual examiner’s
cases to a general conclusion about how that examiner worked. Finally, the
developers combined the six methods into one set that described the
examiner’s consensus.
Tapping the session was tremendous help. It saved having to write everything
down and allowed the developers to concentrate on what was said, and they
were better able to probe their thought process for inconsistencies and missing
pieces. The transcripts also allowed them to see their responsive verbatim.
A detailed implementation plan was devised based on the above analysis, which
was then agreed to and approved by the top management of HS. The KM
program was officially launched in April 2002.
As seen, a good start does not guarantee continuity and success. First, two
crucial reasons were identified as to why HS was unable to bridge the knowledge
gap. They were (1) the top management was too ambitious or unrealistic to
grasp and incorporate the “best” knowledge in industry into the company and
(2) their insufficient role support in encouraging the desired behavior.
Similar to many other KM misconceptions, top management wrongly aimed at
incorporating other enterprises’ best practices (e.g., product design of the fad)
or success stories (e.g., cost cutting and streamlining operational processes) into
its repositories without considering the relevance, suitability, and congruence
to its capabilities. Therefore, this “chasing-for-the-best” strategy soon became
problematic and departed from its KM goals.
References
Awad, E. M., & Ghaziri, H. (2004). Knowledge management. Prentice Hall.
Jennex, M. E. (Ed.). (2005). Case studies in knowledge management. IGI Global.