Chapter 9: Knowledge Capture and Creation

Learning Objectives

After completing this chapter, you will be able to:

Identify opportunities for knowledge capture within organizational processes and workflows
Apply various knowledge elicitation techniques to extract expertise from subject matter experts
Design and use templates that facilitate effective knowledge documentation
Establish quality standards and review processes for knowledge assets
Implement just-in-time knowledge capture approaches that minimize disruption to work
Differentiate between various types of knowledge content and select appropriate capture methods
Create a knowledge capture strategy aligned with organizational priorities
Overcome common barriers to knowledge capture through proven techniques and incentive structures
Design and conduct effective expert interviews for tacit knowledge elicitation
Implement event-based and scheduled capture triggers

Introduction

Knowledge capture and creation form the foundation of any knowledge management program. Without effective mechanisms to capture existing knowledge and create new knowledge assets, even the most sophisticated knowledge management systems and strategies will have little value. This chapter explores the methods, techniques, and practices that enable organizations to systematically capture knowledge from experts, processes, and experiences, and to create high-quality knowledge assets that serve organizational needs.

Knowledge capture is not simply about recording information. It involves eliciting expertise, organizing insights, documenting context, and creating knowledge assets that others can understand and apply. Effective knowledge capture requires understanding what knowledge is valuable, when and how to capture it, and how to do so in ways that maintain quality while minimizing burden on contributors.

At the heart of effective knowledge capture lies the SECI model’s Externalization mode - the critical process of converting tacit knowledge (expertise in people’s heads) into explicit knowledge (documented, shareable assets). This chapter focuses primarily on Externalization techniques, while Chapter 10 explores the full spectrum of knowledge conversion modes.

The Knowledge Capture Challenge

Why Knowledge Capture Is Difficult

Organizations face several fundamental challenges in capturing knowledge:

Tacit Nature of Expertise: Much valuable knowledge exists as tacit expertise - patterns, insights, and judgment that experts apply unconsciously without explicit awareness. Experts often don’t know what they know or find it difficult to articulate their expertise.

Time and Resource Constraints: Knowledge capture requires time from busy experts and subject matter specialists. Creating high-quality documentation competes with operational priorities and billable work.

Motivation and Incentives: Without clear benefits or incentives, individuals may not prioritize knowledge sharing. Some may fear that sharing knowledge reduces their value or competitive advantage.

Quality and Usability: Captured knowledge must be accurate, complete, well-organized, and usable by the intended audience. Poor quality knowledge assets create more confusion than value.

Knowledge Decay: Knowledge becomes outdated as processes, technology, and context change. Keeping knowledge current requires ongoing effort and commitment.

Strategic Approach to Knowledge Capture

Effective knowledge capture requires a strategic approach:

Strategic Element	Description	Key Considerations
Prioritization	Focus on high-value knowledge gaps and risks	Critical processes, retiring experts, repeated questions, error-prone areas
Integration	Embed capture in existing workflows and processes	After-action reviews, project closeouts, ticket resolution, onboarding
Standardization	Use consistent formats, templates, and quality criteria	Article templates, style guides, metadata standards, review criteria
Facilitation	Provide support and tools that make capture easier	Knowledge brokers, writing support, capture tools, structured interviews
Recognition	Acknowledge and reward knowledge contribution	Attribution, performance metrics, gamification, leadership recognition
Governance	Establish roles, responsibilities, and quality processes	Content owners, reviewers, approval workflows, retirement policies

Knowledge Capture Methods

Just-in-Time Capture

Capturing knowledge at the point of use or creation minimizes disruption and maximizes relevance:

After-Action Reviews (AARs): Structured reflection immediately following an event, project, or incident to capture lessons learned while details are fresh.

Ticket Resolution Documentation: Capturing solutions and troubleshooting steps when resolving support tickets or service requests.

Problem Resolution Records: Documenting root cause analysis and solutions when solving complex problems.

Exit Interviews and Knowledge Transitions: Systematically capturing knowledge from employees who are leaving or changing roles.

Project Closeout Sessions: Structured knowledge capture at project completion, documenting decisions, lessons, and reusable artifacts.

Peer Assists: Bringing together experts before starting a new initiative to capture and transfer relevant experience.

Planned Knowledge Capture

Proactive, scheduled capture of critical knowledge:

Expert Interviews: Structured or semi-structured interviews with subject matter experts to elicit and document their expertise.

Documentation Sprints: Dedicated time blocks focused on creating or updating knowledge documentation.

Knowledge Audits: Systematic identification of knowledge gaps followed by targeted capture efforts.

Observation and Job Shadowing: Watching experts perform tasks to identify tacit knowledge and undocumented procedures.

Workshops and Group Sessions: Facilitated sessions where teams collaboratively document processes, lessons, or best practices.

Automated and Passive Capture

Leveraging technology to capture knowledge with minimal manual effort:

Activity Monitoring: Capturing patterns from system logs, search queries, and user behavior to identify knowledge needs.

Collaboration Analytics: Mining emails, chat transcripts, and collaboration tools for frequently discussed topics and emerging issues.

Content Recommendation: Using AI to identify experts, related content, and potential knowledge assets based on user activity.

Process Mining: Analyzing workflow and transaction data to document actual processes and identify variations.

Capture Methods Deep Dive

Understanding the specific techniques for knowledge capture enables more effective knowledge elicitation and documentation. Each method has strengths, limitations, and appropriate use cases.

Interview and Debrief Methods

Structured Expert Interviews:

Formal, planned sessions with subject matter experts using prepared questions and elicitation techniques. Best for capturing deep expertise on specific topics.

Advantages:

Focused knowledge elicitation on priority topics
High-quality, detailed information
Opportunity to probe and clarify
Expert’s full attention and engagement

Limitations:

Time-intensive for experts
Requires skilled interviewer
May miss contextual knowledge
Single perspective

Best Used For:

Complex technical expertise
Critical process documentation
Retirement knowledge transfer
Troubleshooting methodologies

Semi-Structured Interviews:

Flexible conversations guided by topic areas rather than rigid scripts. Allows exploration of emergent themes and unexpected insights.

Advantages:

Natural conversation flow
Captures unexpected knowledge
Expert can lead to important topics
More comfortable for interviewee

Limitations:

May miss planned topics
Harder to compare across interviews
Requires experienced interviewer
Can be unfocused

Best Used For:

Exploratory knowledge discovery
Understanding decision-making
Capturing wisdom and judgment
Initial knowledge audits

Post-Event Debriefs:

Immediate capture following significant events like incidents, projects, or changes. Conducted while memories are fresh and team is still assembled.

Advantages:

Captures fresh, detailed memories
High relevance and immediacy
Natural part of event closure
Team-based perspective

Limitations:

May be emotionally charged
Time pressure to complete quickly
Participants want closure
May lack reflection time

Best Used For:

Incident lessons learned
Project retrospectives
Change implementation reviews
Problem resolution documentation

Observation Methods

Direct Observation:

Watching experts perform work to identify tacit knowledge, undocumented steps, and contextual factors that experts may not articulate.

Advantages:

Captures tacit, unconscious knowledge
Identifies actual vs. documented process
Minimal expert time burden
Reveals environmental context

Limitations:

Observer interpretation required
Cannot capture reasoning
May alter expert behavior
Time-intensive for observer

Best Used For:

Physical procedures
Interface interactions
Troubleshooting approaches
Workflow documentation

Job Shadowing:

Extended observation where the observer follows an expert through normal work activities over time.

Advantages:

Full context understanding
Natural workflow observation
Relationship building
Multiple scenario exposure

Limitations:

Very time-intensive
Privacy/confidentiality concerns
May affect expert behavior
Requires access and trust

Best Used For:

Role-based knowledge capture
Customer service expertise
Clinical or field work
Comprehensive role documentation

Screen Recording with Narration:

Experts record themselves performing tasks while explaining their actions and reasoning.

Advantages:

Visual and verbal capture
Reusable training content
Expert controls timing
Shows actual system interaction

