The colleague who knows where everything is

Every small team I have ever worked on had one. The person who knows where everything is. Which folder the old contract lives in, why the client insists on being invoiced on the ninth and not the first, what the login is for the account nobody remembers setting up. They are wonderful. They are also the biggest risk on your team, and almost nobody treats them that way.

The good version first

Let me be fair to them, because they earn it. This person is usually generous, quick and genuinely helpful. Ask them anything and the answer comes back in seconds. They save the team hours every week. On a crew of five or six people, having one human search engine feels like a gift, and for a long time it is one.

The trouble is that the gift and the risk are the same thing. Every question that goes to them, and only to them, is a small deposit of knowledge into an account with a single keyholder. The team feels fast. What it actually is, is fragile.

The team feels fast. What it actually is, is fragile.

The day they are away

You find out the truth on an ordinary Tuesday when that person is off sick, or on leave, or, worst of all, has just handed in their notice. Suddenly the simplest task takes half a day. Nobody can find the file. Nobody knows why the client wants the ninth. The work does not stop because it is hard. It stops because the map was in one person's head and the head is not in the room.

I have watched capable teams lose a week to the departure of someone who was not even senior, simply because they were the one who knew where things were. That is not a people problem. It is a design problem, and you designed it, quietly, every time you let a question go to one person because it was faster.

What to do about it, without a big project

You do not need a new system or a fashionable piece of software. You need a habit, and the habit is small enough to start on Monday.

When someone answers one of those questions, the answer gets written down somewhere the whole team can reach. Not a beautiful document. A plain page, a shared note, a pinned message, anything searchable. The rule is simple: if a person had to ask, the answer was missing, so now we write it down once so nobody has to ask again. The person who knew stays helpful. They just stop being the only copy.

The second habit is even smaller. Every so often, on purpose, route a question away from the obvious expert. Ask the newer person to find the answer using what has been written down. If they can, your map is working. If they cannot, you have found a gap while it is cheap to fix, rather than in the week someone leaves.

The quiet part

There is a reason teams resist this, and it is worth naming. Being the person who knows where everything is feels good. It is a kind of security. Writing it all down can feel like giving that away. A decent manager gets ahead of this by making the sharing itself the thing that is valued, so the expert is praised not for holding the knowledge but for spreading it. You want the most generous person on the team to be your best documented one, and you want them to feel bigger for it, not smaller.

None of this is dramatic. That is the point. The failures that sink small teams are rarely dramatic. They are the slow, invisible kind, the single points of knowledge you never counted because everything was working. Count them now, while the person who knows is still smiling and still in the room.