MELLORCATalk to Mellorca
Patterns

Knowledge, Documentation & Institutional Memory

When One Employee Becomes the Company’s Search Engine

Colleagues ask the same long-serving person where things are because it is faster than searching. Here is how that dependency forms and how to move retrieval into a shared structure.

Mellorca Patterns2026-10-09

Observable condition

A technician in a Durban distribution business needs to know which version of the returns procedure applies to a customer on a special contract. He does not search the shared drive. He walks to Thandi's desk, because Thandi has been with the company for eleven years and always knows. Within a day, Thandi has been asked where a supplier agreement is saved, who approved a discount, why a customer was credited last March, and which spreadsheet is the real one. Her own work gets done after hours.

Every business has someone like this. They are the person new staff are told to ask, the person managers message when a client calls with a question about history, and the person whose leave is quietly dreaded. Their value is real. The trouble is that the business has begun to use one person's memory as its search function, and her memory is the only index it has.

An illustrative example: a Johannesburg accounting practice of forty staff stores documents across a file server, a cloud folder, email attachments and two practice-management tools. Nobody can agree on where a signed engagement letter lives. The office manager is the only one who can reliably find it in under five minutes, so every partner and every junior asks her instead of looking.

Realisation

The realisation is that the interruptions are not a personality quirk or a sign that colleagues are lazy. They are a rational response to a system that does not work. People ask Thandi because asking is faster and more reliable than searching, and each time they ask, the pressure to fix the search disappears. The more helpful she is, the less likely the underlying problem is ever addressed.

The arrangement also hides its own cost. Her time looks like normal work, since she is busy and useful, but a large share of it is retrieval for other people. The business pays a senior salary for a human directory.

Realisation prompt: if your most knowledgeable colleague were unreachable for two weeks, which questions would stall, and how many of them are about where something is rather than what to decide?

Identification

This is a pattern of person-dependent retrieval. The visible symptom is one individual who fields a constant stream of "where is" and "who knows" questions. The common assumption is that she is simply good at her job and the business is lucky to have her. The structural cause is that information is spread across folders, inboxes, chat threads and systems without a shared structure, naming habit or owner, so only someone who watched it accumulate can navigate it.

The published Pattern why customer service becomes a human search engine covers the frontline version of this, and the business process that only works because someone remembers covers process steps held in memory. This Pattern is about the company-wide version, where one person becomes the access route to documents, history and decisions.

Diagnosis

  • Information is stored by habit, not by rule. Files are saved under the name and folder the author found convenient. Over a few years, the same kind of document ends up in six places.
  • Context is in email and chat. The reason a decision was made sits in a thread that only the people copied can find. Atlassian's guidance on knowledge sharing points out that useful answers are lost when they remain in private conversations rather than a shared, findable place.
  • Search tools cannot find what is not described. Documents with names such as "final v3 revised" give the software nothing to work with, so even a good search function returns noise.
  • There is no owner for the answers. Nobody is responsible for keeping the pricing rules, supplier terms or procedures current, so asking a person is the only way to know what is still true.
  • Being asked is rewarded. The person who knows is thanked, gains influence and may not wish to give it up. Without anyone intending it, there is little incentive to change.
  • Tenure substitutes for structure. The longer someone has been there, the more they know, and the more the business leans on them instead of writing it down.

Commercial impact

The commercial value at stake is productivity, continuity, response time and the capacity of the knowledgeable person to do the work they were hired for.

Take a conservative case. If Thandi spends ninety minutes a day answering retrieval questions and each question also interrupts someone else for ten minutes, a team of ten may lose several hours a week. At an average cost of R300 an hour, that is a figure in the tens of thousands of rand a year, before counting delays to customers while an answer is tracked down. The Impact page on the same internal questions asked repeatedly examines this cost more closely, and employees searching for files covers the searching side.

The continuity risk is larger than the daily cost. IBM describes knowledge management as the practice of capturing and distributing an organisation's knowledge so that it is not lost when people move on. When the business relies on one person's memory, resignation, illness or even an extended holiday can freeze decisions. If the person leaves for a competitor, what walks out is also an index of the company's history.

There is a people cost too. The person at the centre often cannot take leave without being called, cannot finish their own projects, and may be passed over for growth because they are too useful where they are. Resentment and burnout follow.

Common misidentification

Managers often respond by asking the knowledgeable person to "document everything". It rarely works. It adds a large task to an already overloaded schedule, produces a long document that is out of date within months, and does not change how people look for things. The result is a manual that nobody opens.

The second response is to buy a company-wide search tool or an AI assistant. A search tool can only surface what is stored in a way it can understand, and it will confidently return outdated versions. Retrieval technology works best on content that has an owner, a current status and a sensible name, which is exactly what is missing.

Possibility

In a better state, the common questions have a known home. There is one agreed place for each type of document, a simple naming convention, a short list of owners for the areas people ask about, and a place where answers to repeated questions are saved after they are given. New staff are shown where to look first. The knowledgeable person is consulted for judgement, exceptions and context, not for location. When she is away, the business slows slightly instead of stopping.

Intervention

  1. Log the questions for two weeks. Ask the person at the centre to note each question with a tick mark or a one-line description. The pattern emerges fast: perhaps twenty questions account for most of the volume.
  2. Answer each in writing once. For the top questions, write the answer and the location in a shared page or index, and name an owner who keeps it current.
  3. Fix the filing structure for the highest-traffic areas. Choose one location for contracts, one for supplier terms, one for procedures. Retire duplicates rather than add a new folder.
  4. Redirect, kindly. When someone asks, answer and then point to where it now lives. The aim is to make the shared source the quicker option, not to refuse help.
  5. Capture decisions where they are made. A one-line note of what was decided and why, saved in the record it affects, saves the next person from asking. The Insight how to move operational knowledge out of people's heads offers practical methods.
  6. Measure the interruptions again after a month. A drop in questions is the evidence that the structure is working.

Diagnostic questions

  • Who do new employees say they are told to ask when they cannot find something?
  • How many places could a signed customer agreement be saved?
  • What would stall if your most knowledgeable colleague left tomorrow?
  • Do repeated questions get answered in a shared place, or only in a chat?
  • Does anyone own the accuracy of pricing, terms and procedures?

Bottom line

When one employee becomes the company's search engine, the business is paying a senior person to compensate for information it has not organised. Capturing the most frequent answers, giving them a home and an owner, and keeping the expert for judgement rather than retrieval protects both the continuity of the business and the person it has come to depend on.

Sources and further reading

Related Mellorca reading

Article summaryColleagues ask the same long-serving person where things are because it is faster than searching. Here is how that dependency forms and how to move retrieval into a shared structure.
Explore our solutionsStart a conversation