Limitations:

Requires comfort with recording
May not capture all reasoning
Technology barrier for some
Post-production needed

Best Used For:

Software procedures
Configuration tasks
Troubleshooting demonstrations
Self-paced training content

After-Action Review (AAR) Method

AARs are structured reflection processes that capture lessons immediately following events. They originated in military operations and are now widely used in healthcare, emergency response, project management, and IT operations.

Standard AAR Structure:

What was supposed to happen? (The plan/expectation)
What actually happened? (Objective facts)
Why was there a difference? (Root causes)
What should we do next time? (Lessons and actions)

AAR Facilitation Best Practices:

Conduct within 24-48 hours while memories are fresh
Include all key participants, not just leaders
Create psychologically safe environment
Focus on learning, not blame
Document lessons and action items
Assign ownership for improvements
Follow up on action items

AAR Documentation Template:

# After-Action Review: [Event Name]
Date: [Date]
Facilitator: [Name]
Participants: [List]

## Event Overview
Brief description of the event, project, or incident reviewed.

## What Was Planned
- Key objectives
- Expected outcomes
- Planned approach

## What Actually Happened
- Timeline of actual events
- Outcomes achieved
- Variances from plan

## Analysis
### What Went Well
- Successes to sustain
- Effective practices
- Positive outcomes

### What Could Be Improved
- Gaps or issues identified
- Ineffective practices
- Unexpected challenges

### Root Causes
- Why did variances occur?
- What contributed to issues?
- What enabled successes?

## Lessons Learned
1. Lesson one with context
2. Lesson two with context
3. Lesson three with context

## Action Items
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
| Action 1 | Name | Date | Open |
| Action 2 | Name | Date | Open |

## Knowledge Assets to Create/Update
- Article titles or topics identified
- Procedures to document
- Training needs identified

## Metadata
- Event Type: [Incident/Project/Change/Other]
- Impact Level: [Critical/High/Medium/Low]
- Team/Department: [Name]
- Related Records: [Links]

Knowledge Elicitation Techniques

Critical Incident Technique:

Ask experts to describe specific situations where their expertise made a difference, then probe for decision-making process, alternatives considered, and reasoning.

Sample Questions:

“Tell me about a time when troubleshooting this system was particularly challenging.”
“What made that situation different from normal cases?”
“What did you consider when choosing your approach?”
“What signals or symptoms did you rely on?”

Think-Aloud Protocol:

Expert verbalizes their thinking while performing a task or solving a problem, exposing internal reasoning and decision processes.

Implementation:

Brief expert on think-aloud technique
Start with practice task
Remind expert to keep talking
Record session for later analysis
Minimize interruptions during performance
Follow up with clarifying questions

Scenario-Based Elicitation:

Present hypothetical or past scenarios and ask expert to explain how they would respond, revealing conditional knowledge and judgment.

Scenario Types:

Normal operations: “How do you handle X situation?”
Exceptions: “What if Y occurs during the process?”
Multiple failures: “If both A and B fail, what’s your approach?”
Conflicting priorities: “When you must choose between P and Q, what factors guide your decision?”

Repertory Grid Technique:

Structured method to elicit how experts differentiate and categorize elements in their domain.

Process:

Identify elements (systems, problems, approaches)
Present triads of elements
Ask: “How are two similar and different from the third?”
Record constructs (dimensions of difference)
Rate all elements on all constructs
Analyze patterns in expert’s mental model

Crowdsourcing Knowledge

Community Contribution Models:

Leverage collective intelligence by enabling many contributors to add and refine knowledge.

Approaches:

Open Contribution: Anyone can create or edit content (wiki model)
Moderated Contribution: Submissions reviewed before publication
Expert Review: Community contributes, experts validate
Peer Review: Contributors review each other’s submissions

Success Factors:

Clear guidelines and templates
Low barrier to entry
Recognition and visibility
Quality feedback mechanisms
Community moderation
Editorial oversight

Q&A Community Capture:

Convert community question-and-answer interactions into structured knowledge articles.

Process:

Monitor Q&A platforms (forums, Slack, Teams)
Identify high-value questions and answers
Synthesize multiple answers if needed
Structure into knowledge article format
Have expert validate
Publish and link to original discussion

Indicators of High-Value Content:

Multiple people asking same question
Complex answers from recognized experts
High engagement (views, votes, comments)
Gap in existing documentation
Frequently referenced in discussions

Idea Management Platforms:

Structured systems for collecting, evaluating, and implementing ideas from across the organization.

Features:

Idea submission with categories
Voting and commenting
Evaluation workflows
Implementation tracking
Recognition systems

Knowledge Capture Applications:

Identify documentation needs
Collect best practices
Discover innovative approaches
Engage broader organization
Build knowledge-sharing culture

Capture Triggers and Timing

Knowing when to capture knowledge is as important as knowing how. Effective trigger mechanisms ensure knowledge is captured at optimal moments while maintaining workflow efficiency.

Event-Based Triggers

Specific events that signal knowledge capture opportunities:

Trigger Event	Knowledge to Capture	Capture Method
Incident Resolution	Solution steps, root cause, troubleshooting path	Ticket documentation, AAR
Problem Closure	Root cause analysis, permanent solution, prevention	Problem record, knowledge article
Project Completion	Decisions, lessons, reusable components, best practices	Project retrospective, documentation sprint
Change Implementation	Implementation approach, issues encountered, rollback procedures	Change review, runbook updates
Repeated Questions	Answer to question, related information, prerequisites	FAQ article, how-to guide
Escalation	Why escalated, required expertise, resolution approach	Escalation analysis, training needs
Employee Transition	Role-specific knowledge, relationships, context, pending items	Exit interview, knowledge transfer sessions
System Upgrade	New features, changed procedures, migration lessons	Release notes, updated procedures
Audit Finding	Gap identified, corrective action, evidence requirements	Process documentation, compliance guide
Customer Complaint	Root cause, solution, prevention, communication approach	Service improvement article

Scheduled Capture Activities

Regular, planned knowledge capture activities:

Daily Triggers:

End-of-shift handoff documentation
Daily standup action items
Support ticket resolution notes
Operational log entries

Weekly Triggers:

Team retrospectives
Documentation sprint sessions
Expert interview appointments
Content review and updates

Monthly Triggers:

Knowledge audit reviews
Trending issue analysis
Article usage analytics review
Knowledge gap assessment

Quarterly Triggers:

Process documentation review
Technology update documentation
Compliance requirement updates
Knowledge strategy assessment

Annual Triggers:

Comprehensive knowledge audit
Strategic documentation planning
Technology refresh documentation
Organizational change knowledge needs

Demand-Driven Capture

Knowledge capture initiated by identified need or request:

Search Failure Triggers: When users search but don’t find answers, capture the need:

Analyze zero-results searches
Identify missing documentation
Create or update articles
Optimize findability

Support Ticket Patterns: When tickets reveal documentation gaps:

Analyze ticket categories and volumes
Identify repeated issues
Create self-service content
Monitor impact on ticket reduction

Training Needs: When training reveals knowledge gaps:

Collect trainer observations
Analyze trainee questions
Document complex topics
Create reference materials

User Feedback: When users report documentation issues:

Review article ratings and comments
Prioritize low-rated content
Update based on feedback
Verify improvements with users

Capture Triggers Matrix

Trigger Type	Timing	Effort	Quality	Use Case
Event-Based	Immediate after event	Low-Medium	High (fresh details)	Incidents, changes, projects
Scheduled	Regular intervals	Medium	Medium (may lack urgency)	Process docs, reviews, audits
Demand-Driven	As needed	Low-High	High (addresses real need)	Gap filling, improvements
Automated	Continuous	Low	Variable (needs curation)	Trending issues, usage patterns

Implementing Effective Triggers

Technical Implementation:

Workflow integration in ITSM tools
Automated reminders and notifications
Template availability at point of use
Dashboard for tracking capture activities

Cultural Implementation:

