Observable condition
The business has a shared drive, a cloud folder structure and perhaps an intranet. Thousands of files are stored there: policies, contracts, procedures, meeting notes, price lists, old proposals. Everything, in theory, is kept. And yet the same questions keep arriving by message. Which version of the supplier agreement applies? What did we promise this client in the last renewal? How do we handle a returned item that was bought on account?
People know the answer exists somewhere. They search, find four near-identical files and give up. They ask the colleague who has been there longest. The documents are stored, but the knowledge is not available.
An illustrative example: a Cape Town accounting practice moved all of its working papers and client correspondence to a cloud drive three years ago. It is proud that nothing is lost. But when a junior staff member needs to know how the practice handles a late VAT submission for a client with a provisional tax arrangement, she finds a policy from 2019, a draft update, a template and a long email thread. She cannot tell which is current, so she asks a partner.
Realisation
The realisation is that storing documents and managing knowledge are different jobs. Storage answers the question "is it kept?". Knowledge management answers the question "can the right person find the right answer, in a form they can trust and use, at the moment they need it?". A business can excel at the first and fail at the second.
IBM describes knowledge management as the process of creating, sharing, using and managing an organisation's knowledge and information, which includes capturing what people know and making it usable, not merely keeping files. Atlassian's description of a knowledge base makes a similar distinction between a pile of content and a curated, searchable source of answers. The common thread is curation: someone decides what is current, what is authoritative and how it is described.
Realisation prompt: pick the last three questions a colleague asked you that were answered somewhere in your files. How long did it take them to find out the answer was there, and how did they decide it was correct?
Identification
This is a pattern of storage mistaken for knowledge. The visible symptom is a large archive and a steady flow of repeat questions. The common assumption is that staff do not read the documentation or that the search tool is poor. The structural cause is that nothing in the arrangement distinguishes current from obsolete, authoritative from draft, or one topic from another, so searching returns volume rather than answers.
The Pattern why can nobody find the document they know exists describes the finding problem. This Pattern goes one step further: even when the document is found, the reader still has to decide whether to trust it.
Diagnosis
- There is no concept of "current". Old versions, drafts and finals sit in the same folder with names like "final_v3_revised". Readers must guess.
- Nobody owns each topic. A file has an author but not an owner who is responsible for keeping the subject accurate. When a rule changes, no one is tasked with updating the page.
- Structure follows who saved it, not what it is about. Folders are named for people or projects, so someone looking for a topic has to know who wrote about it.
- Documents record events rather than answer questions. A meeting minute notes that a decision was taken, but a person needing to apply it must read the whole discussion to find out what the decision was.
- Tacit knowledge is not captured. The judgement calls, exceptions and reasons that experienced staff apply are not in the files at all. The Pattern when business knowledge lives in inbox history shows where much of it ends up instead.
- Nobody reviews. Pages are never retired. The archive only ever grows, which makes every search noisier.
Commercial impact
The commercial value at stake is staff productivity, consistency of service, risk control and the ability to train and delegate.
The direct cost is search time and interruption. When staff cannot trust the archive, they ask people, and each question costs two people's attention. The Pattern why teams keep asking the same internal questions describes how that accumulates into a daily tax on the most knowledgeable staff.
The second cost is inconsistency. If two people answer the same customer question using two different versions of a policy, the customer receives two different answers. In regulated work, such as anything touching POPIA, tax or labour law, acting on an outdated procedure is a compliance risk rather than a mere inconvenience.
The third cost is dependency. The business becomes reliant on those who remember what is true, which makes holidays, resignations and growth more painful. The fourth is wasted effort: staff recreate documents that already exist because they cannot find or trust the earlier ones, adding more near-duplicates to the pile.
Common misidentification
The typical response is to buy better search or a larger storage plan. Better search can help people find a file faster, but if five similar files exist and none is marked authoritative, faster search simply delivers the confusion sooner. More storage makes the archive larger, not clearer.
Another response is a one-off clean-up project. A tidy folder structure is satisfying and improves things for a few months, but without owners and a review routine, the same drift returns. A third response is to tell staff to "read the policy". That assumes there is one policy to read.
Possibility
In a better state, the business separates its working knowledge from its archive. The working layer is small and curated: each page answers a defined question, carries a named owner and a review date, and clearly replaces its predecessors. The archive remains for records and history, but nobody is expected to search it for the answer to a live question.
Staff then trust the working layer because it is visibly maintained. New joiners learn from it, and experienced staff stop being the search engine. The Insight how to move operational knowledge out of people's heads and the Insight why documentation is part of the business system, not an add-on explain the principle.
Intervention
- List the repeat questions. For two weeks, note every question that colleagues ask each other that a document should have answered. Rank them by frequency.
- Write answer pages for the top ten. Each page should address one question in plain language, state the rule, give an example and link to the source document if one exists.
- Assign an owner and a review date to each page. The owner is the person accountable for accuracy, not necessarily the one who writes it. A page with no owner is not published.
- Mark status clearly. Use simple labels such as current, draft and retired, and move retired material into an archive area away from live searches.
- Capture the judgement, not just the rule. For each topic, record the common exceptions and who decides them.
- Review on a schedule. Set a quarterly check where owners confirm or update their pages. Track the number of repeat questions as a simple measure of whether it is working.
Diagnostic questions
- For your five most common operating questions, is there a single page that gives the current answer?
- Does each page have a named owner and a date by which it will next be checked?
- Can a new employee tell, without asking, which version of a policy applies?
- How many of last month's internal questions were answered by a person rather than by a document?
- When did you last retire a document?
Bottom line
A large archive is a record of what the business has done, not a guide to how it works. Knowledge management adds the missing layer: curated answers, named owners and visible status. When that layer exists, the documents the business already holds start to do their job, and the people who used to act as its search engine get their time back.
Sources and further reading
- What Is Knowledge Management? - IBM (last verified 10 October 2026)
- Knowledge Management in ITSM: Process & Benefits - Atlassian (last verified 10 October 2026)
- Knowledge Base Guide: Examples, Templates & Best Practices (last verified 10 October 2026)
- How to Ace Internal documentation - The Workstream (last verified 10 October 2026)
Related Mellorca reading
- When New Employees Spend Their First Week Chasing Basics
- When One Employee Becomes the Company’s Search Engine
- When Sales Data Is Complete but the Pipeline Is Still Unreliable