The Knowledge That Only Lives in One Person's Head: How to Share It Across Your Company

Every company has at least one person everyone asks. They know why the supplier invoice has to go in before the 5th of the month, what to say on a third-round complaint, and which button you should never press in the system. None of this is written down anywhere. It lives in one head, and as long as that head shows up for work, everything runs.

The trouble doesn’t start when they quit. It starts much earlier.

Knowledge sharing: the process of turning the unspoken work experience that lives in people’s heads into a written, searchable, and transferable form, so the company doesn’t depend on a single person to keep running.

Hidden knowledge costs you money in four ways

Quitting isn’t the most expensive part. It’s just the most visible one.

1. The interruption

The person who knows everything gets asked every day. Each question pulls them out of whatever they were doing, and getting back into it takes far longer than the answer itself. The company pays for the expert’s time, and then pays again for the work they can’t get done because of it.

2. The waiting

When the answer sits with one person and that person is on holiday, off sick, or in a meeting, the work stops. It doesn’t just slow down, it halts, because the colleague doesn’t dare take the next step.

3. Fifteen different solutions

If there’s no written way to do something, everyone invents their own version. Five colleagues close a case five different ways, all five are almost right, and the mistakes pile up invisibly until someone runs into them at a customer.

4. Onboarding that never ends

A new person arrives and you sit the expert down next to them. Now two people’s time is gone at once, and with the next hire the whole thing starts over from scratch, with the same sentences.

Why doesn’t anyone just write it down?

It’s not laziness. There are usually three reasons, and all three are real.

There’s no time. The person who knows the most is also the most overloaded. Documentation always gets pushed off whatever day it is right now.

It’s harder to write than to do. You don’t even think of the things you do every day as knowledge. They happen automatically, without thinking, and that’s exactly why they’re so hard to put into words.

There’s nowhere to put it. If the answer is “write it in a Word file and drop it on the drive,” the material ends up among the other thousand files and no one ever finds it again. Anyone who has been through that once won’t even start a second time.

These three reasons together explain why asking your team to “document more” solves nothing. There’s nothing wrong with the intention, the problem is the circumstances.

What to do instead

Don’t aim for all the knowledge

Writing down every bit of company knowledge is a hopeless task, and that’s exactly why it never gets started. Instead, start with the pain: collect the questions most often asked of the same person. A week of paying attention is enough. The list builds itself, and it’s usually shorter than you’d think.

Don’t start in writing

Your expert can explain in ten minutes something they couldn’t write down in two hours. Use that: record them explaining or showing it on screen, and make the wording the second step.

In Corganize, this step is built into the product. From a silent screen recording, the AI writes a step-by-step process description, and from an audio recording it creates a transcript that turns into a lesson. In our own measurement, a 42-second screen recording became a 10-step description for roughly the equivalent of a few cents. The point isn’t the price, it’s that the barrier disappears: the expert doesn’t have to write, they just have to talk.

Put it where people will look for it

A description is only worth something if people find it. That means having it all in one place, searchable, and having the search answer the question the colleague actually asks. Not by file name, but by content.

Check whether they actually read it

Sending the link doesn’t mean anyone knows it. If the description goes into an onboarding plan, you can see who is where in it, and with a closing set of questions you can also check that they didn’t just scroll through it.

Where to start tomorrow morning

You don’t need to launch a project for this. Four steps are enough for the first round.

Step	What you do	How long
1. Question log	For a week, write down what the expert gets asked	a few minutes a day
2. Top 5	Pick the five most frequent questions	half an hour
3. Recording	The expert explains or shows all five	5-10 minutes each
4. Rollout	The descriptions become material and the team gets it	one afternoon

A week later you already see the effect where it matters: the expert gets asked the same thing fewer times.

How to keep it from going stale

Give every piece of material an owner. Not so there’s someone to blame, but so there’s someone to turn to when it goes out of date.

Update it where the flaw shows up. If someone gets stuck following a description, that’s not their fault, it’s the description’s fault. That’s the best moment to fix it.

Don’t let it become a rulebook. The goal of knowledge sharing isn’t to have a folder you can point to, it’s to have the work run without the expert. If no one uses the material, the problem isn’t the people, it’s that the material doesn’t answer the question they’re actually asking.

The bottom line

Knowledge in people’s heads isn’t dangerous because the owner might one day leave. It’s dangerous because you pay for it every single day: in interruptions, in waiting, in fifteen different solutions, and in onboarding that starts over and over.

You don’t have to write down everything. It’s enough to start with the five questions most often asked of the same person.

Frequently asked questions

Where do I start with knowledge sharing?

Not with all your company knowledge. For a week, write down what the same person gets asked most, and start with the five most frequent questions.

Why isn't it enough to just ask my team to document more?

Because it's not a matter of intention. The person who knows the most is the most overloaded, daily routines are hard to put into words, and if the description lands on a shared drive, no one ever finds it. You have to change the circumstances, not people's attitude.

How long does the first round take?

A week of a question log, half an hour of selection, five to ten minutes of recording per task, and one afternoon for the rollout.