Clear expectations and accountability
Recognition for timely capture
Leader modeling and reinforcement
Feedback on captured knowledge value

Optimization:

Monitor trigger effectiveness
Adjust timing and frequency
Reduce capture friction
Balance thoroughness with burden

Expert Knowledge Capture

Expert knowledge, particularly tacit expertise developed over years of experience, represents some of an organization’s most valuable and vulnerable assets. Capturing this knowledge requires specialized approaches.

Tacit Knowledge Elicitation Techniques

Tacit knowledge is difficult to articulate because experts often don’t consciously think about their expertise - it has become automatic through practice.

Cognitive Task Analysis (CTA):

Systematic approach to understanding complex cognitive work:

Steps:

Task Identification: Define the cognitive task to analyze
Knowledge Audit: Identify what expert knows and does
Knowledge Elicitation: Use multiple techniques to extract knowledge
Analysis and Representation: Structure and organize knowledge
Validation: Verify with expert and other users
Documentation: Create usable knowledge artifacts

CTA Methods:

Goal Decomposition: Break complex tasks into goals and sub-goals
Decision Laddering: Explore decision criteria and reasoning
Concept Mapping: Visualize relationships between concepts
Simulation Interview: Walk through scenarios and cases
Critical Decision Method: Analyze challenging real-world incidents

Laddering Technique:

Probe upward (why) and downward (how) to uncover reasoning and details:

Upward Laddering (Understanding Why):

“Why is that important?”
“What does that tell you?”
“Why do you check that first?”

Downward Laddering (Understanding How):

“How do you do that?”
“What specifically do you look for?”
“What are the steps involved?”

Example Exchange:

Expert: “I check the system logs first.”
Interviewer: “Why do you check the logs first?” (up)
Expert: “Because they show the sequence of events.”
Interviewer: “What does the sequence tell you?” (up)
Expert: “Whether it’s a cause or symptom.”
Interviewer: “How do you distinguish cause from symptom?” (down)
Expert: “I look for the first unusual entry that breaks the expected pattern.”
Interviewer: “What specifically makes an entry unusual?” (down)

Pattern Recognition Elicitation:

Experts recognize patterns that novices miss. Uncover these through:

Comparison Tasks:

Present similar cases with different outcomes
Ask expert to identify key differences
Document decision criteria and cues

Anomaly Detection:

Present normal and abnormal cases
Ask what seems wrong or unusual
Capture warning signs and red flags

Prototype Cases:

Elicit typical examples of each category
Identify defining characteristics
Document variations and edge cases

Retiring Expert Programs

When experienced employees retire, critical organizational knowledge can walk out the door. Structured programs can capture and transfer this expertise.

Knowledge Transfer Planning:

Begin 6-12 months before departure:

Phase 1: Assessment (6-12 months prior)

Identify expert’s critical knowledge domains
Assess existing documentation gaps
Determine successors and audiences
Prioritize knowledge to capture
Plan transfer approach and timeline

Phase 2: Capture (3-6 months prior)

Conduct structured interviews
Document critical procedures
Create decision guides
Record video demonstrations
Build case libraries

Phase 3: Transfer (1-3 months prior)

Pair expert with successors
Guided practice and observation
Q&A sessions
Review of captured materials
Build successor confidence

Phase 4: Transition (Final month)

Final questions and clarifications
Documentation completeness review
Identify remaining gaps
Establish post-departure contact agreement
Archive and organize all captured knowledge

Expert Knowledge Domains to Capture:

Knowledge Domain	Capture Approach	Deliverables
Technical Procedures	Interview + observation + documentation	Process guides, troubleshooting flowcharts
Decision-Making Criteria	Critical incident + scenario analysis	Decision matrices, judgment guides
Relationships and Context	Interview + organizational mapping	Stakeholder guides, relationship notes
Institutional Memory	Historical interview + documentation review	Historical context documents, decision records
Tacit Skills	Observation + guided practice + mentoring	Video demonstrations, apprenticeship guides
Tool and System Expertise	Screen recording + walkthrough + documentation	System guides, configuration notes

Knowledge Transfer Session Structure:

Session Planning:

60-90 minute focused sessions
Specific topic or domain per session
Successor(s) and documenter present
Recording for later reference
Prepared questions and scenarios

Session Execution:

Review session objectives
Expert explains concepts and context
Walk through examples and scenarios
Successor asks clarifying questions
Hands-on practice if applicable
Summarize key points and next steps

Post-Session Activities:

Document session notes
Create or update knowledge articles
Identify follow-up topics
Schedule practice or observation
Share materials with expert for review

Mentoring and Apprenticeship Models

Structured relationships for knowledge transfer over time:

Formal Mentoring Programs:

Structure:

Defined objectives and timeline
Regular scheduled meetings
Knowledge domains to transfer
Milestones and checkpoints
Documentation requirements

Documentation Approach:

Mentoring agreement and goals
Session notes and learnings
Knowledge gaps identified
Articles created from mentoring
Final transfer completion report

Apprenticeship and Shadowing:

Phases:

Observation: Successor watches expert work
Assisted Practice: Successor performs with expert guidance
Supervised Practice: Successor leads, expert observes
Independent Practice: Successor works independently, expert available
Full Transfer: Successor fully capable, expert transitions out

Knowledge Capture During Apprenticeship:

Expert verbalizes reasoning while working
Successor documents observations
Regular reflection sessions
Progressive creation of job aids
Building comprehensive role documentation

Communities of Practice:

Expert knowledge shared across practitioner community:

Regular meetings to share experiences
Case study discussions
Problem-solving sessions
Best practice documentation
Cross-training opportunities

Capture Tools and Templates

Standardized tools and templates reduce the effort required to capture knowledge while improving consistency and quality.

Interview Guides and Frameworks

Expert Interview Guide Template:

# Expert Interview Guide

## Interview Information
- Expert Name: _________________
- Expertise Area: _________________
- Interview Date: _________________
- Interviewer: _________________
- Objectives: _________________

## Pre-Interview Preparation
- [ ] Background research completed
- [ ] Questions prepared
- [ ] Recording arranged
- [ ] Expert briefed on purpose and process
- [ ] Session duration agreed (60-90 minutes)

## Opening (5 minutes)
- Welcome and introductions
- Confirm purpose and use of captured knowledge
- Explain interview structure
- Start recording (if applicable)

## Background and Context (10 minutes)
1. What is your role and how long have you been doing this work?
2. What are your primary responsibilities in this area?
3. How did you develop expertise in this domain?

## Core Knowledge Elicitation (40-60 minutes)

### Process and Procedures
1. Walk me through the typical process for [task].
2. What variations or exceptions exist?
3. What are the critical steps that must not be skipped?

### Problem-Solving and Troubleshooting
1. When [problem] occurs, how do you approach it?
2. What do you look for first? Why?
3. What are common misconceptions or mistakes?

### Decision-Making
1. What factors do you consider when [decision]?
2. How do you balance competing priorities?
3. When do you escalate or seek additional input?

### Critical Incidents
1. Tell me about a particularly challenging situation.
2. What made it difficult?
3. How did you resolve it?
4. What did you learn?

### Tips and Best Practices
1. What advice would you give someone new to this work?
2. What should they absolutely avoid?
3. What resources or relationships are most valuable?

### Edge Cases and Exceptions
1. What unusual scenarios have you encountered?
2. How do these differ from normal operations?
3. What special knowledge or resources are needed?

## Documentation Needs (10 minutes)
1. What documentation currently exists?
2. What gaps or pain points exist in current documentation?
3. What would be most valuable to document?
4. Who would benefit most from this documentation?

## Closing (5 minutes)
- Review key points captured
- Identify areas needing follow-up
- Schedule review of documented knowledge
- Thank expert for participation

## Post-Interview
- [ ] Transcribe or review recording
- [ ] Document key knowledge
- [ ] Identify gaps requiring follow-up
- [ ] Create draft knowledge articles
- [ ] Schedule expert review

Observation Checklists

Process Observation Checklist:

