Knowledge Silos Are Killing Your Business: When Key People Leave, What Goes With Them?

Every growing Malaysian SME reaches a point where the team knows more than the systems do.

Your operations manager knows every vendor's quirks. Your senior salesperson remembers every client's preferences. Your accountant knows the workaround for that one process that never quite works right. This is not a failure, it is the natural result of experienced people doing their jobs well.

The trouble starts when that knowledge needs to move: during a handover, when someone is on leave, when the team grows, or when a key person walks out the door. If it lives only in people's heads, every one of those moments becomes a scramble.

That is the knowledge silo problem. It is not about whether your team is good. They clearly are. It is about whether the business can reach what they know when they are not in the room.

What a Knowledge Silo Looks Like

Silos are rarely obvious. They build up quietly, one capable person at a time. In practice they look like this:

Pricing locked in one person's head. "Ask Ahmad, he knows the margins for that line." Then Ahmad is on medical leave and a prospect needs a quotation today.

Supplier terms in a personal phone. Your procurement person has years of vendor relationships. The contact numbers, negotiated rates, and payment terms exist only in their personal WhatsApp.

Processes only one person can run. "Siti handles month-end." "Raj does the stock reconciliation." Those are not job descriptions, they are single points of failure.

Strip away the examples and every silo is one of three kinds. You do not need to study them, just recognise which one you are looking at:

• Process knowledge is the "how we do it" know-how: the sequence, the exceptions, the workarounds. Lose it and quality drops the day the person leaves. Highest risk.
• Relationship knowledge is the "who to call and what to say": vendor contacts, client preferences, the person at the bank who actually gets things done. Relationships take months to rebuild. Medium-high risk.
• System knowledge is the "how to make the tech work": the logins, the custom Excel macro that builds the report, the manual step that makes two tools talk. We have seen a business unable to raise invoices because the person who built the template left. Critical if undocumented.

The Procurement Chaos Connection

Silos hit hardest in procurement, and it follows a pattern we see again and again.

One person manages every vendor. They know who gives 60-day terms, who needs cash on delivery, who has the best price on item A but terrible quality on item B. It works beautifully, right up until it does not. They go on leave, or they leave for good, and suddenly purchase orders go to the wrong vendors, prices creep up because nobody negotiates the discounts, and deliveries slip because nobody knows the lead times.

The relationship still matters. What needs to change is where the data behind it lives. Vendor terms, negotiated prices, past performance, preferred items: a connected system holds all of it, so the knowledge belongs to the business, not to one person's memory.

Making That Knowledge Transferable

The fix is not to replace people with systems. Good people are the point. The fix is to make what they know transferable, so the business still benefits when they are busy, on leave, or gone.

It comes down to recording decisions against the thing they affect. A client approves a scope change? That belongs on the order or the project, not in a chat someone has to scroll back through later. A vendor confirms a special rate? That belongs on the vendor record. Communication can happen anywhere. The decision just needs to be findable by whoever needs it next.

Do that consistently and a new hire is productive in days, not weeks. They look up a vendor's terms instead of asking around. They see a client's full history instead of leaning on tribal knowledge. They follow a documented process instead of guessing.

Three Steps to Start This Week

You do not need an ERP to begin. You need to start making the implicit explicit.

1. List your single points of failure

Write down every task only one person can do. Be honest, the list is longer than you expect. Those are your highest-risk silos.

2. Document the top three

Take the three most critical and have the person who owns each write down the steps. Not a manual, just a checklist: "Step 1, open this. Step 2, check that. Step 3, if this happens, do that." The exercise usually reveals the process is more involved than anyone realised, which is exactly why it needs writing down.

3. Move critical data off personal devices

Any client contact, vendor term, price, or approval that lives only on a personal phone or in a personal email needs to be copied into a shared system. Even a shared spreadsheet beats a personal WhatsApp chat.

These are starting points, not the destination. The real solution is a connected system where knowledge gets captured as part of daily work, not as one more thing people have to remember.

How Exposed Is Your Business?

Take 30 seconds to audit your key-person dependencies:

How transferable is your business knowledge? Find out in 2 minutes with our Readiness Check.