There is usually one person a company leans on without quite noticing. She knows which exception each client got last time, where the right template lives, and why it was once done differently from what the manual says. As long as she is there, everything runs smoothly, and no one notices how much depends on her. Then she is out for two weeks, and a perfectly ordinary task grinds to a halt, because the knowledge it needs is written down nowhere. It lived in one head.
This scene is the heart of what people call knowledge management, and most companies treat it as a tooling question. A new tool, a wiki, another shared folder. The tool is rarely the problem. Knowledge cannot be managed while you cannot see it, and it only becomes visible once it hangs on a task and on a role, not on a name. That is the first move. The second decides whether it stays visible.
Why the most valuable knowledge is invisible
The chemist and philosopher Michael Polanyi coined a line that still describes all experience-based work: we know more than we can tell. An experienced employee reads a client in the first minutes of a call and makes a decision without being able to explain exactly what tipped her off. That tacit knowledge is often the most valuable thing in the business, and for the same reason it is invisible. No one ever wrote it down, because it never felt like something you had to.
While the knowledge stays tacit, the company keeps paying for it. In Deloitte’s research on knowledge management, 29% of people said it was hard or nearly impossible to get the knowledge they need for daily work out of the company’s own systems, while only 19% said the same about getting it from a colleague. So people ask a colleague, because asking is the path with less friction, and the knowledge stays in heads that were never meant to be the filing system. It is a quiet bill, because it shows up on no balance sheet.
From the head to the task
The management researchers Ikujiro Nonaka and Hirotaka Takeuchi described, in their work on knowledge-creating companies, the decisive step: making tacit knowledge explicit. Taking what sits in one head and putting it into a form someone else can use. In practice, this mostly means changing the question. Away from “who knows this?” and toward “which task needs which knowledge?”. Once the knowledge hangs on a task rather than a person, someone else can take it over, and the business does not stall when a calendar happens to go empty.
This shift is more than a turn of phrase. Order things by people and you build dependencies. Order them by roles and tasks and you build a system that can be handed on. The person stays just as important; she simply stops carrying alone what should belong to the company.
The coat and the hook
That gets half the job done. The other half is why so many knowledge bases quietly fall silent after three months. You can make knowledge visible once and put it in a place no one goes near in daily work. Then it is invisible again, only with more effort than before.
It is like the coat when you get home. If the hook is not where your hand already goes on the way in, the coat ends up over the chair. That does not happen out of carelessness. It happens because the intended spot is the wrong one, and you can tell because the house still looks messy even though the hook exists. It is the same reason people ask a colleague instead of opening the system: they take whichever path costs less friction. If you want the coat on the hook, you put the hook where the hand already is.
For a place to keep knowledge, three things follow. The place has to sit where the work already happens, so you do not have to open a second system on the side. It has to be simple enough that writing something down costs less than asking again, because the moment asking is easier, asking wins. And it has to be able to grow and move, so that in two years you extend or migrate it, instead of throwing it away and starting over.
How to start this week
No reorganizing, no new software. Take a single task that stalls the moment a particular person is away, and make its knowledge visible:
- Name the task, not the person. Write down which recurring task it is and what knowledge it demands, so that someone else could take it over. The person’s name does not belong on that line.
- Ask three questions. How do you know it is starting? What do you need before you begin? How do you know it is finished and good? The answers are the tacit knowledge, said out loud.
- Write it at the point of reach. Put the answer exactly where the task happens day to day, not in a new folder on another drive. One line in the right place beats a whole page in the wrong one.
- Test it on a person. Let someone who does not know the task follow it alone. Where they stall, the knowledge was still in the head, and that is where you write the next line.
One task a week is enough. Within a few weeks the knowledge hangs on tasks rather than heads, and the business stops depending on individual people.
The rest is location
Knowledge that lives in one head does not really belong to the company. It is on loan, until the next holiday. It becomes visible and durable the day it hangs on a task and sits in a place the hand finds on its own. The right place is always the one the hand reaches for by itself. Everything else, sooner or later, drifts back onto the chair.
In the next part of the Clarity Playbook, we take on the next building block of clarity. Each part brings a method that builds on the one before.
One last thought, in case this reads as thankless. Writing down what only you know can feel like handing away the very thing that makes you needed. In practice it frees you. When the knowledge lives in the task rather than in your head, you stop being the person who can never fully step away, and the hours you spent being the only one who could help come back to you, for the work only you can do next.
Care for your systems, and you care for your people.
Elisa
This article is written by Elisa Winkelmann with AI assistance and under her editorial review.
Sources
- Michael Polanyi, The Tacit Dimension (1966). On “we know more than we can tell” — the foundation for why experience-based knowledge is invisible by default. (Book.)
- Ikujiro Nonaka & Hirotaka Takeuchi, The Knowledge-Creating Company (1995); see also Nonaka, “The Knowledge-Creating Company,” Harvard Business Review (1991). On making tacit knowledge explicit.
- Sandy Becker & Faris Behme, “The new organizational knowledge management,” Deloitte Insights (2021). Source of the 29% vs 19% finding.
- Galan et al., “Knowledge loss induced by organizational member turnover,” The Learning Organization, 30(2) (2023), Emerald. A peer-reviewed review of what leaves when people leave.