By Dan Katen

A longtime employee gives notice, and at first the problem seems straightforward. The company needs to replace the position.

Then the questions begin.

Who knows the history behind that customer account? Why is one piece of equipment handled differently from the others? Which supplier can be counted on when something goes wrong after hours? Why was a certain process changed years ago, and what happened the last time someone tried to change it back?

The job can usually be filled. The experience is much harder to replace.

Small and midsize businesses are especially vulnerable to this kind of loss because they tend to run lean. One employee may have spent years working with the same customers. A technician may know a machine well enough to recognize a problem before it becomes obvious. A manager may understand the reason behind decisions that were made long before newer employees joined the company.

Most of that knowledge never appears on a balance sheet, yet the business depends on it every day.

The issue is not that companies fail to document anything. Established businesses usually have procedures, customer records, training materials, service histories and software systems. Those records matter, but they do not capture everything people learn by doing the work.

A procedure may explain how a task should be performed. It may not explain what an experienced employee notices when something does not look right.

A customer file can show years of orders and correspondence. It may not tell the next account manager that a particular customer tends to change quantities late, or that one person needs to be consulted before a decision is made.

A maintenance record tells you what was repaired. It does not always tell you why the technician knew where to look first.

That difference between recorded information and working knowledge is easy to overlook because experienced employees make difficult things look routine. They have seen the same problems enough times to recognize patterns. They know which questions to ask, which details deserve attention and which apparent problems are not problems at all.

When that person leaves, the business often discovers how much of its operating knowledge was tied to an individual.

The cost shows up in small ways before anyone recognizes the larger problem. A customer has to explain the same history again. A new employee spends hours researching something the previous employee knew immediately. A mistake is repeated because no one remembers that the company already learned that lesson five years earlier.

Individually, those problems may not look serious. Together, they create delay, rework and frustration.

Growth can make the situation worse.

As a business gets larger, responsibilities are divided among more people and more systems. That is necessary, but it also creates distance between the people doing the work today and the people who learned the lessons that shaped the business.

A process may still be followed long after everyone has forgotten why it exists. A decision made after an expensive failure can eventually become nothing more than a line in a procedure. New employees learn what the company does without necessarily understanding what happened before they arrived.

Over time, a business can accumulate more records while losing part of its memory.

The answer is not to document every conversation or turn experienced employees into full-time writers. Most small businesses do not need another layer of paperwork.

They do need to identify the knowledge they cannot afford to lose.

One useful place to start is by paying attention to where people go when something unusual happens. Who gets the call when a customer problem does not fit the normal process? Who knows what to do when equipment behaves strangely? Who remembers the history behind an old decision?

Those people are carrying knowledge that deserves attention.

Ask them what they know that is not written down. Capture the reason behind important decisions, not just the decision itself. When an unusual problem is solved, record what happened and why the solution worked. When a project goes badly, keep the lesson instead of simply closing the file and moving on.

This is just as important for business owners.

Many small and midsize companies still rely heavily on what the owner knows personally. The owner remembers why certain customers are handled differently, which suppliers have been dependable over time, what warning signs deserve attention and which opportunities are more trouble than they appear to be.

That knowledge helped build the company. If it exists only in the owner’s head, it can also limit the company.

Succession becomes harder. Growth becomes harder. Training takes longer. Selling the business can become more complicated because some of what makes the company work cannot easily be transferred to someone else.

A strong business should become more knowledgeable as it gets older, not simply older.

Every difficult project, failed decision, unusual customer problem and hard-earned solution should leave the company a little better prepared than it was before.

That only happens when the lesson stays behind.

The larger issue is easy to miss because knowledge does not look like an asset in the traditional sense. It is not parked in the yard, stored in the warehouse or listed with a dollar value on a financial statement.

But a company’s experience is still something it has spent years building.

Most owners would never knowingly throw away customer records, equipment history or financial information.

They should be just as careful with what their people have learned.

Because when an experienced employee walks out the door, the most expensive thing leaving may be what the company never thought to keep.

Original article