# Process Observation Checklist

## Observation Details
Process: _________________
Expert Observed: _________________
Observer: _________________
Date/Time: _________________
Location/System: _________________

## Pre-Observation
- [ ] Confirmed observation with expert
- [ ] Reviewed existing documentation
- [ ] Prepared to take notes/record
- [ ] Briefed expert on observation goals

## Process Steps

For each step observed, document:

### Step [#]: [Step Name]
- **Action**: What does the expert do?
- **Purpose**: Why is this step necessary?
- **Tools/Systems**: What is used?
- **Inputs**: What information/materials are needed?
- **Outputs**: What is produced?
- **Duration**: How long does it take?
- **Decision Points**: Any choices or judgment?
- **Validation**: How is success verified?
- **Notes**: Special observations, tips, warnings

## Tacit Knowledge Observations

- [ ] Expert shortcuts or efficiency techniques
- [ ] Visual cues or signals expert responds to
- [ ] Pattern recognition exhibited
- [ ] Judgment calls or decisions made
- [ ] Error detection and recovery
- [ ] Tool usage techniques
- [ ] Environmental or contextual factors

## Variations and Exceptions

- What variations did expert mention?
- What edge cases were discussed?
- What error conditions might occur?
- How would exceptions be handled?

## Questions Arising

1. [Question about step/decision]
2. [Question about variation]
3. [Question about underlying reasoning]

## Documentation Needs Identified

- [ ] Missing or incomplete procedures
- [ ] Undocumented troubleshooting
- [ ] Decision criteria to document
- [ ] Best practices to capture
- [ ] Common errors to highlight

## Follow-Up Required

- [ ] Clarification interview
- [ ] Additional observation needed
- [ ] Documentation creation
- [ ] Expert review of draft docs

After-Action Review (AAR) Templates

Already covered in previous section. See “AAR Documentation Template” above.

Knowledge Capture Forms

Quick Capture Form:

For rapid capture of knowledge at point of use:

# Quick Knowledge Capture

## Basic Information
- **Date**: _________
- **Author**: _________
- **Topic**: _________
- **Category**: [ ] How-To [ ] Problem-Solution [ ] Tip [ ] Lesson Learned [ ] Other

## The Knowledge

**Situation/Context**:
What was the situation or problem?

**Solution/Approach**:
What was done?

**Result**:
What happened?

**Key Insight**:
What should others know?

**When to Use**:
In what situations is this applicable?

**Cautions**:
Any warnings or things to avoid?

## Next Steps
- [ ] Needs full article development
- [ ] Needs expert review
- [ ] Ready to publish as-is
- [ ] Add to existing article

**Related Articles**: ___________
**Keywords**: ___________

Lessons Learned Template:

# Lesson Learned

## Event Information
- **Event**: _________________
- **Date**: _________________
- **Team/Department**: _________________
- **Submitted By**: _________________

## What Happened
Brief narrative of what occurred.

## Lesson Category
- [ ] Process Improvement
- [ ] Technical Solution
- [ ] Communication
- [ ] Risk Management
- [ ] Resource Management
- [ ] Other: _________

## What Worked Well
Practices or approaches that were effective.

## What Didn't Work
Practices or approaches that were ineffective or caused problems.

## Root Cause
Why did this happen? What were contributing factors?

## Recommendation
What should be done differently in the future?

## Application
- **When does this apply?**: _________
- **Who needs to know?**: _________
- **What changes are needed?**: _________

## Action Items
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
|        |       |          |        |

## Supporting Information
- Related incidents/tickets: _________
- Documentation to update: _________
- Training implications: _________

Expert Knowledge Transfer Template

Knowledge Transfer Plan:

# Knowledge Transfer Plan

## Expert Information
- **Expert Name**: _________________
- **Department**: _________________
- **Departure/Transition Date**: _________________
- **Successor(s)**: _________________

## Knowledge Domains to Transfer

| Domain | Priority | Complexity | Current Documentation | Transfer Method |
|--------|----------|------------|---------------------|-----------------|
| Domain 1 | H/M/L | H/M/L | Adequate/Partial/None | Method |
| Domain 2 | H/M/L | H/M/L | Adequate/Partial/None | Method |

## Transfer Schedule

### Phase 1: Assessment and Planning
- Dates: _________
- Activities:
  - [ ] Identify critical knowledge domains
  - [ ] Assess documentation gaps
  - [ ] Prioritize transfer needs
  - [ ] Create detailed transfer plan

### Phase 2: Knowledge Capture
- Dates: _________
- Activities:
  - [ ] Conduct expert interviews
  - [ ] Document procedures
  - [ ] Create decision guides
  - [ ] Record demonstrations
  - [ ] Build case library

### Phase 3: Knowledge Transfer
- Dates: _________
- Activities:
  - [ ] Mentoring sessions
  - [ ] Shadowing opportunities
  - [ ] Hands-on practice
  - [ ] Review captured materials
  - [ ] Q&A sessions

### Phase 4: Validation
- Dates: _________
- Activities:
  - [ ] Successor performs tasks independently
  - [ ] Expert reviews and coaches
  - [ ] Identify remaining gaps
  - [ ] Complete documentation
  - [ ] Establish ongoing contact approach

## Transfer Sessions

| Session # | Date | Topic | Duration | Participants | Deliverables |
|-----------|------|-------|----------|--------------|--------------|
| 1 | | | | | |
| 2 | | | | | |

## Documentation Deliverables

- [ ] Process procedures
- [ ] Troubleshooting guides
- [ ] Decision matrices
- [ ] System configurations
- [ ] Relationship and contact information
- [ ] Historical context documents
- [ ] Video demonstrations
- [ ] Case studies

## Success Criteria

- [ ] All critical knowledge domains addressed
- [ ] Successors feel confident in capabilities
- [ ] Documentation complete and reviewed
- [ ] Knowledge validated through practice
- [ ] Stakeholders briefed on transition

## Post-Departure Support

- Expert contact approach: _________
- Questions escalation process: _________
- Documentation repository: _________
- Ongoing support arrangement: _________

Overcoming Capture Barriers

Even with good methods and tools, organizations face barriers to effective knowledge capture. Understanding and addressing these barriers is essential for success.

Common Barriers to Knowledge Capture

Barrier	Impact	Root Causes
Time Constraints	Knowledge not captured due to operational priorities	Lack of dedicated time, competing deadlines, firefighting mode
Lack of Skills	Poor quality documentation, ineffective elicitation	No training in writing or knowledge capture techniques
Low Motivation	Knowledge hoarding, minimal participation	No incentives, fear of reduced value, lack of recognition
Perfectionism	Delays in publishing, over-editing	Fear of criticism, unclear “good enough” standard
Tool Complexity	Friction in capture process, workarounds	Difficult systems, too many steps, technical barriers
Unclear Ownership	Nobody responsible for capture	Diffuse accountability, no assigned roles
Quality Concerns	Reluctance to publish inadequate content	Lack of review process, unclear standards
Cultural Issues	Knowledge seen as power, not shared	Competitive culture, silos, lack of trust

Time Constraint Solutions

Build Capture into Workflows:

Integrate knowledge capture into existing processes so it’s not “extra work”:

ITSM Integration:

Mandatory solution field in ticket closure
Knowledge article checkbox in problem records
AAR required for major incidents
Post-implementation review in change management
Project closeout knowledge deliverables

Time Allocation:

Dedicated documentation time in schedules
“Capture Friday” - last hour of week for documentation
Sprint velocity adjusted for documentation tasks
Knowledge capture as performance objective

Reduce Capture Effort:

Make capture as quick and easy as possible:

Techniques:

Templates and forms pre-fill standard sections
Voice-to-text for rapid capture
Screen recording instead of written procedures
Quick capture buttons in workflows
AI-assisted drafting from raw notes

Value Demonstration:

Show time invested returns benefits:

Metrics to Track:

Support tickets deflected by self-service
Time saved by reusing documented solutions
Onboarding time reduction
Escalation reduction
Error prevention

