Knowledge transfer before experience retires

Why knowledge transfer so often fails in SMEs

In many SMEs, a few long-serving employees carry knowledge that is written down nowhere in full: why a machine is set up the way it is, what a customer was promised ten years ago, which supplier delivers reliably on rush orders. When a retirement is announced, there are often only a few months left. They go into handover documents that hardly anyone finds again.

The material usually exists. Notes, minutes, mail, offers and project folders sit scattered across drives, SharePoint and mailboxes. What is missing is a form the successor can use without first knowing where everything is filed.

How yeos captures experience

yeos reads documents where they already live: SharePoint, Teams and OneDrive stay in sync, and files such as PDF, Word or Excel can be uploaded directly. Add the material that was never filed anywhere: notes, voice notes and recorded conversations with the person who is leaving. Audio files such as MP3 or M4A are transcribed and become searchable like any other document.

The knowledge goes into a workspace for the team or role taking over, such as "Maintenance plant 2" or "Customers region east". That way the successor and the team see exactly the documents they need.

What the yeos Brain keeps

While reading, the yeos Brain records what the documents decided, promised or left open, each with its document and date. "That is how Mr Meier always did it" becomes a decision with a reason and a source.

Open questions stay visible as knowledge gaps. In the last months before a retirement this list is especially valuable: it shows what to ask the person while they are still there.

How the successor works with it

The successor asks in plain language, at the desk or on the move by voice: "Why does line 3 run at reduced speed at night?" "What did we promise the municipality for the 2019 renovation?" "Who do I call when the press controller fails?" yeos answers with the passages from notes, minutes and conversations and names the source. If two documents disagree, yeos shows both.

Approach: start early, add as you go

Starting six to twelve months before the departure pays off most. Connect the person’s folders and notes first. Then use the open knowledge gaps as a guide for short conversations, recorded as a voice note or captured in minutes. Every answer goes back into yeos and closes a gap.

If the transfer starts later, it is still worth it: existing folders connect in a few clicks, and the conversations can focus on what is written down nowhere.

Limits: what yeos does not take over

yeos does not replace the conversation. Knowledge that is never spoken or written down cannot be found by any AI. yeos shows where something is missing; a person has to fill the gap. Spot-check scanned handwritten notes after they are imported.

Private mail and personal data do not belong in a shared workspace. Agree with the person beforehand which folders and mailboxes are handed over. Access follows the organization and workspaces, not the permissions of individual files in the source system. yeos is also not a document management system and does not meet retention obligations.