SOPX logo SOPX

People & Knowledge

Knowledge Management

Also known as: KM, Organizational Knowledge

The discipline of capturing, organising, and sharing what an organisation knows so that the right information reaches the right people at the right time.

Read this article summarized with
ChatGPT Claude Perplexity Gemini Grok

Knowledge management (KM) emerged from a 1987 McKinsey internal study and went public at an Ernst & Young conference in Boston in 1993. [2] Tom Davenport offered the classic one-line definition the following year: 'Knowledge Management is the process of capturing, distributing, and effectively using knowledge.' [2] A few years later, the Gartner Group framed it more broadly as 'a discipline that promotes an integrated approach to identifying, capturing, evaluating, retrieving, and sharing all of an enterprise's information assets.' [2] APQC narrows the same idea down to its purpose: KM is 'the application of a structured process to help information and knowledge flow to the right people at the right time.' [3] IBM puts it more operationally: 'the process of identifying, organizing, storing and disseminating information within an organization.' [4] In practice, KM treats know-how as an asset: pulling it out of the people who have it, structuring it so others can find it, and keeping it current. [1] [4] In operations, that mostly means converting tacit, hands-on know-how into explicit, documented procedures, and making those procedures accessible at the moment of need (the workstation, the field, the shop floor) rather than buried in a folder. [1]

Key characteristics

  • Distinguishes between tacit knowledge (in heads) and explicit knowledge (written or recorded), and works to convert one into the other. [1]
  • Captures knowledge from people through interviews, recordings, templates, and lessons-learned databases. [1] [2]
  • Organises and retrieves knowledge through search, taxonomy, expertise location, and point-of-use access. [2]
  • Keeps knowledge current with named owners, review cycles, and feedback loops.
  • Is judged on whether people use the knowledge, not on how much content exists. [1]

Example

Building a knowledge base for a 60-person field service team

A field service company employs 60 technicians who repair commercial refrigeration units. Senior techs know how to diagnose 200+ failure modes from sound, smell, and gauge readings. The company starts a KM program: each tech records a 2-minute video any time they encounter a tricky failure, narrating the diagnosis. Within a year, the library has 400 short procedures, tagged by equipment model and symptom. New techs in the field scan a QR code on the unit, type a symptom, and get a curated set of likely fixes. First-visit resolution rates climb 20 points.

How SOPX handles this

Most KM programs fail because writing is slow and search is bad. SOPX shortcuts both. Field workers and operators record short videos of what they did and why, the AI converts each recording into a structured, searchable procedure with steps and screenshots, and the whole library is organised, version-controlled, and translatable into 50+ languages. The bottleneck stops being 'we should write this down someday' and becomes 'pull out your phone and record it now'.

Related use case: Knowledge Retention →

Frequently asked questions

What is the difference between knowledge management and document management?
Document management is about controlling files (versions, permissions, retention). Knowledge management is about controlling what people know and how that gets shared. A document management system can be part of a KM strategy, but having a tidy folder structure does not mean the right knowledge is reaching the right people. IBM puts the payoff plainly: companies with a KM strategy 'achieve business outcomes more quickly' because organisational learning and collaboration speed up decision-making, and KM streamlines processes like training and onboarding. [4] KM is judged on whether work gets done better.
What is the difference between tacit and explicit knowledge?
Tacit knowledge is internalised, experience-based understanding people may not consciously recognise, which makes it difficult to articulate or transfer. [1] Explicit knowledge is consciously held information that can be communicated through documents, systems, or formal instruction. [1] Some KM practitioners draw a finer line: truly tacit knowledge (getting up on water skis, recognising a face) overlaps very little with what KM systems actually capture. Most of what KM converts is implicit knowledge, things that could have been written down but no one has bothered to. [2] The hard part is converting it without losing the nuance. Video captures more of that implicit detail than text, because it shows hand movements, tool angles, and tone of voice that words struggle to convey.
What are the components of a KM system?
KMWorld lists four core operational components. Content management makes the organisation's information findable through dashboards, portals, and enterprise search. Expertise location identifies and locates people inside the company who hold specific know-how (in the early days this was called the 'Yellow Pages'). Lessons learned databases capture how-to knowledge that would normally go unwritten, often borrowed from the military's after-action report tradition. Communities of practice are groups that come together, in person or virtually, to share problems, best practices, and lessons learned. [2] A complete KM program usually has all four, even if it does not use those exact labels.
How do you start a knowledge management program?
Start narrow. Pick one team and one painful gap (for example, 'we lose 4 hours of production every time the Friday machinist is off'). Capture the knowledge that closes that gap. Measure the outcome (downtime, defect rate, onboarding time). Use the result to fund the next round. APQC argues you also need a documented strategy and roadmap behind that work: 'organizations without a documented KM strategy and roadmap will struggle to achieve their goals.' [3] And resist the urge to lead with software. APQC puts it bluntly: 'expecting new technology to change employee behavior is like expecting a new car to make you a better driver.' [3] Programs that try to document everything, or buy a tool and hope, fail. Programs that solve one expensive problem at a time, with a clear strategy behind them, compound.
Who owns knowledge management in a company?
It depends on the size. In small teams, operations leaders own it directly. In mid-size companies, training managers or quality leaders typically run it. In large enterprises, there is often a dedicated KM function, sometimes led by a Chief Knowledge Officer (a role first formalised at Skandia in the 1990s). [1] APQC reports that around half of surveyed KM programs run as a centralised team with consolidated oversight and a defined strategy. [3] The principle is constant: ownership belongs close to where the knowledge is used, not in a centralised function disconnected from the floor.
How do you keep a knowledge base from going stale?
Three habits. First, every document has a named owner and a review date. Second, anyone can flag a document as out of date with one click, and that flag goes to the owner. Third, leadership treats updating documentation as part of the job, not as overhead. Without those, libraries decay quietly until people stop trusting them, and then no one uses them.

Sources

Statements above draw on the references below. Numbers in the text link to the matching entry.

  1. [1]
    Knowledge management
    Wikipedia · Accessed 2026-04-28
  2. [2]
    What is KM? Knowledge Management Explained
    KMWorld · Accessed 2026-04-28
  3. [3]
    What Is Knowledge Management?
    APQC · Accessed 2026-04-28
  4. [4]
    What is knowledge management?
    IBM · Accessed 2026-04-28

Related terms

Tags

leadership documentation training onboarding

Last reviewed: 2026-04-28

Stop writing SOPs. Start recording them.

Film any process on your phone. SOPX turns it into a structured, editable SOP in under 10 minutes. No writing required.

Try SOPX free Book a 15-min demo