Introduction to Knowledge Management: KM Essentials
Based on APQC's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Treat knowledge as information in action; prioritize findability and usability over storing content.
Briefing
Knowledge management is best understood as a way to turn organizational know-how into usable value—by making knowledge flow reliably between people and content, not by “managing” knowledge as a static asset. The core message is simple: knowledge equals information in action, so a lesson stored in a repository that nobody can find or use creates little value. That framing matters because it shifts KM from collecting documents to designing the processes, roles, and systems that help people apply expertise when they need it.
APQC breaks knowledge into two practical types: explicit knowledge (easy to document, replicate, and store in repositories) and tacit knowledge (harder to capture because it lives in experience, judgment, and decision-making). Most organizations can already handle explicit content to some degree, but tacit expertise—often the “80%” people care about most—requires deliberate knowledge sharing. The two categories also overlap: a written process can be more powerful when paired with context from the person who used it with real clients.
The need for KM comes from business pressure and opportunity. Finding information takes time, and teams may act without the right knowledge, hurting efficiency and cost control. KM also helps prevent knowledge loss when people leave through retirement, job changes, or project turnover. Beyond risk reduction, KM can improve agility and enable competitive differentiation by letting organizations work faster, reuse best practices, and operate effectively across global value chains.
APQC emphasizes that knowledge management is not the same as knowledge management software. KM is a systematic approach to enable knowledge and information to grow, flow, and create value—through both people and content. A widely used guiding idea is that knowledge is “sticky” without processes and systems: people may not hoard knowledge intentionally, but they hoard time and energy, don’t know what to share, or don’t know where it belongs. Social tools can help collaboration, yet deep tacit knowledge still needs structured extraction and transfer.
To organize KM work, APQC points to a portfolio of approaches rather than a single tactic. Common approaches cluster into three buckets: communities and collaboration; knowledge retention and transfer (e.g., interviews, mentoring, lessons learned, codifying expertise into tools and content); and content management for explicit knowledge, including documents and increasingly multimedia and video. Another framework places approaches along two dimensions: the level of human interaction (high-touch to low-touch) and the depth of tacit knowledge transfer (explicit to deep expertise). This yields four categories—self-service, process-based approaches, communities of practice, and transfer of best practice—each suited to different knowledge needs and resource constraints.
Successful KM also depends on roles and enablers. APQC highlights four knowledge management roles: a KM leader to align KM with business strategy; a KM specialist to design, implement, maintain, and measure KM approaches; marketing/communications to drive adoption and sustain engagement; and an analyst to connect technology needs with business requirements. Business sponsorship is repeatedly flagged as a predictor of effectiveness and budget confidence. Finally, APQC urges a balanced, holistic strategy built around people, process, content, and technology—while starting with specific business problems, asking for concrete participation, and measuring value through both activity and impact metrics.
Cornell Notes
Knowledge management (KM) turns information into usable value by ensuring knowledge flows between people and content. APQC distinguishes explicit knowledge (documentable and easier to store) from tacit knowledge (experience-based expertise that requires sharing and context). KM becomes necessary because organizations face business pressures—slow information retrieval, knowledge loss from turnover, and the need for reuse, learning, and innovation—and because modern tools make knowledge flow more feasible. Effective KM uses a portfolio of approaches (self-service, process-based transfer, communities of practice, and best-practice transfer) matched to the type of knowledge and the required level of human interaction. Success depends on roles (leadership, specialists, communications, and technology/analyst support), business sponsorship, and a strategy that balances people, process, content, and technology.
Why does APQC define knowledge as “information in action,” and what problem does that definition solve?
What’s the practical difference between explicit and tacit knowledge, and why does it change what KM must do?
What business drivers make KM a “must,” not a “nice to have”?
How do APQC’s four KM approaches (self-service, process-based, communities of practice, best-practice transfer) differ?
Why does APQC insist KM needs more than tools—especially for tacit knowledge?
Which roles and enablers most influence KM adoption and effectiveness?
Review Questions
- How should an organization decide which KM approach (self-service, process-based, communities of practice, or best-practice transfer) fits a specific knowledge problem?
- In what ways can explicit knowledge management still fail if tacit context isn’t addressed?
- What metrics would you use to demonstrate KM value beyond participation activity, and why?
Key Points
- 1
Treat knowledge as information in action; prioritize findability and usability over storing content.
- 2
Separate explicit and tacit knowledge to determine whether KM needs repositories alone or structured sharing and mentoring.
- 3
Use business imperatives—efficiency, cost avoidance, knowledge retention, learning acceleration, and innovation—to justify KM investment.
- 4
Build a portfolio of KM approaches and match them to the required level of human interaction and depth of tacit transfer.
- 5
Define knowledge management as managing knowledge flow through processes, enablers, and roles—not as managing knowledge itself or buying software.
- 6
Assign clear KM roles (leader, specialist, communications, analyst) and secure business sponsorship to sustain adoption and funding confidence.
- 7
Balance people, process, content, and technology; people and process barriers often determine whether KM sticks long term.