§ 2.3Module 2

Knowledge Management

On this page

2.3 Knowledge Management

Suggested retrieval lesson: 20–30 minutes.

Recall first

  1. Distinguish data, information, and knowledge.
  2. What is the difference between tacit and explicit knowledge?
  3. Why is a document repository alone not knowledge management?

Commit before reading.

From data to organizational knowing

A useful ladder is data → information → knowledge: data are observations; information is contextualized data; knowledge is the ability to interpret information and apply it to a task or decision. Knowledge includes experience, judgment, causal understanding, and know-how, so it cannot be reduced to files. Knowledge management (KM) is the deliberate process of creating, capturing, organizing, sharing, applying, and renewing knowledge so individuals and the organization can perform and learn better. This is the textbook exam framing in Rainer & Prince and Laudon & Laudon; the exact cycle labels vary by author.

Tacit and explicit knowledge

Good KM supports both. A searchable lesson captures explicit guidance; mentoring, communities of practice, shadowing, and after-action discussion transfer tacit judgment.

KM cycle

Use this cycle for exams, while noting that sources may name stages differently:

  1. Create/acquire: generate insight, learn from research, customers, partners, or experience.
  2. Capture: record what matters before it disappears; identify owner and context.
  3. Store/organize: classify, version, secure, and make it findable.
  4. Share/transfer: connect people to knowledge through search, training, communities, or workflow prompts.
  5. Apply: use it in a real decision or process.
  6. Evaluate/renew: test whether it worked, update outdated content, and feed lessons into new creation.

The cycle fails if incentives reward hoarding, search is poor, content is stale, access is unsafe, or workers have no time to contribute. KM therefore combines people and culture (trust, recognition, learning) with processes and technology (repositories, wikis, search, expertise directories, workflow, permissions). Technology stores and connects knowledge; it does not create willingness or judgment by itself.

Worked example: maintenance organization

A senior engineer knows that a pump’s vibration pattern predicts failure. KM begins when the team records the observation with conditions and evidence. It is reviewed, tagged to the pump model, versioned, and linked to a maintenance checklist. New technicians discuss it with the engineer during a community-of-practice session. They apply it on a live inspection; the team measures false alarms and missed failures, then updates the rule. The repository stores explicit knowledge, while mentoring transfers the tacit diagnostic skill.

Exercise — reveal after committing

A company uploads 20,000 untagged documents to a portal and calls it KM. Identify two missing cycle stages and one people problem.

Revealed answer: Capture may be present, but organization/findability, sharing, application, and renewal are missing or weak. A people problem could be lack of incentives or time, so employees do not contribute or trust the content. A portal is an enabler, not the KM cycle itself.

Exam lens

Rapid revision checklist

Key takeaways

  1. Knowledge is actionable understanding, not merely stored data.
  2. Tacit knowledge needs social transfer as well as documentation.
  3. KM is a cycle: create, capture, organize, share, apply, renew.
  4. Culture, incentives, trust, and time are as important as platforms.

Sources