What Is Knowledge Maturity Management? A Practical Guide for SMBs and Growing Teams
Every business runs on knowledge: how to quote a difficult job, which supplier to call when a shipment stalls, why a process has an odd extra step, what a particular customer will never accept. In many small and growing companies, most of that knowledge lives in a handful of people. It works well until one of them goes on leave, resigns or simply becomes too busy to answer the fifth question of the day.
Knowledge maturity management is about making that dependence less fragile. This guide explains what the term means, what it covers, what the research and standards say, and how to approach it without buying software first.
A working definition
Lakhlani International frames knowledge maturity management around systemising and maturing an organisation's knowledge capital. The practical aim, in its words, is to make important knowledge easier to find, maintain, transfer and apply in everyday work. Its FAQ describes it as a structured approach to understanding how an organisation captures, governs, maintains and applies its institutional knowledge.
Three ideas sit in that description.
- →Knowledge capital. What your people know, and what your documents, systems and routines record, is an asset that can be built up or run down.
- →Maturity. Organisations handle knowledge with different degrees of discipline, from ad hoc habits to managed, measured practice. "Maturity" describes that progression.
- →Everyday use. Knowledge that is captured but never applied has little value. The test is whether it helps someone do their work.
Tacit and explicit knowledge
A distinction made famous by Ikujiro Nonaka and Hirotaka Takeuchi in "The Knowledge-Creating Company" explains much of the difficulty.
- →Explicit knowledge can be written down and shared: procedures, specifications, checklists, templates.
- →Tacit knowledge lives in experience and judgement: how an experienced technician hears that a machine is about to fail, or how a sales lead senses a deal is slipping.
Nonaka and Takeuchi describe four ways knowledge moves between these forms: socialisation (tacit to tacit, through shared experience), externalisation (tacit to explicit, by putting it into words or models), combination (explicit to explicit, by combining documents) and internalisation (explicit to tacit, by learning by doing). A practical consequence is that a folder of documents does not transfer know-how by itself. People also need to work alongside each other, discuss cases and apply what they read. And some tacit knowledge cannot be fully captured at all, so expectations should be realistic.
What it covers in practice
The capability page lists four problems it addresses.
- Critical operating knowledge exists only in individuals' heads.
- Documentation is fragmented, outdated or difficult to find.
- Onboarding and handovers depend on informal explanations.
- Teams repeat work because decisions and lessons are not captured.
And it describes five parts of the approach.
- Identify critical workflows and knowledge risks.
- Map current repositories, ownership and maintenance practices.
- Prioritise knowledge assets by business criticality.
- Define governance, review cycles and access principles.
- Measure adoption and revise the system based on actual use.
The order is deliberate. It begins with what matters most and what is at risk, not with a tool.
Is there a standard?
Yes. ISO 30401:2018, "Knowledge management systems — Requirements", sets requirements and guidelines for establishing, implementing, maintaining, reviewing and improving a management system for knowledge management. Its requirements apply to any organisation, regardless of type or size. It is a management-system standard, in the family of standards that include quality management, and an organisation does not need to seek certification to borrow its thinking.
The standard itself is paywalled; this description is based on official catalogue summaries. If you plan to rely on it formally, obtain a copy. The last article in this series looks at how it relates to other frameworks.
Why it matters: what the research suggests
A widely cited estimate from the McKinsey Global Institute, in its 2012 report "The social economy", is that knowledge-intensive "interaction workers" spend nearly 20% of their working time looking for internal information or tracking down colleagues who can help. A critical analysis of that figure notes that it combines earlier IDC estimates with McKinsey's own data and applies to a specific group of workers. So treat it as an indication of scale, not a measurement of your business.
There is little recent, independent research on what knowledge loss costs small businesses in India. That is a gap, and it means the benefit should be assessed in your own terms: how long does onboarding take, how often do handovers fail, how many hours go into answering the same questions?
What it is not
- →It is not only software. The capability page says a new platform is not necessarily required. A platform decision should follow requirements, not precede them.
- →It is not a one-off documentation project. The page notes that effectiveness depends on participation, ownership and ongoing maintenance.
- →It is not a guarantee. A knowledge system can help document and transfer critical know-how, but it cannot remove every dependency on individuals.
An illustrative scenario (hypothetical)
Consider a hypothetical 60-person distribution company where one operations manager knows how every large customer's orders are handled, including exceptions that are not written anywhere. She is planning a long leave. The owner's first instinct is to buy a documentation tool.
Instead, the company lists the workflows that would hurt most if she were unavailable, ranks them by business criticality and picks the top three. For each, she and a colleague walk through real cases, a short procedure is written and the colleague shadows her on the next live exceptions. An owner is named for each document, with a review date. The tool question is deferred until the team sees what they actually need. This scenario is invented for illustration and does not describe any client.
Where to start
Ask yourself three questions. Which three processes or relationships would cause the most damage if one particular person disappeared tomorrow? Where do people repeatedly ask the same questions? And which documents do people actively avoid because they are out of date?
If you would like to scope an assessment, the Knowledge Maturity Management capability sets out how the work runs. The firm's work with smaller organisations is outlined on the SMB enterprises page, and the last article in this series explains how to assess your own maturity level.
Knowledge Maturity Management
A scoped inventory of priority knowledge domains, an ownership and review model, and a phased improvement roadmap.
Explore the capabilityAssessing your maturity level
Compare APQC, ISO 30401 and a simple self-assessment you can run with your own leadership team.
Read the maturity models guideSMB enterprises
How Lakhlani International works with small and growing businesses.
Explore SMB enterprisesFrequently asked questions
What is knowledge maturity management?
It is a structured approach to understanding and improving how an organisation captures, governs, maintains and applies its institutional knowledge, so that important knowledge is easier to find, maintain, transfer and use in daily work.
What is the difference between tacit and explicit knowledge?
Explicit knowledge can be written down, such as procedures and templates. Tacit knowledge lives in experience and judgement and is harder to express. Both matter, and documents alone rarely transfer the tacit kind.
Does a small business need knowledge management?
Often yes, especially if it depends on a few key people. The approach can be small and focused on the most critical workflows rather than a company-wide programme.
Do we need new software to start?
Not necessarily. Start by assessing the problem, your current tools and how people actually behave. Choose a platform only once you know your requirements.
Is there an international standard for knowledge management?
Yes. ISO 30401:2018 sets requirements for knowledge management systems and applies to organisations of any type or size. You can use its ideas without seeking certification.
Can a knowledge system remove dependence on key employees?
It can reduce it by documenting and transferring critical know-how, but results depend on participation, ownership and ongoing maintenance. Some tacit knowledge cannot be fully captured.
References
- →ISO 30401:2018, Knowledge management systems — Requirements (catalogue record). https://genorma.com/en/standards/iso-30401-2018
- →McKinsey Global Institute. The social economy: Unlocking value and productivity through social technologies (2012). https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy
- →Nonaka, I. The Knowledge-Creating Company. Harvard Business Review (1991). https://hbr.org/2007/07/the-knowledge-creating-company
- →Lakhlani International. Knowledge Maturity Management capability page. https://lakhlaniinternational.com/capabilities/knowledge-maturity-management