How to Build a Knowledge Inventory and Ownership Model: A Step-by-Step Guide
Organisations that decide to "get our knowledge in order" often start by documenting everything, or by moving everything into a new tool. Both approaches tend to produce a large pile of content that nobody owns and few people trust.
A better start is a scoped knowledge inventory and an ownership model. Lakhlani International's Knowledge Maturity Management page lists these among the things you get: a scoped inventory of priority knowledge domains, a proposed ownership and review model for knowledge assets, documentation and retrieval priorities, and a phased improvement roadmap. This article shows how to build them yourself, step by step, and what to watch for.
What an inventory is, and is not
A knowledge inventory is a structured list of the knowledge your business depends on, where it lives, who holds it and how well it is maintained. It is not a copy of all your documents. Think of it as a register of knowledge assets, in the way a finance team keeps a register of physical assets.
The word "scoped" on the capability page matters. The aim is to cover priority domains first, not the whole organisation.
Step 1: Identify critical workflows and knowledge risks
Begin with the work, not the documents. List the workflows that matter most to revenue, customers, compliance and continuity, such as order handling, quoting, onboarding, quality checks, month-end close or incident response. For each, ask what knowledge it needs and what would happen if the knowledge were unavailable.
This follows the first step of the page's method. Our article on reducing key-person dependency gives a simple risk-ranking method that fits here.
Step 2: Map current repositories, ownership and maintenance
For each priority workflow, record where its knowledge currently lives and how it is kept. Use a table like this, one row per knowledge asset.
Inventory fields
- Knowledge domain. The workflow or topic, for example customer onboarding.
- Asset. The specific item: procedure, template, decision record, recording.
- Why it matters. The business consequence if it is unavailable or wrong.
- Holders. The people who know it, including those who hold it only in their heads.
- Current location. Where it lives today, or "none".
- Format. Written, video, system configuration, tacit only.
- Quality. Current, partly outdated, outdated or missing.
- Owner. Who is responsible today, if anyone.
- Last reviewed. The date, or "unknown".
- Access. Who can see and edit it.
Expect gaps, especially in the Owner and Last reviewed columns. Those gaps are findings. The page names exactly this mapping of repositories, ownership and maintenance practices as step two.
Step 3: Prioritise by business criticality
Score each asset on criticality and on risk of loss, and sort. A simple rule of thumb is to work first on assets that are high in business criticality and held by few people, or missing entirely.
Set a limit. A first phase of five to ten assets is usually more productive than fifty. The capability page recommends prioritising knowledge assets by business criticality, and its roadmap is phased for this reason.
Step 4: Define governance, review cycles and access principles
This is where most knowledge efforts succeed or fail, because it determines whether content stays alive.
Ownership roles
A light model is enough for most small and mid-sized organisations.
- →Executive sponsor. Makes the effort a priority, resolves conflicts, protects time.
- →Domain steward. Oversees a domain, for example customer operations, and keeps the inventory current.
- →Asset owner. Accountable for the accuracy of specific items.
- →Contributors. Add and improve content, report errors.
- →Users. Use the content and give feedback.
One person can hold more than one role in a small company. The principle is that each asset has a named person who answers for it.
Review cycles
Agree when content will be checked.
- →Time-based: a review date, such as every six or twelve months, matched to how fast the content changes.
- →Event-based: review when something changes, such as a new regulation, system upgrade, product launch or incident.
- →Use-based: flag items that are never opened and decide whether to update or retire them.
Outdated content should be visibly marked or removed, because stale procedures damage trust in everything else.
Access principles
Decide in advance who can see and edit what. A common starting point:
- →Open by default for general operating knowledge, to encourage use.
- →Restricted for commercially sensitive, confidential or personal data.
- →Controlled editing for procedures where errors have serious consequences.
If content includes personal data about customers or employees, take advice on data protection obligations, including India's Digital Personal Data Protection regime where it applies.
The international standard ISO 30401:2018 organises knowledge management as a management system, and its table of contents includes scope, culture, objectives and management review. The contents page alone illustrates the point: knowledge management needs ongoing management attention, not a one-off project.
Step 5: Choose documentation and retrieval priorities
Decide two things for each priority asset.
- →How will it be captured? Written procedure, recorded walkthrough, decision record, template or shadowing arrangement. Match the method to the type of knowledge, as covered in our article on key-person dependency.
- →How will people find it? A named location, consistent titles, links from the places people already work, and a short guide on where to look.
Retrieval is often the weaker half. A well-written procedure that nobody can find does not help. The page lists retrieval priorities alongside documentation priorities for this reason.
Step 6: Measure adoption and revise
The final step on the capability page is to measure adoption and revise the system based on actual use. Useful measures depend on your goals. Examples:
Measures that reflect use
- →Is the content used? Views or searches for priority assets, and the share of staff using them.
- →Is it findable? The share of test searches that find the right item, and the time taken to find it.
- →Is it current? The share of priority assets reviewed on schedule.
- →Does it help? Time for new joiners to reach agreed competence, reduction in repeat questions to experts, handover quality.
- →Are people contributing? The number of new or improved items by owners and contributors.
Record baselines before you begin. Without a starting point you cannot tell whether things improved. Be wary of vanity measures such as the total number of documents, which can rise while usefulness falls.
A phased roadmap
The capability page promises a phased improvement roadmap. A generic shape, to adapt:
Phases, focus and output
- Scope and inventory. Priority workflows, risks, current state. Output: scoped inventory with risk ranking.
- Foundations. Owners, review rules, access principles, a clear location. Output: ownership model and conventions.
- Capture and retrieval. Document or transfer the top assets, and fix findability. Output: priority assets live and owned.
- Adoption and review. Measure use, collect feedback, retire stale content. Output: revised priorities and next phase.
This is a template, not Lakhlani International's proprietary plan. Durations depend on scope and capacity.
Common mistakes
- →Trying to inventory everything at once.
- →Skipping the owner column, then wondering why content decays.
- →Treating the inventory as a one-off exercise rather than a living register.
- →Choosing tools before requirements. Our article on whether you need a new platform covers that decision.
- →Ignoring tacit knowledge that cannot be written down.
- →Measuring volume instead of use.
An illustrative scenario (hypothetical)
Consider a hypothetical 80-person manufacturer preparing for rapid growth. The operations director identifies six critical workflows, from supplier onboarding to quality escalation, and builds an inventory with ten priority assets. The inventory shows that four have no owner, three exist only in one supervisor's notes and two are outdated.
Owners are named and review dates set. The supervisor records a walkthrough of his notes with a colleague, and a new joiner tests the supplier onboarding guide on a real case. After two months, the team looks at which items are being opened and which questions still reach the supervisor, and chooses the next five assets from the results. This scenario is invented for illustration and does not describe any client.
Next step
Start the inventory with one workflow and five assets. Fill in every column, including the uncomfortable ones, and name an owner for each.
If you would like help scoping a Knowledge Maturity Management assessment, the capability page sets out what the work covers. Related reading sits in the Business & Technology section of the Knowledge Hub, including the guides to key-person dependency and to choosing a platform.
Knowledge Maturity Management
A scoped inventory of priority knowledge domains, an ownership and review model, and a phased roadmap.
Explore the capabilityReducing key-person dependency
How to rank knowledge risk and pick the right capture method for each kind of knowledge.
Read the key-person guideDo you need a new platform?
Define requirements before you buy: content, findability, access, ownership, cost and exit.
Read the platform decision guideFrequently asked questions
What is a knowledge inventory?
It is a structured register of the knowledge a business depends on, recording where it lives, who holds it, its quality, who owns it and how often it is reviewed. It is scoped to priority domains rather than covering everything.
How is a knowledge inventory different from a document library?
A document library stores files. An inventory describes knowledge assets, including those that exist only in people's heads, and records ownership, quality and risk so you can decide what to capture and maintain.
Who should own knowledge assets?
The person closest to the work who can keep the content accurate, usually a team lead or subject expert, with a domain steward overseeing consistency and an executive sponsor protecting time.
How often should knowledge be reviewed?
It depends on how fast the content changes. Common patterns are time-based reviews, such as every six or twelve months, plus event-based reviews when processes, systems or regulations change.
How do we measure whether the knowledge system is working?
Track use, findability, currency and effect, for example views of priority assets, search success, share of reviews on time, time for new joiners to reach competence and repeat questions to experts. Record baselines first.
How many assets should we start with?
Few. Five to ten priority assets in a first phase is usually more productive than a broad sweep. Expand after you have measured use and refined the model.
References
- →ISO 30401:2018, Knowledge management systems — Requirements (catalogue record and table of contents preview). https://genorma.com/en/standards/iso-30401-2018
- →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