There are two kinds of knowledge in a business. One is written down somewhere: prices, processes, manuals. The other sits in people's heads and never gets written down, because nobody clocks it as knowledge at all. It just feels like being good at your job.
Explicit and tacit, the difference
Explicit knowledge is easy to pass on. It's in the price list, the procedure, the quality manual. Tacit knowledge is the opposite: experience someone has but finds hard to explain. Why a quote for this particular client gets worked out one way and not another. Which supplier actually delivers when things get tight, and which one just promises. Which machine's odd noise means it's about to fail.
The tricky part: whoever has this knowledge treats it as obvious. Which is exactly why nobody writes it down. You don't document what feels trivial to you. Until the person leaves and it turns out it was the opposite of trivial.
Why it's so expensive
Tacit knowledge is expensive because it's uninsured. It's in no file, so it can't be backed up, handed over, or replaced. When the colleague who's been there for twenty years retires, the client history she carried in her head goes with her. When the workshop manager hands in his notice, the hand movements nobody wrote a manual for disappear too. The business keeps running, just slower, more error-prone, and nobody can quite say why.
Hard to put a number on, easy to feel straight away. The new hire needs three months to work out what the old one knew in three minutes. That's the cost. It just never shows up on an invoice.
How to get it out of people's heads
Tacit knowledge doesn't become explicit through some big documentation project. Those projects fail because nobody knows where to start, and because writing things down in the abstract goes nowhere. The practical route runs the other way: start with the questions, not the answers.
With Rinqo it works like this: you upload what already exists, your website, process descriptions, the onboarding PDF. Then the team puts real, everyday questions to the personal agent. Every question without a good answer marks a gap in the documented knowledge, a piece of tacit knowledge still sitting in someone's head. The person who has it writes half a page on it, and the gap closes. Not as one big project, but piece by piece, following the questions that actually come up.
That's how knowledge moves out of people's heads and into a base that answers questions, with a citation attached. The workshop manager still retires eventually. His knowledge stays. That's the difference between a business whose value hangs on individual people, and one that owns the knowledge itself.
