Knowledge concentration risk: when your company depends on what one person knows

Why does this matter more for SMEs and family businesses?

Large companies spread expertise across teams, rotate roles and survive individual departures. An SME rarely can. One person often carries thirty years of decisions: which client needs what, which machine fails how, why a supplier was dropped in 2009 and should stay dropped. That depth is the company's real edge — and its single point of failure.

Family businesses add a second layer: the knowledge holder is often also the owner, and the transfer moment coincides with succession. Two hard transitions land on the same person at the same time.

Who holds the risk?

The risk concentrates in a handful of recurring profiles: the retiring founder who built every process, the senior engineer who designed the installed base, the plant manager who keeps operations coordinated, the salesperson who owns the client relationships, the technician who can diagnose anything by sound, the R&D specialist who remembers every failed experiment, and the operations manager who holds the informal web together. Each role holds a different kind of knowledge — and each fails differently when it leaves.

When does it become acute?

Concentration risk is chronic; certain moments make it acute. Retirement on the horizon. A succession or sale being prepared, where buyers price key-person dependency into the deal. A sudden departure or long illness, where there is no runway at all. A merger, where the people who know how things really work are the first to feel redundant. The common pattern: the time available for transfer is always shorter than the time transfer needs.

Why doesn't documentation solve it?

Writing things down captures procedures, not judgment. SOPs record what to do in the situations someone thought to describe. They don't record how your expert weighs a trade-off, reads a client, or recognizes a failure he has seen twice in a career. That knowledge is tacit: it shows up in conversation and decisions, not in documents. A documentation project also freezes at the moment of writing, while the knowledge keeps evolving.

A five-question self-check

Answer these honestly for your own company:

• Is there a question only one person in the company can answer — and does the team ask it weekly?
• If that person were unreachable for three months starting tomorrow, which decisions would stall?
• Does anyone under 45 understand why your core processes are designed the way they are?
• Would a buyer doing due diligence flag a key-person dependency?
• Is that person's departure date closer than the time a full handover would take?

Two or more uncomfortable answers means the risk is real and already priced into your company's future — by banks, buyers and your own succession timeline.

How MentX addresses it

MentX is a personality-aware knowledge base. It captures the knowledge of a company's key person — from meetings and a guided intake track — into a living, temporal knowledge graph with full source attribution. Instead of a one-off documentation push, capture runs continuously: Connect ingests the meetings your expert is already in, Deepen adds a guided intake track, and Converse makes the knowledge usable through DigiME, the digital knowledge copy your team can ask questions. Every answer carries its sources, so the knowledge stays checkable rather than becoming folklore.