6. 6
Management Levels
Knowledge Assets
Knowledge Sharing
Knowledge
Work
Knowledge
Transfer
Knowledge Infrastructure
Stock
Flow
Business
National Defence,
National Security,
Public Safety
Defence
R&D
Canada
Markets
Resources Government
Agenda
9. 9
Knowledge Infrastructure
Processes
work routines
lessons learned,
best practices,
People
learning, motivation,
rewards, incentives,
staffing, skills
Governance roles, responsibilities,
authorities, resources
Content,
Services
data, risk analysis,
reports, monitoring,
operations, policies
Tools
systems to
capture, store,
share, and
process content
Levels
10. 10
Knowledge Assets
• Capture: Represent explicit or tacit
knowledge on reproducible media
• Inventory: Find, list, and describe
knowledge; map to business needs,
value and prioritize
• Needs: What needs to be known to
accomplish DRDC goals; identify
core knowledge
• Gaps: Difference between what is
known and what needs to be known
• Preserve: organize, store, search &
retrieval, maintain and migrate
throughout life-cycle
Levels
11. 11
Knowledge Sharing
• Exchange: Develop & implement internal systems to
enable people to find and retrieve knowledge.
• Integrate: Combine diverse knowledge from many
sources to create a holistic view of complex issues.
• Transfer: Disseminate knowledge from DRDC to
enable use by the Forces, partners, practitioners,
and Canadians.
• Monitor: Acquire knowledge
from the environment to
identify events and
developments of interest to
the CSS or public safety.
Levels
12. 12
Knowledge Work
• Input-Related: apply the mandate, monitor the
environmental, analyze external content, operational
needs analysis, set priorities, establish projects
• Transformation: manage programs, provide
corporate services, generate knowledge, develop
products & services, mobilize knowledge, learn from
experience
• Output-Related: reports, integrated knowledge,
open innovation, trusted advice, risk mitigation,
organizational adaptation
Levels
13. 13
Knowledge Transfer
• Communications: one-way dissemination of
approved messages and positions.
• Transaction: two-way exchanges of knowledge
products & services.
• Parallel: Transferring knowledge products &
services from or to two or more providers or users.
• Sequential: Multiple organizations sequentially
produce and transfer knowledge products &
services.
• Cyclic: Knowledge service “value chains”
continuously create and transfer new knowledge.
• Network: Interactions among large numbers of
participants in a “knowledge ecosystem.”
Levels
16. 16
Engagement
• Autonomy: (agreed task, flexible schedule, select
technique, choose team)
• Mastery: (is a mindset, it takes time and effort, it
is asymptotic)
• Purpose: (meaningful goals, words are important,
policies)
Daniel Pink (2009)
Engagement
17. 17
Engagement Signals
Positive
• Mutual expectations
• Listen to ideas
• Ask for help & advice
• Jointly review progress
• Freely share information
• Work collaboratively
• Delegate decisions
Negative
• Monitor closely
• Don’t include in planning
• Ignore suggestions
• Seldom interact
• Withhold information
• Control tightly
• Approve all decisions
Tosti & Nickols (2010)
Engagement
18. 18
Community of Practice
People who share common expertise, skill, or
profession (position, work, colleagues)
• Government, department
• Sector, branch, division staff
• Scientists, engineers, lawyers
• Policy analysts, regulators
• Finance, purchasing officers
• Information, communication specialists
Communities
19. 19
Communities and
Knowledge Management
• Knowledge exists in the minds of people.
Experience is as important as formal knowledge.
• Knowledge is tacit as well as explicit.
Transferring tacit knowledge is more effective
through human interaction.
• Knowledge is social as well as individual.
Today’s knowledge is the result of centuries of
collective research.
• Knowledge is changing at an accelerating rate.
It takes a community of people to keep up with
new concepts, practices, and technology.
Communities
20. 20
Participants
- Help with their work
- Solve problems
- Find experts
- Receive feedback
- Place to learn
- Latest information
- Enhance reputation
Management
- Connect isolated experts
- Coordinate activities
- Fast problem solving
- Reduce development time
- Quickly answer questions
- Standardize processes
- Develop & retain talent
Community Benefits
Outputs
- - Tangible: documents, reports, manuals,
recommendations, reduced innovation time and cost
- - Intangible: increased skills, sense of trust, diverse
perspectives, cross-pollinate ideas, capacity to
innovate, relationships, spirit of enquiry
Communities
21. 21
Networks
Interconnection among many individuals groups
or organizations with common
interdependencies, interests, or purpose
• Networks are much bigger
than communities (100s
to 1,000,000s of nodes
• Participants don’t know
most other participants,
limiting trust and security
• Large numbers of nodes
leads to complex behavior
and emergence
Communities
22. 22
Social Networks –
SWOT Analysis
• Strengths – rapid development, world-class
solutions, emergent properties, creative synergies,
vibrant collaboration, openness
• Weaknesses – constant change, unknown quality,
less used by mature individuals, need to motivate
participants, cannot be forced
• Opportunities – leverage internal capacity,
provides creative solutions, easy to implement, low
cost, can monitor emerging trends
• Threats – knowledge leaks, free expression poses
risk, is the crowd wise, documents subject to ATIP,
compatibility with mandate
Communities
31. 31
Sustainability
• Leadership – Outputs must be delivered within a leader’s
tenure; preferably, get them institutionalized.
• Governance – Representative, federated decision making
is the only sustainable governance for knowledge work.
• Reorganization – Align a project/activity with the
organizational business model.
• Priorities – Align the project/activity with the organization’s
long-term strategy
• Support – Deliver initial outputs when & as promised; be
prepared to adapt to changing priorities.
• Culture – Develop favorable policies, reward desired
behavior, leverage work, implement helpful systems.
Authority
33. 33
Key
Messages
Management authorizes
the use of knowledge to
enable action.
Management authorizes
the use of knowledge to
enable action.
A knowledge
organization
engages people to
enhance creativity
A knowledge
organization
engages people to
enhance creativity
Community
collaboration
validates individual
knowledge
Community
collaboration
validates individual
knowledge
Community knowledge
must be put into an
organizational context.
Community knowledge
must be put into an
organizational context.
Notas del editor
A knowledge network looks something like a knowledge organization except that the boundary is somewhat vague and the network has a capacity to create its own knowledge.
It should be evident from this slide that everything depends on members putting content into the network in order to make it go.
This is an organizational infrastructure that includes pretty much everything that is needed to run CSS.
This applies to KM as well as anything else that we do.
Simply put, people use tools and process within a governance structure to increase the value of content and services.
It isn’t a matter of focussing on one or more parts of the infrastructure. All parts must be reflected in a task, project, or program if it is to succeed.
A SWOT analysis is strongly recommended before developing and implementing a social network in government agencies.
Describe the four aspects.
The key question is: if a department participates in a social network, how does it “capture value” from commonly held external intellectual property?
The answer, in a few words, is to bring it inside the organization.
The common property has to be stabilized. A report, policy, or regulation cannot change once it is formalized.
Internal value has to be added by ensuring that it works. For example, in policy, all stakeholder concerns must be addressed; in business, an innovation must be producible and marketable.
A key implication is that a department must retain enough internal core capacity to be able to add value to commonly-held IP.
Managers won’t fund what they don’t understand.
Managers won’t abandon what worked (or didn’t) before.
Managers will oppose loss of resources.
Managers want short-term-low-risk deliverables.