The document discusses knowledge management. Section I defines knowledge management as treating knowledge as an explicit business concern and making a direct connection between an organization's intellectual assets and positive business results. Section II describes how knowledge management was implemented at one organization using a wiki to create a collaborative space. Section III discusses how to implement knowledge management by defining a strategy, creating a plan, and addressing possible issues like resistance to change.

1. Knowledge
Management
October 2007 Štefan Urbánek

2. Contents
I. What is Knowledge Management
II.How we did it
III.How to get it done
Štefan Urbánek, 2007 2

3. I. What is
Knowledge
What problems it solves, where it fits.

4. It Is a Business
Activity
treating the knowledge component of business activities as an explicit
concern of business reflected in strategy, policy, and practice at all levels of
the organization; and, making a direct connection between an organization's
intellectual assets (explicit and tacit) and positive business results.
Barclay and Murray
Knowledge management is a collaborative and integrated approach to the
creation, capture, organization, access and use of an enterprise’s intellectual
assets.
Grey
Štefan Urbánek, 2007 4

5. It Is a Business
Activity
Explicit (recorded)
tacit (personal know-how)
intellectual assets
intellectual assets
!
time
Oragnisational memory Positive business
results
Štefan Urbánek, 2007 5

6. What does it
mean?
Few examples

7. Lost Knowledge
Capital
people join and leave teams
team members share knowledge
lost member is lost knowledge
?
?
Štefan Urbánek, 2007 7

8. Learning
Organisation
people join and leave learning teams
team members store and share
when one leaves a team, team retains its
knowledge
Štefan Urbánek, 2007 8

9. Time
meeting, analysis knowledge sharing knowledge application
1+1=? 2
1+1=? 2
No KM
time
With KM
No KM
With KM free time
Štefan Urbánek, 2007 9

10. Summary I.
Helps people do their jobs
and save time through better decision making and problem solving
Promotes peer-to-peer mentoring
develops a common language
Diffuses best practises
cross-fertilizes ideas and increases opportunities for innovation
Builds organisational memory
Štefan Urbánek, 2007 10

11. Paradigm Shift
knowledge is power
sharing knowledge is more powerful
Štefan Urbánek, 2007 11

12. II. How we did it
How it was born, how it grew,
how is it now and what is Wiki

13. From the Beginning
Started as DWH team knowledge storage
Infected neighboring teams
Now official knowledge management for IT
Increases collaboration, saves time, reveals misinformation
Seeded in marketing department
Plan to make whole organization participate
and migrate existing prehistoric knowledge management systems
Štefan Urbánek, 2007 13

14. Instant Solution: Wiki
Collaborative space
anyone can add, edit, discuss, correct
Information put into context
connected with related information, knowledge, people or
documents
Place for knowledge refinement
incremental idea creation Wiki
social error correction
Štefan Urbánek, 2007 14

15. Collaborative Space
participants
pages
links
back links
discussions
Štefan Urbánek, 2007 15

16. Demo
(some screen-shots from Wiki here...)
Štefan Urbánek, 2007 16

17. Summary II.
The Tool is Wiki
many implementations exist
Information is put into context
linked with people and other knowledge
Collaboration is the way
sharing, evolution, refinement, correction
Štefan Urbánek, 2007 17

18. Discussion
Customer Services Strategy
Technical
Commercial
Forums Wiki
Human Resources IT
Glossary
Processes
Štefan Urbánek, 2007 18

19. III. How to get it
done
What to do to have knowledge management
and what to do to make it work

20. Before we start
Nature of knowledge:
Štefan Urbánek, 2007 20

21. Start
Define knowledge management strategy
Perform knowledge audit
Create plan
Define and assign roles
Adjust processes and prepare cultural change
Pick a tool
Štefan Urbánek, 2007 21

22. Steps and roles
time
Research and plan Create and seed Grow Use and benefit
sponsor - pushes the project, takes care of
resources, removes obstacles
evangelist - maintains knowledge, motivates
others, seeds core knowledge, corrects, links
participants - feed, discuss, refine, use
Štefan Urbánek, 2007 22

23. Possible Issues
Resistance to change
“not invented here”, “we have been doing it like this for ages, it
works”
No Time and no Desire
“I have millions of more important things to do”
No Trust
“people are trolls by nature”, “it is not complete”
Low or no Sponsorship
Štefan Urbánek, 2007 23

24. Recommendations
Do not design, let it grow
it is an evolutionary process that must be embedded into the
organizational culture
knowledge management is alive, sometimes unpredictable
Trust people, they will trust you
motivate
do not add many restrictions, they can discourage people
social moderation will do emerge
Štefan Urbánek, 2007 24

25. Summary III.
Almost always requires a cultural change
if not a complete transformation or tweaking of existing culture(s)
Put people and culture first
systems and tools are second
Štefan Urbánek, 2007 25

26. Discussion III.
Chaotic
Ad-hoc
Managed
Agile
Štefan Urbánek, 2007 26

27. Thank You
stefan@agentfarms.net
Creative Commons Attribution-Noncommercial-Share Alike
Štefan Urbánek, 2007 27

28. Credits

29. Images
Brain image: Wikimedia Commons, Human Brain
Beans and peas image: Project Gutenberg, www.guttenberg.org, Outlines of Lessons in Botany,
Part I; From Seed to Leaf, by Jane H. Newell, Illustrated by H. P. Symmes
Seeds image: Wikimedia Commons, Seeds / Star Anise
Štefan Urbánek, 2007 29