Reluctance and Motivation Solutions

Recognition and Rewards:

Recognition Type	Implementation	Impact
Public Acknowledgment	Shout-outs in meetings, newsletters, dashboards	Peer respect, visibility
Performance Metrics	KM contribution in reviews and goals	Career advancement
Gamification	Points, badges, leaderboards	Engagement, competition
Expert Status	Subject matter expert designation	Authority, influence
Monetary Rewards	Bonuses, prizes for contributions	Financial incentive
Career Development	Technical writing skills, teaching opportunities	Professional growth

Address Knowledge Hoarding:

Fear of Reduced Value:

Recognize experts for teaching others
Create expert mentor roles
Promote based on knowledge sharing
Highlight expert status through attribution

Fear of Being Wrong:

Emphasize learning culture over blame
Implement supportive review process
Share examples of senior leader mistakes
Normalize iteration and improvement

Competitive Culture:

Team-based incentives, not just individual
Cross-functional collaboration metrics
Knowledge sharing in team objectives
Leadership modeling of sharing

Build Intrinsic Motivation:

Purpose:

Connect capture to helping colleagues
Show impact of shared knowledge
Highlight benefits to customers
Relate to organizational mission

Autonomy:

Choice in what to document
Flexibility in capture method
Control over published content
Self-directed improvement

Mastery:

Develop documentation skills
Growth as teacher/mentor
Recognition as expert
Professional development

Quality Issue Solutions

Clear Quality Standards:

Define “good enough” to prevent over-editing:

Minimum Viable Article Standards:

Accurate information
Clear structure (template followed)
Actionable steps
Proper metadata
SME approval

Publication Threshold:

70% solution published is better than 100% solution delayed
Continuous improvement approach
Version history visible
Community feedback encouraged

Review and Support Processes:

Support Mechanism	Purpose	Implementation
Writing Center	Help with documentation	Office hours, writing coaches
Peer Review	Collaborative improvement	Review buddies, team reviews
Editorial Support	Polish and consistency	Editors help with clarity
Templates	Structure and completeness	Easy-to-use article templates
Style Guide	Consistency across content	Clear writing standards
Review Checklists	Ensure quality dimensions	Self-review and peer review checklists

Feedback and Iteration:

Continuous Improvement:

User ratings and comments
Usage analytics
Search failure analysis
Regular content audits
Scheduled reviews and updates

Tool Complexity Solutions

Simplify Capture Process:

Reduce Friction:

Single sign-on
Mobile-friendly interfaces
One-click capture from workflows
Email-to-article features
API integrations with existing tools

Provide Alternatives:

Multiple capture paths for different preferences:

Web forms for structured capture
Email submissions for quick capture
Voice recording for verbal processors
Screen recording for visual demonstrations
API/automation for technical users

Training and Support:

Capability Building:

Quick start guides and job aids
Video tutorials
Hands-on training sessions
Super-user network for peer support
Help desk support for tool issues

Incentive Structures

Formal Incentive Programs:

# Knowledge Contribution Incentive Program

## Recognition Tiers

### Bronze (Entry Level)
- **Requirements**: 5 articles published, average quality score ≥3.5/5
- **Benefits**:
  - Certificate of recognition
  - Name featured in newsletter
  - Contributor badge in profile

