# When Operational Knowledge Lives in One Person’s Head
A customer asks how a difficult job was handled last time. An unusual supplier issue appears. A new employee needs to know which steps are normally skipped for a particular client.
Everyone turns to the same person.
That person may be an operations manager, senior technician, office administrator or business owner. They know the exceptions, workarounds and unwritten rules that keep the business moving. While this arrangement can work for years, it creates operational risk when that employee is unavailable, leaves the business or simply becomes overloaded with questions.
The problem is not that the employee has valuable knowledge. The problem is that the business has no dependable way to share, maintain and use it.
The hidden cost of informal knowledge
Critical knowledge is often spread across memory, old emails, personal notes, chat messages and documents that few people know exist. New staff learn by asking questions, watching someone else or repeating mistakes.
This creates several business problems:
- routine decisions are escalated unnecessarily;
- work is performed differently by different employees;
- customers receive inconsistent answers;
- urgent tasks slow down when the experienced employee is absent;
- support issues are solved repeatedly instead of permanently;
- management cannot easily tell whether a process is being followed.
The risk is particularly high in businesses with exceptions. A standard operating procedure may explain the normal job, but real operations also include special pricing, unusual site conditions, preferred communication methods, client-specific requirements and common failure scenarios.
Capturing only the “happy path” is not enough.
Start with the questions staff actually ask
A knowledge project should not begin with an instruction to “document everything”. That approach usually produces a large folder of documents that becomes difficult to search and maintain.
A more useful starting point is to identify recurring operational questions, such as:
- What should happen when a customer changes the scope after approval?
- Which checks are required before a job is closed?
- Who can approve an exception?
- What information should be collected before escalating a support issue?
- What has caused this type of problem before?
- When should staff stop troubleshooting and contact a supplier?
These questions reveal where informal knowledge is affecting speed, quality or risk.
The goal is not to replace judgement with a rigid script. It is to provide enough context for staff to make consistent decisions and know when human escalation is appropriate.
A practical digital knowledge workflow
For a small business, the solution may be a searchable internal knowledge area connected to the systems staff already use. Depending on the process, it could include:
- A structured article or procedure
Each entry explains the situation, recommended action, owner and last review date.
- Decision guidance
Simple conditions can direct staff to the next step: resolve, request more information, seek approval or escalate.
- Links to relevant records
A procedure can point to the related customer, product, job, application screen or supplier process rather than duplicating information.
- An escalation path
When the documented guidance does not apply, staff should know who to contact and what evidence to provide.
- A review process
Employees can flag outdated guidance, suggest changes or record a newly discovered exception.
This could be implemented within an existing business platform, a secure internal website or a tailored application. The important design decision is not the brand of tool. It is whether the information is easy to find at the moment it is needed.
Record decisions, not just instructions
Many knowledge bases fail because they document activities without explaining the reasoning behind them.
“Check the account before confirming the booking” is less useful than:
Check the account for outstanding issues because confirmation should be delayed if the customer has an unresolved service dispute. Escalate exceptions to the operations manager.
The second version helps a new employee understand the purpose of the step and recognise when the normal process does not apply.
For recurring incidents, a support record can also capture:
- the symptoms observed;
- the likely cause;
- the checks already completed;
- the safe workaround;
- the permanent fix or next escalation;
- the date the guidance should be reviewed.
This reduces repeated investigation and gives application support a clearer path from incident response to root-cause improvement.
Keep ownership explicit
Knowledge becomes unreliable when nobody owns it. Every important entry should have a responsible role, even if several people contribute.
Ownership includes:
- approving changes;
- reviewing content after a process change;
- removing obsolete instructions;
- checking that linked systems or screens still exist;
- deciding whether a new exception deserves a documented procedure.
Version history is also valuable. Staff should be able to see what changed and when, particularly when the guidance affects customer commitments, pricing, compliance activities or production systems.
Do not turn every decision into a form
Documentation can create its own burden when every unusual event requires a long record. A sensible design distinguishes between:
- common procedures that deserve clear instructions;
- significant exceptions that need an approval or audit trail;
- minor judgement calls that do not need additional administration.
The objective is operational resilience, not paperwork.
A useful test is whether the digital workflow helps a capable employee answer a question faster and with more confidence. If it adds several screens without improving the decision, the process needs simplifying.
The business lesson
If one employee is the only person who knows how to handle a recurring situation, the business has an undocumented dependency.
The answer is not always a large knowledge-management project. It may be a focused set of searchable procedures, decision guides, incident records and review responsibilities built around the questions staff already ask.
The most valuable knowledge is captured close to the work, maintained by its owners and connected to the systems where decisions are made.
Melbourne Digital Solutions can help SMEs assess where operational knowledge is becoming a risk, then design a practical digital workflow, internal tool or support process around it.
