What happens to what we know when someone leaves?

The short answer

Someone gives notice, perhaps near the end of the year when people think about a change. You are glad for them and a little worried for the work. They know which customers are touchy. They know what was promised last month and what is half done.

What happens to that knowledge depends on where it lived. If it lived in their head, their notebook or their phone, most of it goes when they do. If it was written into the business’s own records as the work happened, it stays.

You cannot make a person remember less. You can make sure the business remembers more.

What actually walks out of the door

It is rarely the big things. A handover document can cover the big things. It is the small facts that nobody thought to write down.

The customer who prefers a call to a message. The promise made on a Tuesday, to be kept by the end of the month. The reason a job was priced the way it was. The answer to a question that comes up every few weeks, which only one person ever gave.

None of it was secret. It was simply never put anywhere that someone else could look. The person leaving did not hide it. Nobody asked for it while they were still there, because it was always a few steps away, in the head of someone who could be asked.

Why a handover meeting does not fix it

The usual remedy is a handover in the last week. It helps, but it has a built-in weakness. You ask someone to recall, in an hour or two, a year of small decisions. They will remember the large ones and the recent ones. They will forget what they stopped noticing long ago.

It also happens at the worst time. The person is already half gone, and the people receiving the handover do not yet know which questions matter. Those come up in the third week, when the person is no longer there to answer.

Knowledge is kept better in small amounts, written down close to the moment, than in one large amount written down at the end.

What changes when the work is noted as it happens

This is where Felesh fits, and it is a modest fit. Felesh keeps what is done on Felesh. So the habit that matters is a small one, repeated.

After a customer conversation they type one sentence, and Felesh drafts the note and the promise for their yes. That is all it asks of the person doing the work: a sentence, a quick read, a yes.

Now suppose that person leaves. The notes are there. The promises are there, with their dates. The next steps are there. They were not collected in a panic during the last week. They built up as the work went on.

How the next person finds out

A record is only useful if someone can get at it without knowing where to look. This is the other half of the problem. A pile of notes is better than nothing, but it still depends on knowing what to search for.

You can ask Felesh questions in your own words about your work, and it answers from your own records. The person taking over a customer might ask what was promised to them, or what is still open, or what happened at the last conversation. The answer comes from what was written down, not from a guess.

So the successor does not need to know the old filing habits. They do not have to find the right folder or the right person to ring. They ask the question they would have asked the colleague.

What about the customers who write in?

Some of what a business knows is not about one person at all. It is the answers to the questions customers keep asking.

Customer messages from the website chat, Instagram, WhatsApp and Telegram arrive in one inbox. Felesh answers from what you taught it: documents you uploaded and instructions you wrote. Those belong to the business. They stay when a person goes.

What it cannot answer goes to “Needs you”, with the reason it could not answer. Nobody is notified. Whoever picks up the queue sees the message and the reason beside it. When a person joins a conversation, Felesh stays quiet.

This matters when someone leaves, because the way you answer is no longer carried by one person’s habits. It sits in the documents and instructions, where the next person can read it, change it and correct it.

What Felesh cannot know

It is worth being plain about the limit. Felesh knows what is done on Felesh. It knows the files you import and what you upload or teach it. It does not read mail or drives, and it does not connect to other tools.

So if a leaver kept every promise in a private notebook and never typed a word of it anywhere, Felesh does not know it. If the history sits in their inbox, it stays in their inbox. Nothing reaches into those places and pulls it out.

There is one useful door. If the person kept a list of contacts and companies in a spreadsheet, you can bring it in from one Excel or CSV file through a reviewed import. You see the column mapping and the rows before anything is saved. That gets the names into the business. It does not bring the history behind them.

This is why the habit matters more than the tool. The records are as good as what was put in.

What to do before and after someone leaves

Before they go, ask for the loose ends, not a lecture. Which promises are still open? Which customers are waiting for something? Have them type each one up as a sentence about what happened, and review the drafts together. A short sitting now is worth more than a long meeting.

Look at the customers, not at the person. A customer who has gone quiet is worth a question. Ask what was last said, what was promised and what the next step was. The records answer without anyone having to be chased.

After they go, let the next person ask. They work from the notes, the dated promises and the answers they get when they put a question in their own words. Where there is a gap, they write it down, so the next departure leaves a smaller one.

Nothing here makes the business immune to losing a good person. Their judgement and their relationships go with them. But the facts of the work do not have to.

Where to start

You do not need to wait for someone to hand in their notice. After your next conversation, type one sentence about what happened, and review the draft. Later, ask Felesh a question in your own words, and see whether the answer comes from what your business has written down.