Knowledge Management Overview
• Build capabilities to identify, acquire and
share knowledge in a structured and
• Develop a culture of learning
What the project team plans to do
• Awareness of -
- Knowledge already in Place
- Knowledge still missing
- Knowledge Acquiring and
• Repository of “Know how” and “Know
• KS Calanders
• Thought leadership group which drives
What the team delivers into the business
• Increased cross-pollination between
• Improve employee’s engagement with
wing to wing understanding.
• Improve quality and productivity.
• Continuity in times of attrition.
What benefits the stakeholders derive
from the outputs
Knowledge Capture Knowledge Distribution
I. Acquisition II. Creation III. Repository IV. Sharing V. Use VI. Evaluation
Tacit to Explicit
into tangible K-
measure ROI -
Influencing Variables Quality Of Variables
A) Task Classifying Organisational Tasks : Ambiguous, Interdependent Etc.
B) Structure Organisational .Structure : By Function , Extn. Teams Etc.
C) Leadership Performance measure, Planning and control etc.
D) Culture Norms, Shared Values, Beliefs
E) People Training, Right Resourcing
F) Reward systems Recognition, Promotion
Tacit Knowledge : Brain dump, Skills Developed with Experience, Information not documented
Explicit Knowledge : Process Documents, Guides, References, MOMs, Update Decks, Project Artifacts etc.
Acquisition Creation Repository Sharing Use Evaluation
Tacit to Tacit
Experience > Socializing>
Learning by Observation
Identify “Know who”
of “Know who”
Hard to Archive
Task, Structure Leadership
Tacit to Explicit
Observation > Hypothesis>
in NLs, Blogs,
Structure, R&R People, R&R
Explicit to Tacit
Observe & do
Key man Coverage
People, Task Leadership
Explicit to Explicit
Structured – Mostly
Unstructured - Hunt
Key man Coverage
Knowledge Management Life Cycle
Initiated Yet to Start Concept
Project Output Activity Example Artifact
Creating a Governance and
Execution Team - Leadership
•Identify what is knowledge – what needs to be
•Identify who is the SME.
•Develop a communication plan and massaging
•Create a Reward and Recognition plan
•Monitor usability and measure benefits
•Regular meeting of FT leads – sharing updates.
•Core team to connect the dots reconcile with
big picture. – Forum Specific only to discuss
knowledge “needs” and where and how to
Project Plan for –
•Creating SME pool
Creating the Repository •Develop Knowledge Infrastructure
•Identify right repository platform – SharePoint,
Share drive, Physical archiving.
•Creating Document hierarchy
•Create a “Know who” SME directory
•“Bringing out” the unstructured
•Create a database within FT of “who knows
•A directory of deliverables and artifacts with
brief description which is user friendly Ex – PSC
Decks, Status Updates, Report Inventories etc.
•Ready to use templates structures for
• Archive the 1-1 communications on mails
which is not normally cascaded.
Knowledge Sharing Events •Create cross team projects.
•Knowledge sharing sessions – Presentation in Town
hall, Quizzes, Learning as fun.
•Have write-up competitions -
•Knowledge sharing sessions – Participation as
per knowledge level.
•Archiving session presentations in library
•Cross team project or rotation to capture tacit
KS calendar to be
and make learning
Developing SME as a Career
•Develop and groom individuals as SMEs
•Recognize SMEs as Career
•SMEs in domains, skills need to be pooled and
put on short term assignments with multiple
teams – Consulting model. They evolve as
carriers of knowledge between teams.