HKSM

Knowledge management is a technique for systematically capturing, sharing, and reusing project knowledge to improve decisions and outcomes. It covers both explicit assets and tacit know-how by creating channels, repositories, and behaviors that let knowledge flow among stakeholders.

Key Points

• Focuses on enabling the flow of both explicit and tacit knowledge across the team and stakeholders.
• Combines people practices (sharing, mentoring) with information practices (repositories, tagging).
• Most valuable when tied to real decisions, risks, and upcoming work rather than generic documentation.
• Continuous activity integrated into delivery, not a one-time lesson-capture at project close.
• Relies on a safe culture that encourages asking, sharing, and learning from mistakes.
• Measures success by reuse, cycle time improvements, and reduced repeat defects, not just page counts.

Purpose of Analysis

To identify what knowledge is critical, where it resides, how it moves, and how to make it available when decisions and actions require it.

• Map critical decisions and the knowledge needed to make them well.
• Reveal gaps, bottlenecks, and risks in current knowledge flows.
• Prioritize capture and sharing where the impact on outcomes is highest.
• Design lightweight practices that fit team rhythms and toolsets.

Method Steps

1. Clarify objectives: define outcomes to improve (quality, speed, risk reduction) and key decisions ahead.
2. Identify knowledge domains: what explicit artifacts and tacit know-how are critical and why.
3. Map sources and consumers: who holds, needs, and brokers knowledge; include external experts.
4. Assess current state: review repositories, lessons learned, communication channels, and pain points.
5. Plan capture: choose tactics for tacit (peer assists, communities, interviews, shadowing) and explicit (templates, wikis, playbooks).
6. Enable sharing: set up findable spaces, tags, office hours, brown-bags, and feedback loops.
7. Integrate into workflow: embed checklists, definitions of done, and knowledge prompts into ceremonies and tools.
8. Secure and govern: classify sensitivity, set access rules, and assign maintenance ownership.
9. Measure and adapt: track reuse, time-to-find, and defect/issue recurrence; refine practices.

Inputs Needed

• Project objectives, roadmap, and key upcoming decisions.
• Stakeholder and team roster with roles and expertise areas.
• Existing repositories, templates, and documented procedures.
• Lessons learned and retrospectives from current and prior efforts.
• Performance data, issue logs, and defect trends.
• Risk register and assumptions that depend on specialized knowledge.
• Communication and team working agreements, including tool access.
• Organizational policies for information security and data retention.

Outputs Produced

• Knowledge map showing critical domains, sources, consumers, and flows.
• Knowledge register with prioritized gaps, actions, and owners.
• Curated repositories and playbooks with findable, current content.
• Updated lessons learned and actionable checklists embedded in workflow.
• Onboarding guides and role-based how-to materials.
• Decision logs including rationale and references for future reuse.
• Metrics on reuse, access frequency, and time-to-find information.
• Access controls and governance assignments for sensitive content.

Interpretation Tips

• Distinguish tacit (experience-based, context-rich) from explicit (documented) and match capture methods accordingly.
• Start where decisions or risks are most affected by knowledge gaps to show early value.
• Make knowledge easy to discover: clear titles, tags, summaries, and cross-links.
• Favor concise, action-oriented artifacts over long narratives; keep content fresh.
• Track behavior change (reuse, fewer repeats) to validate that sharing improves outcomes.
• Balance openness with confidentiality; classify and control access as needed.

Example

A project faces repeated rework during handoffs. The manager maps the knowledge needed at each handoff, finds gaps in tacit know-how, and sets up brief peer assists plus a visual handoff checklist stored in a shared wiki. Reuse of the checklist rises, defects drop, and cycle time shortens.

Pitfalls

• Equating knowledge management with dumping files into a repository without curation.
• Over-documenting instead of embedding practical guidance into day-to-day work.
• Ignoring tacit knowledge and relying only on templates and reports.
• Letting content become stale due to unclear ownership and review cycles.
• Investing in tools without fostering a sharing culture and incentives.
• Failing to protect sensitive information, causing trust and compliance issues.

PMP Example Question

A key subject matter expert will leave the project in two weeks. To best manage knowledge risk, what should the project manager do first?

1. Ask the expert to upload all documents to the repository.
2. Schedule a series of structured interviews and peer assists to capture tacit know-how tied to critical decisions.
3. Request the HR department to extend the expert's contract.
4. Send a survey to the team asking what they want to know.

Correct Answer: B — Schedule a series of structured interviews and peer assists to capture tacit know-how tied to critical decisions.

Explanation: The immediate priority is capturing critical tacit knowledge in a reusable form focused on real upcoming decisions. Documents alone may miss context and rationale.