### Silver (Active Contributor)
- **Requirements**: 15 articles published, average quality score ≥4.0/5, 500+ article views
- **Benefits**:
  - Gift card (example: $50 value—adjust to your organization's recognition budget)
  - Featured in knowledge champion spotlight
  - Access to advanced training
  - Invitation to quarterly KM advisory group

### Gold (Knowledge Champion)
- **Requirements**: 30+ articles, quality score ≥4.5/5, 2000+ views, mentors other contributors
- **Benefits**:
  - Significant gift card (example: $150 value—adjust to your organization's recognition budget)
  - Executive recognition event
  - Professional development opportunity
  - Permanent designation as Subject Matter Expert
  - Speaking opportunity at company events

### Platinum (KM Leader)
- **Requirements**: 50+ articles, quality score ≥4.5/5, 5000+ views, drives KM initiatives
- **Benefits**:
  - Major award (example: $500 value or equivalent—adjust to your organization's recognition budget)
  - Executive team presentation
  - External conference attendance
  - Consideration for KM leadership roles
  - Company-wide recognition

## Performance Integration

### Individual Performance Reviews
- Knowledge contribution as weighted objective (10-15% of review)
- Specific goals for article creation and quality
- Recognition for mentoring and peer review

### Team Metrics
- Team knowledge contribution rates
- Quality scores and usage metrics
- Knowledge sharing culture indicators
- Integration with team performance goals

## Special Recognition

### Monthly Awards
- Article of the Month (highest quality new article)
- Most Helpful Contributor (highest usage/impact)
- Community Champion (most peer reviews and mentoring)

### Annual Awards
- Knowledge Management Excellence Award
- Lifetime Achievement in Knowledge Sharing
- Innovation in Knowledge Capture

Informal Recognition:

Day-to-Day Appreciation:

Thank-you emails cc’d to leadership
Praise in team meetings
Slack/Teams channel for knowledge wins
Manager feedback and appreciation
Peer nominations and thanks

Knowledge Elicitation Techniques

Structured Interviews

Systematic approach to extracting knowledge from experts:

Preparation Phase:

Research the expert’s background and area of expertise
Define learning objectives and key questions
Review existing documentation and identify gaps
Schedule adequate time (typically 60-90 minutes)
Prepare recording/note-taking approach

Interview Techniques:

Technique	When to Use	Example Questions
Critical Incident	Understand problem-solving and decision-making	“Tell me about a time when X went wrong. What did you do?”
Scenario-Based	Elicit conditional knowledge and judgment	“If you encountered Y situation, how would you handle it?”
Process Walkthrough	Document procedures and workflows	“Walk me through the steps you take to accomplish Z.”
Decision Analysis	Understand decision criteria and trade-offs	“What factors do you consider when deciding between options?”
Problem Exploration	Identify troubleshooting approaches	“When users report problem X, what do you check first? Why?”
Exception Handling	Capture edge cases and variations	“What are the unusual cases or exceptions to the normal process?”

Follow-up Phase:

Document the interview while details are fresh
Identify gaps or areas needing clarification
Share draft documentation with the expert for review
Iterate until accuracy is confirmed

Cognitive Task Analysis

Detailed method for understanding complex cognitive work:

Steps in Cognitive Task Analysis:

Knowledge Audit: Identify what the expert needs to know and do
Knowledge Elicitation: Extract knowledge using multiple techniques (observation, interview, scenario analysis)
Knowledge Analysis: Organize and structure the elicited knowledge
Knowledge Representation: Document knowledge in usable formats
Knowledge Verification: Validate with experts and potential users

Applications:

Documenting complex troubleshooting procedures
Capturing diagnostic expertise
Creating decision support systems
Developing training programs for complex skills

Group Knowledge Capture

Leveraging collective knowledge through facilitated sessions:

Retrospectives: Team reflection on what worked, what didn’t, and what to improve. Structure using “Start, Stop, Continue” or “Went Well, Needs Improvement, Action Items.”

Knowledge Cafes: Informal discussion sessions where participants explore topics and share experiences in small groups that rotate between topics.

World Cafe Method: Large group conversation process where participants move between tables discussing questions, with ideas building across rounds.

Delphi Technique: Structured process using multiple rounds of questionnaires to achieve consensus among experts on complex issues.

Nominal Group Technique: Structured brainstorming approach where participants independently generate ideas, then share and prioritize as a group.

Documentation Techniques

Article Templates

Standardized templates ensure consistency and completeness:

How-To Article Template:

# [Task/Process Name]

## Overview
Brief description of what this procedure accomplishes and when to use it.

## Prerequisites
- Required access, tools, or preparations
- Skills or knowledge needed
- Related articles to review first

## Steps
1. Step one with clear action verb
   - Additional details or notes
   - Expected results
2. Step two...
3. Step three...

## Verification
How to confirm the procedure was completed successfully.

## Troubleshooting
Common issues and their solutions:
- Issue 1: Solution
- Issue 2: Solution

## Additional Notes
- Important warnings or cautions
- Tips and best practices
- When to escalate or seek help

## Related Articles
- Link to related procedures
- Link to background information
- Link to troubleshooting guide

## Metadata
- Last Updated: [Date]
- Owner: [Name/Team]
- Applies To: [Systems/Versions]
- Keywords: [tags]

Problem-Solution Article Template:

# [Problem/Error Description]

## Symptoms
Clear description of what users experience or observe.

## Cause
Root cause or underlying issue (if known).

## Resolution
### Quick Fix
Immediate workaround or temporary solution.

### Permanent Solution
Complete resolution steps:
1. Step one...
2. Step two...
3. Step three...

## Prevention
How to avoid this problem in the future.

## Related Problems
- Similar issues users might encounter
- Upstream/downstream impacts

## Technical Details
Additional information for advanced users or troubleshooting.

## Metadata
- Affected Systems: [list]
- Severity: [Critical/High/Medium/Low]
- Frequency: [Common/Occasional/Rare]
- Last Updated: [Date]

Decision Record Template:

# [Decision Title]

## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-XXX]

## Context
What is the issue we're trying to solve? What factors are influencing this decision?

## Decision
What is the change we're proposing/making?

## Rationale
Why did we choose this option?

## Alternatives Considered
What other options did we evaluate?
- Option 1: Pros and Cons
- Option 2: Pros and Cons

## Consequences
What are the implications of this decision?
- Positive consequences
- Negative consequences
- Risks and mitigation

## Related Decisions
- Links to related decision records
- Dependencies or prerequisites

Writing Effective Knowledge Articles

Clarity Principles:

Principle	Description	Example
User-Focused	Write from the user’s perspective and use cases	“To reset a user password…” not “The password reset function…”
Action-Oriented	Start with clear action verbs	“Click,” “Enter,” “Select,” “Verify”
Specific	Provide exact details, not vague descriptions	“Click the blue ‘Submit’ button” not “Submit the form”
Structured	Use consistent organization and formatting	Templates, numbered steps, clear headings
Visual	Include screenshots, diagrams, or videos where helpful	Annotate images to highlight key elements
Contextual	Explain when and why, not just how	“Use this approach when performance is critical…”
Searchable	Include terms users would search for	Keywords, synonyms, error messages

Quality Checklist:

Knowledge Creation

Converting Implicit Knowledge to Explicit

Many valuable insights exist as implicit knowledge - patterns and understanding that haven’t been formally articulated. This conversion is the essence of the SECI model’s Externalization mode.

Identification Methods:

Analyze frequently asked questions
Review resolved support tickets and problem records
Monitor discussion forums and collaboration spaces
Conduct knowledge gap analysis
Survey users about documentation needs

Creation Approaches:

Synthesize patterns from multiple sources (tickets, emails, discussions)
Document tribal knowledge through interviews and observation
Create visualizations that make patterns and relationships explicit
Develop decision trees or diagnostic guides from expert judgment
Build reference materials from scattered information

Collaborative Knowledge Creation

Leveraging collective intelligence to create comprehensive knowledge assets:

Wiki-Style Collaboration:

Start with a basic structure or outline
Enable multiple contributors to add and refine content
Use discussion/comments for questions and coordination
Implement version control to track changes
Designate content owners to maintain quality and coherence

Documentation Sprints:

Time-boxed events (typically 1-3 days) focused on creating documentation
Bring together experts, writers, and users
Target specific documentation gaps or priorities
Use templates and style guides for consistency
Conduct peer review before publishing

Book Sprints:

Intensive 3-5 day events to create comprehensive documentation or guides
Facilitated process with defined roles (authors, facilitator, technical support)
Collaborative writing, editing, and illustration
Produces complete, publication-ready content

Content Quality Standards

Quality Dimensions

Effective knowledge assets must meet multiple quality criteria:

Quality Dimension	Description	Assessment Questions
Accuracy	Information is correct and factually precise	Is the information correct? Are there errors or inaccuracies?
Completeness	All necessary information is included	Are there gaps? Is anything missing? Does it answer the full question?
Currency	Information is up-to-date and relevant	When was this last updated? Is it still accurate?
Clarity	Content is easy to understand	Can the target audience understand this? Is language clear and unambiguous?
Consistency	Format and terminology align with standards	Does it follow templates and style guides? Is terminology consistent?
Relevance	Content addresses real user needs	Does this answer common questions? Is it useful to the target audience?
Findability	Users can discover the content when needed	Is it properly titled, tagged, and categorized? Will searches find it?
Usability	Content can be easily applied	Can users follow this successfully? Are steps clear and actionable?

Quality Review Process

Peer Review Approach:

Author Self-Review: Creator checks against quality checklist before submission
Technical Review: Subject matter expert verifies accuracy and completeness
Editorial Review: Editor checks clarity, consistency, and style compliance
User Testing: Representative users test procedures and provide feedback
Final Approval: Content owner approves for publication
Post-Publication Review: Monitor usage and feedback; update as needed

Lightweight Review Options:

Single reviewer (technical or editorial depending on content type)
Community review (publish draft, solicit feedback, revise)
Continuous improvement (publish minimum viable content, improve based on usage)

Knowledge Capture Tools and Technologies

Content Creation Tools

Authoring Tools:

Markdown Editors: Simple, text-based authoring with formatting (Typora, MarkText, VS Code)
Wiki Platforms: Collaborative documentation with version control (Confluence, MediaWiki, BookStack)
Documentation Generators: Convert code comments and structured text to documentation (Sphinx, MkDocs, Docusaurus)
Screen Recording: Capture procedures visually (Loom, SnagIt, Camtasia)

Diagram and Visualization Tools:

Flowcharting: Process flows and decision trees (Lucidchart, Draw.io, Visio)
Mind Mapping: Concept mapping and brainstorming (MindMeister, XMind)
Diagram-as-Code: Version-controlled visual documentation (Mermaid, PlantUML, Graphviz)

Capture Support Tools

Interview and Elicitation Tools:

Recording and Transcription: Capture and transcribe expert interviews (Otter.ai, Rev, Teams/Zoom transcription)
Screen Capture: Record expert demonstrations (OBS Studio, Loom, SnagIt)
Collaborative Whiteboards: Visual collaboration during elicitation sessions (Miro, Mural, FigJam)

Automated Capture Tools:

Activity Analytics: Identify knowledge needs from user behavior (search logs, page analytics)
Conversation Mining: Extract insights from chat and collaboration platforms (AI analysis of Slack, Teams)
Process Mining: Document actual processes from workflow data (Celonis, UiPath Process Mining)

Knowledge Capture Strategy

Prioritization Framework

Not all knowledge is equally valuable to capture. Prioritize based on:

Value Dimensions:

Dimension	High Priority	Low Priority
Business Impact	Affects critical operations, revenue, or compliance	Limited operational impact
Reuse Potential	Needed frequently by many people	Rarely needed or single-use
Knowledge Risk	Held by few experts, retirement risk	Widely distributed knowledge
Current State	Not documented, scattered, or outdated	Well documented and current
Effort Required	Can be captured efficiently	Extremely difficult or time-consuming
Urgency	Time-sensitive need or deadline	Can be deferred

Prioritization Matrix:

High Impact + High Risk = URGENT - Capture immediately
High Impact + Low Risk = IMPORTANT - Schedule capture
Low Impact + High Risk = OPPORTUNISTIC - Capture if easy
Low Impact + Low Risk = DEFERRED - Capture only if time permits

Capture Planning

Knowledge Capture Project Plan:

Scope Definition
- Identify knowledge domain or topic area
- Define target audience and their needs
- Determine success criteria and deliverables
Expert Identification
- Identify subject matter experts and stakeholders
- Assess availability and willingness to participate
- Plan for backup experts if needed
Method Selection
- Choose elicitation techniques appropriate to the knowledge type
- Select documentation formats and templates
- Plan for tools and support needed
Schedule and Resources
- Allocate time for elicitation, documentation, and review
- Assign roles (facilitator, documenter, reviewer)
- Schedule sessions and milestones
Execution
- Conduct elicitation sessions
- Create documentation drafts
- Facilitate review and iteration
Quality Assurance
- Conduct technical and editorial review
- Test with representative users
- Obtain final approval
Publication and Socialization
- Publish to knowledge repository
- Announce availability to target audience
- Integrate into training or onboarding as appropriate

Connection to SECI Model

The knowledge capture and creation practices described in this chapter primarily address the Externalization mode of the SECI model - converting tacit knowledge into explicit knowledge. Understanding this connection helps contextualize capture within the broader knowledge conversion cycle.

Externalization in the SECI Model

Externalization (Tacit → Explicit): The process of articulating tacit knowledge into explicit concepts through:

Metaphors and analogies that make implicit understanding explicit
Dialogue and reflection that surface assumptions and insights
Documentation that codifies expertise and experience
Models and frameworks that structure intuitive knowledge

Why Externalization Is Critical:

Makes individual expertise available to the organization
Preserves knowledge that would otherwise be lost
Enables scaling of expertise across teams and locations
Creates foundation for organizational learning
Supports innovation through recombination of explicit knowledge

Knowledge Capture Methods Mapped to SECI

Capture Method	SECI Mode	Knowledge Flow
Expert Interviews	Externalization	Expert’s tacit knowledge → Documented procedures
After-Action Reviews	Externalization	Team experience → Lessons learned articles
Observation	Externalization	Expert’s tacit practice → Process documentation
Collaboration	Socialization + Externalization	Shared tacit knowledge → Co-created explicit assets
Documentation Synthesis	Combination	Multiple explicit sources → Integrated knowledge base

Integration with Other SECI Modes

While this chapter focuses on Externalization (capture), effective knowledge management requires all four SECI modes:

Socialization (Tacit → Tacit):

Mentoring and apprenticeship programs
Communities of practice
Job shadowing and observation
Covered in Chapter 11 (Communities)

Combination (Explicit → Explicit):

Organizing and integrating captured knowledge
Creating knowledge architecture and taxonomy
Building comprehensive documentation from fragments
Covered in Chapter 10 (Conversion)

Internalization (Explicit → Tacit):

Using captured knowledge to build individual expertise
Learning from documentation
Training and skill development
Covered in Chapters 12 (Transfer) and 15 (Adoption)

The Complete Cycle:

Socialization: Experts share tacit knowledge through mentoring
Externalization: Tacit expertise documented (this chapter)
Combination: Documents organized into knowledge base (Chapter 10)
Internalization: Others learn from knowledge base, building new tacit knowledge
Cycle repeats: New expertise shared and captured

Facilitating Externalization

Effective externalization requires addressing common challenges:

Tacit Knowledge Is Hard to Articulate:

Use structured elicitation techniques (interviews, CTA)
Employ scenario-based questioning
Combine observation with verbal explanation
Use metaphors and analogies
Create safe environment for imperfect articulation

Quality Varies Across Contributors:

Provide templates and examples
Offer writing support and editing
Implement review processes
Focus on “good enough” not perfection
Enable iterative improvement

Time and Motivation Barriers:

Integrate capture into workflows
Provide clear incentives and recognition
Make capture tools easy to use
Demonstrate value and impact
Allocate dedicated time

Figures and Visual Frameworks

Figure 9.1: Knowledge Capture Process Flow

Figure 9.1: Knowledge Capture Process Flow Caption: End-to-end process from trigger identification through publication and improvement Position: Place after “Knowledge Capture Strategy” section

[Trigger Event] → [Capture Decision] → [Elicitation] → [Documentation] → [Review] → [Publication] → [Usage & Feedback] → [Improvement]
      ↓                    ↓                 ↓                ↓              ↓             ↓                  ↓                    ↓
  ┌─────────┐      ┌──────────────┐   ┌──────────┐   ┌──────────┐   ┌────────┐   ┌──────────┐      ┌────────────┐      ┌──────────┐
  │ Event   │      │ Prioritize   │   │ Select   │   │ Create   │   │ QA     │   │ Publish  │      │ Monitor    │      │ Update   │
  │ Occurs  │──────▶ Value & Risk │───▶ Method   │───▶ Draft    │───▶ Review │───▶ & Share  │──────▶ Usage     │──────▶ Content  │
  │         │      │              │   │          │   │          │   │        │   │          │      │            │      │          │
  └─────────┘      └──────────────┘   └──────────┘   └──────────┘   └────────┘   └──────────┘      └────────────┘      └──────────┘
                            │                                                                                │
                            │                                                                                │
                            └────────────────────── Not High Priority ──────────────────────────────────────┘
                                                         (Defer or Reject)

Figure 9.2: Expert Knowledge Transfer Model

Figure 9.2: Expert Knowledge Transfer Model Caption: Four-phase model for systematic expert knowledge transfer with overlapping activities Position: Place in “Expert Knowledge Capture” section

Phase 1: Assessment         Phase 2: Capture           Phase 3: Transfer          Phase 4: Validation
(6-12 months before)        (3-6 months before)        (1-3 months before)       (Final month)
┌──────────────────┐        ┌──────────────────┐       ┌──────────────────┐      ┌──────────────────┐
│ • Identify       │        │ • Interviews     │       │ • Mentoring      │      │ • Independent    │
│   knowledge      │────────▶ • Documentation  │───────▶ • Shadowing      │──────▶   practice      │
│   domains        │        │ • Recording      │       │ • Practice       │      │ • Final review   │
│ • Assess gaps    │        │ • Case library   │       │ • Q&A            │      │ • Handoff        │
│ • Plan transfer  │        │                  │       │                  │      │                  │
└──────────────────┘        └──────────────────┘       └──────────────────┘      └──────────────────┘
         │                           │                          │                          │
         └───────────────────────────┴──────────────────────────┴──────────────────────────┘
                                    Continuous Activities:
                        • Documentation creation and review
                        • Relationship and context capture
                        • Successor confidence building
                        • Stakeholder communication

Capture Method Comparison Table

Method	Tacit Knowledge Capture	Explicit Knowledge Creation	Time Investment	Skill Required	Best For
Structured Interview	High	High	High (hours per session)	High	Deep expertise, complex domains
Observation	Very High	Medium	Very High (days/weeks)	Medium	Physical tasks, tacit skills
After-Action Review	Medium	Medium	Low (1-2 hours)	Low	Event-based lessons
Screen Recording	Medium	High	Medium (setup + recording)	Medium	Software procedures
Documentation Sprint	Low	High	Medium (dedicated days)	Medium	Known gaps, multiple topics
Crowdsourcing	Low	Medium	Low (distributed)	Low	Broad participation, Q&A
Automated	Very Low	Low	Very Low (passive)	Low	Patterns, trends, gaps

Capture Triggers Matrix

Trigger Type	Frequency	Knowledge Quality	Capture Burden	Sustainability	Examples
Event-Based	Variable	High (fresh, detailed)	Low-Medium	High (workflow integrated)	Incident resolution, project closeout
Scheduled	Regular	Medium (may lack urgency)	Medium	Medium (requires discipline)	Weekly retrospectives, monthly reviews
Demand-Driven	As-needed	High (addresses real need)	Variable	Medium (reactive)	Search failures, ticket patterns
Automated	Continuous	Low-Medium (needs curation)	Very Low	High (passive)	Search analytics, trending topics

Expert Interview Question Framework

Question Type	Purpose	Sample Questions	When to Use
Open-Ended	Explore broadly, get narrative	“Tell me about…”, “Describe how…”	Beginning of interview, new topics
Probing	Dig deeper, clarify	“Why is that?”, “What do you mean by…?”	Follow-up to uncover reasoning
Scenario-Based	Elicit judgment, decision-making	“If X happens, what would you do?”	Understanding conditional knowledge
Process	Document procedures	“Walk me through the steps…”	Capturing procedures and workflows
Critical Incident	Understand problem-solving	“Tell me about a challenging case…”	Eliciting expert problem-solving
Exception	Capture edge cases	“What unusual situations have you seen?”	Identifying variations and outliers
Best Practice	Extract wisdom	“What’s your advice for…”	Capturing tips and insights

Barrier Solutions Matrix

Barrier	Quick Wins (0-3 months)	Medium-Term (3-6 months)	Long-Term (6-12 months)
Time Constraints	Quick capture forms, voice-to-text	Workflow integration, dedicated time	Cultural shift, capacity planning
Lack of Skills	Templates, writing tips	Writing workshops, peer mentoring	Formal training, writing center
Low Motivation	Public recognition, thank-yous	Gamification, contests	Performance integration, career paths
Tool Complexity	Simplified interfaces, job aids	Mobile apps, automation	Tool replacement, UX redesign
Quality Concerns	Clear standards, examples	Peer review, editorial support	Continuous improvement culture
Unclear Ownership	Assign content owners	Define roles and responsibilities	Governance framework, accountability

Review Questions

Externalization and the SECI Model
- How does knowledge capture relate to the SECI model’s Externalization mode?
- Why is Externalization critical for organizational knowledge management?
- What makes Externalization challenging to achieve effectively?
Capture Method Selection for Retiring Experts
- What capture methods would you use for a retiring expert with 25 years of experience in a critical technical area?
- How would you structure the timeline and phases for this knowledge transfer?
- What deliverables would you create during the transfer process?
- How would you address the expert’s concern about being “too busy” to participate extensively?
Overcoming Capture Barriers
- What are at least four potential root causes for a 15% documentation rate in an IT support team?
- What specific, actionable solutions would you propose for each identified cause?
- How would you measure improvement in documentation rates over time?
Event-Based Trigger Design
- How would you design a knowledge capture trigger for project closeouts?
- What specific information would be captured at project closeout?
- Who should be involved in the capture process?
- What template or structure would facilitate effective capture?
- How would you ensure consistent follow-through on capture activities?
Quality vs. Speed Trade-offs
- What are the trade-offs between rigorous multi-step review processes and “publish fast, improve continuously” approaches?
- What middle ground would balance quality and speed effectively?
- Under what circumstances would you favor rigorous review before publication?
- Under what circumstances would you favor rapid publication with continuous improvement?

Key Takeaways

Knowledge capture must be strategic, focusing on high-value, high-risk knowledge areas rather than attempting to document everything
Just-in-time capture integrated into existing workflows (after-action reviews, ticket resolution, project closeouts) is more sustainable than separate documentation efforts
Effective knowledge elicitation requires structured techniques like expert interviews, cognitive task analysis, and facilitated group sessions
Standardized templates and style guides ensure consistency, completeness, and usability of knowledge assets
Quality standards and review processes are essential to maintain accuracy, clarity, and relevance of captured knowledge
Knowledge creation is not just transcription - it involves synthesis, organization, and conversion of implicit patterns into explicit assets through the SECI model’s Externalization mode
Collaborative approaches to knowledge creation leverage collective intelligence and distribute the documentation burden
Technology tools should facilitate and accelerate knowledge capture, not add overhead or complexity
Prioritization frameworks help focus limited resources on the knowledge that provides the greatest organizational value
Successful knowledge capture requires addressing both the technical aspects (methods, tools, standards) and the human aspects (motivation, time, skills)
Event-based, scheduled, and demand-driven triggers ensure knowledge is captured at optimal moments
Expert knowledge transfer requires structured approaches including assessment, capture, transfer, and validation phases
Overcoming capture barriers requires understanding root causes and implementing targeted solutions for time, motivation, skills, and tool issues
Effective incentive structures combine recognition, career development, and integration with performance management

Summary

Knowledge capture and creation are foundational capabilities for any knowledge management program. This chapter has explored the methods, techniques, and practices that enable organizations to systematically capture valuable knowledge and create high-quality knowledge assets.

Effective knowledge capture requires a strategic approach that prioritizes high-value knowledge, integrates capture activities into existing workflows, provides standardized templates and tools, and establishes quality standards. Organizations must choose appropriate elicitation techniques based on the type of knowledge being captured, from structured interviews and cognitive task analysis to group facilitation methods and crowdsourcing approaches.

Creating usable knowledge assets requires more than transcription. It involves converting tacit and implicit knowledge into explicit documentation through the SECI model’s Externalization mode, writing clearly and user-focused content, and organizing information in ways that support effective discovery and use. Quality standards and review processes ensure that captured knowledge is accurate, complete, current, and usable.

Timing matters significantly - implementing event-based, scheduled, and demand-driven triggers ensures knowledge is captured when it has maximum value and freshness. Expert knowledge transfer, particularly for retiring experts, requires structured multi-phase approaches that balance capture efficiency with thoroughness.

Success in knowledge capture depends on addressing both technical and human factors. While tools and techniques are important, overcoming barriers related to time, motivation, skills, and tool complexity determines whether knowledge capture becomes a sustainable practice. Effective incentive structures that include recognition, career development, and performance integration drive long-term engagement.

Organizations that integrate knowledge capture into standard work processes, recognize and reward contributions, provide the necessary support and training, and continuously improve based on usage and feedback will build valuable knowledge assets that enhance organizational capability and performance.

The next chapter explores the full spectrum of knowledge conversion techniques through the SECI model, examining how knowledge flows between tacit and explicit forms to create organizational learning and innovation.

Previous Chapter	Table of Contents	Next Chapter
Chapter 8: Knowledge Architecture	Handbook Home	Chapter 10: Tacit to Explicit Knowledge Conversion

Chapter 9: Knowledge Capture and Creation

Learning Objectives

Introduction

The Knowledge Capture Challenge

Why Knowledge Capture Is Difficult

Strategic Approach to Knowledge Capture

Knowledge Capture Methods

Just-in-Time Capture

Planned Knowledge Capture

Automated and Passive Capture

Capture Methods Deep Dive

Interview and Debrief Methods

Observation Methods

After-Action Review (AAR) Method

Knowledge Elicitation Techniques

Crowdsourcing Knowledge

Capture Triggers and Timing

Event-Based Triggers

Scheduled Capture Activities

Demand-Driven Capture

Capture Triggers Matrix

Implementing Effective Triggers

Expert Knowledge Capture

Tacit Knowledge Elicitation Techniques

Retiring Expert Programs

Mentoring and Apprenticeship Models

Capture Tools and Templates

Interview Guides and Frameworks

Observation Checklists

After-Action Review (AAR) Templates

Knowledge Capture Forms

Expert Knowledge Transfer Template

Overcoming Capture Barriers

Common Barriers to Knowledge Capture

Time Constraint Solutions

Reluctance and Motivation Solutions

Quality Issue Solutions

Tool Complexity Solutions

Incentive Structures

Knowledge Elicitation Techniques

Structured Interviews

Cognitive Task Analysis

Group Knowledge Capture

Documentation Techniques

Article Templates

Writing Effective Knowledge Articles

Knowledge Creation

Converting Implicit Knowledge to Explicit

Collaborative Knowledge Creation

Content Quality Standards

Quality Dimensions

Quality Review Process

Knowledge Capture Tools and Technologies

Content Creation Tools

Capture Support Tools

Knowledge Capture Strategy

Prioritization Framework

Capture Planning

Connection to SECI Model

Externalization in the SECI Model

Knowledge Capture Methods Mapped to SECI

Integration with Other SECI Modes

Facilitating Externalization

Figures and Visual Frameworks

Figure 9.1: Knowledge Capture Process Flow

Figure 9.2: Expert Knowledge Transfer Model

Capture Method Comparison Table

Capture Triggers Matrix

Expert Interview Question Framework

Barrier Solutions Matrix

Review Questions

Key Takeaways

Summary

Chapter Navigation