The problem usually appears on an ordinary Tuesday.
A customer needs a copy of an agreement. Someone in operations is not sure how to handle an exception. A new starter cannot tell which form to use. In many SMEs, the answer sits with one experienced person, often a manager, team lead or long-serving colleague. When that person is on holiday, in a meeting or simply working on something else, everything takes longer.
That is not a criticism of the person who knows the answer. It is a sign that the business has allowed too much everyday knowledge to sit in one place.
When routine questions all land on the same desk
When the same colleague gets asked the same practical questions all day, the cost is spread quietly across the business.
People pause their work while they wait for a reply. Customer responses take longer than planned. Managers get drawn into questions that do not need their judgement. Staff either wait or make their best guess, which can lead to different answers being given to different people.
The result is not always dramatic. It is often a steady drag on pace and consistency. Teams can be in the same office, on the same call and using the same systems, yet still be blocked because the useful answer lives with one person.
That is why this is not only a holiday problem. It is an everyday operating issue.
Why a shared folder helps, but does not solve it
Many businesses respond by creating a shared drive, a policy folder or a set of process documents. That is a sensible start. It is not the whole answer.
Documents can be scattered across different locations. Files may have similar names or old versions that still look official. A procedure might exist, but the person looking for it may not know which document is current or how it applies to a real situation.
Some of the most useful knowledge has never been written down. Experienced people often rely on context, judgement and memory. They know which exception is acceptable, which detail matters most and where the process usually flexes in practice.
That is why the issue should not be framed as a failure by the people who have become indispensable. In most cases, they became indispensable because the business did not build a better way to share what they know.
What an internal knowledge assistant can do
An internal knowledge assistant can help staff find approved business information more quickly.
In plain English, that means people can ask a question in natural language and get an answer based on the company’s own documents, rather than searching through folders or waiting for one person to reply. A useful assistant should also show the source it used, so the user can check the answer instead of taking it on trust.
That can be helpful when someone needs to:
- find the current procedure for a customer handover
- check the right onboarding step for a new starter
- confirm an agreed customer requirement in an internal document
- look up a documented approval limit for a routine request
Used well, this can reduce interruptions and make it easier for teams to work with more confidence. It also gives the business a practical way to use existing information more effectively.
At Hally AI, that is the kind of problem we help SMEs tackle. We look for places where AI can create measurable value, then design practical solutions around the systems and information the business already has. For an internal knowledge assistant, that means starting with the questions people actually ask, the documents that already exist and the controls needed to keep the output reliable.
Where the limits have to stay visible
An internal knowledge assistant should support decision-making. It should not replace it.
If the assistant finds a documented approval limit, that does not mean it should approve an exception. It can surface the rule. A person still decides whether the exception is sensible.
The same applies when information is missing or conflicting. A good assistant should not guess. If there is no clear source, or if two documents say different things, it should direct the user to a person who can check.
Access permissions matter too. Not every employee should see every document, and not every file should be treated as current just because it exists somewhere in the business. The quality of the assistant depends on what it can access, how well that information is maintained and whether the answers are tested properly.
That is why this is as much an operating discipline as a technology choice. The assistant can make information easier to find, but it still needs human oversight, source control and a sensible scope.
A practical example: order handovers in a small operations team
Imagine a small operations team where the manager is the person everyone asks about order handovers.
If someone is unsure whether an order can move to the next stage, they ask the manager. If a customer wants a change, they ask the manager. If a delivery case feels unusual, they ask the manager again. The manager is helpful, but the interruptions build up and routine decisions keep getting pulled back to one person.
Now imagine the team records the questions that keep coming back to that manager. They check the answers, write down the current guidance and agree which cases are standard and which should still be escalated.
A simple internal knowledge assistant is then built around that approved material. A team member can ask, “What is the handover step for a delayed order?” or “Where is the agreed customer requirement recorded?” and receive a response with a link to the source document.
The unusual case still goes to the manager. But the routine questions no longer need to.
That is the point. The assistant does not remove the value of experienced people. It cuts the number of times they are interrupted for work that could have been answered from agreed information.
A manageable way to start
The safest way to begin is with one team and one narrow area of the business.
Start by recording the questions that keep going to the same person. That shows where the bottleneck really is. Then choose one topic area, such as order processing, onboarding or customer service handovers, and capture the answers in a form that can be checked and maintained.
A practical starting sequence looks like this:
- Pick one team and one type of question that comes up repeatedly.
- Agree who will own the content and keep it current.
- Check each answer against the existing source material.
- Test the guidance with a small group before wider use.
- Review whether people are finding answers faster, repeating fewer questions and getting more consistent responses.
Those checks matter because the aim is not to add another tool for the sake of it. The aim is to reduce dependence on individual availability, free up experienced people for work that genuinely needs their judgement and make reliable information easier to access.
Shared knowledge keeps the business moving
When one person knows everything, the business looks more stable than it really is.
The answer is not to strip value away from experienced people. It is to make their knowledge easier for others to use, while keeping judgement where it belongs. Shared knowledge, supported by a carefully scoped internal knowledge assistant, can reduce routine interruptions, speed up access to approved information and help teams work more independently.
For SMEs, that often means less waiting, fewer repeat questions and more time for the work that actually needs experienced oversight.
