PKMC Module IV flashcards
PKMC Module IV · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Tacit knowledge
- Knowledge held in personal experience, intuition, and skill that is difficult to articulate or codify. It transfers best through observation, mentoring, and joint work rather than documents.
- Explicit knowledge
- Knowledge that has been codified into documents, procedures, models, or databases so it can be stored, searched, and transferred independently of the person who created it.
- DIKW hierarchy
- A model ordering data, information, knowledge, and wisdom. Each level adds context and interpretation, with wisdom representing judgment about when and how to apply knowledge.
- Knowledge life cycle
- The sequence of creating, validating, codifying, storing, sharing, applying, and retiring knowledge. Value is realized only when knowledge is actually applied.
- Structured interview
- An elicitation method using a fixed set of predetermined questions asked consistently across interviewees. It supports comparison and coverage but limits exploration of unexpected topics.
- Delphi technique
- An anonymous, multi-round expert elicitation using controlled feedback between rounds to converge opinion. It reduces dominance and groupthink but requires several cycles and time.
- Nominal group technique
- A structured group method: silent individual idea generation, round-robin recording of ideas, then ranked voting. It reduces groupthink compared with open discussion.
- Observation (job shadowing)
- Watching people perform work to capture tacit know-how they cannot easily describe. It reveals workarounds and implicit rules but is time-consuming and can alter behavior.
- After-action review
- A structured debrief immediately after an event asking what was supposed to happen, what happened, why the difference, and what to improve. It captures knowledge while memory is fresh.
- Focus group
- A facilitated discussion with roughly six to ten participants that surfaces shared and conflicting views. Individual interviews are preferable when hierarchy would suppress candor.
- Affinity diagramming
- A technique for clustering large numbers of generated ideas or knowledge items into related groups, revealing themes and structure before prioritization or documentation.
- Metadata for knowledge assets
- Descriptive attributes attached to an asset, minimally title, owner, creation date, version, source project, sensitivity classification, and review or expiry date, enabling retrieval and control.
- Taxonomy versus folksonomy
- A taxonomy is a controlled hierarchical classification; a folksonomy is user-generated tagging. Combining both balances consistency with the findability of emerging terms.
- Retrieval precision
- The proportion of returned search results that are relevant, calculated as relevant items returned divided by total items returned. It falls as repositories grow without curation.
- Retrieval recall
- The proportion of all relevant items that a search actually returns, calculated as relevant items returned divided by all relevant items in the repository.
- Single source of truth
- A principle that each knowledge asset has exactly one authoritative location. Other appearances are links or references, preventing conflicting duplicate versions.
- Information architecture layers
- The four layers enabling retrieval: repository for storage, taxonomy and metadata for organization, search and navigation for retrieval, and permissions for access control.
- Least privilege access
- An access control principle granting users only the knowledge and systems permissions needed for their role. Classification and need-to-know determine what can be stored, viewed, or exported.
- SECI model
- A knowledge conversion model: socialization (tacit to tacit), externalization (tacit to explicit), combination (explicit to explicit), and internalization (explicit to tacit).
- Communities of practice
- Voluntary cross-project groups bound by shared interest in a domain. They differ from formal project teams and temporary task forces and are suited to ongoing peer knowledge exchange.
- Absorptive capacity
- The receiver's ability to recognize and internalize new knowledge, dependent on prior related knowledge and available time. Sending a document does not guarantee transfer.
- Knowledge broker
- A person who spans organizational or technical boundaries and translates knowledge between groups, reducing transfer loss where disciplines, vocabularies, or cultures differ.
- Media richness fit
- Matching communication channel to knowledge complexity: rich media such as face-to-face suit ambiguous knowledge, while lean media such as documents suit simple codified knowledge.
- Push versus pull transfer
- Push mechanisms broadcast knowledge to recipients through reports and portals; pull mechanisms let users seek it through search and expert access. Effective programs combine both.
- Reuse applicability assessment
- Evaluating whether a prior lesson or asset fits a new context by comparing scale, sector, technology, and constraints. Low similarity raises adaptation cost and failure risk.
- Actionable lesson format
- A lesson written as a trigger condition plus recommended action rather than narrative history, making it directly reusable by future project teams facing the same situation.
- Decision log
- A record of key decisions with rationale, alternatives considered, date, and decision maker. It preserves reasoning so later teams can reuse the thinking, not only the outcome.
- Reuse rate metric
- A measure of how often existing knowledge assets are applied in delivery, such as templates used or prior lessons referenced in plans, indicating knowledge application effectiveness.
- Lessons-learned register fields
- Standard fields including identifier, date, phase, category, description, root cause, impact, recommendation, owner, status, and reuse reference, enabling traceability and application.
- Five Whys
- A root-cause technique that repeatedly asks why a problem occurred, typically about five times, to move from symptom to underlying cause before recording a lesson.
- Retention schedule
- A policy specifying how long each record class is kept, the legal or regulatory hold that applies, the storage format, and the authorized destruction date.
- Post-implementation review
- A review comparing actual outcomes against the business case and baseline after delivery, feeding benefits realization and improving future estimates and lessons.