The Person Is the Silo, and Docs Did Not Fix It

We keep talking about knowledge silos like they are folders. Fix the folders, we say. Write better docs, put everything in one place. Years of that later, the silos are still here. The reason is simple: the silo was never the folder. The silo is the person.

What a silo really is

A knowledge silo is any place where knowing lives in one head and cannot get out without that head being available. On a remote team, this is the default, not the exception. The person who set up the pipeline knows why it is built that way. Nobody else does, and the only interface to that knowledge is a message and a wait.

Why docs did not fix it

Docs were supposed to be the cure. Write it down once, and anyone can read it. It sounds right. It mostly failed, for reasons everyone has lived:

• Docs go stale the moment the work moves, and nobody is paid to keep them true.
• They are written for the room that already understood, so they skip the context a stranger needs.
• The important part, the "why we did it this way," rarely gets written at all. It stays a story the person tells when asked.

So the doc exists, and people still ping the person. Because the doc answers what, and the question is usually why, or "is this still true?"

Why we keep blaming the folder

Blaming the folder is comfortable. A folder is a thing you can buy a tool for. A person is not. So teams reach for another doc site, another wiki, another place to file, and feel like they did something. The files pile up. The person is still the one everyone pings. The tool changed. The silo did not. Each new place adds one more thing to keep updated, and one more place the answer might be hiding, which is the opposite of what anyone wanted.

Remote makes the person-silo worse

In an office, you could catch someone at their desk. Remote removes the hallway. Now the only way through the silo is a message across time zones, and the answer arrives hours later, if the person is even working when you are stuck. The knowledge did not become more locked. The lock just got slower to open.

The test that shows the silo

Here is a clean test. Pick any important thing your team depends on. Now imagine the one person who knows it best is unreachable for a week. If the team slows down, stalls, or waits, that thing is a silo, and the person is the wall. A doc only breaks the silo if a teammate can get the real answer from it without the person. Most cannot. That is how you know the doc did not fix it.

What actually breaks a silo

A silo breaks when the knowledge can answer a question while the person is away. Not a static page someone has to read and interpret. A record that responds to the actual question, in the person's own words, with a source you can check. The bar is not "we wrote it down." The bar is "a teammate got what they needed without waiting for a human."

This is the whole point of StandIn. The person who knows writes one short brief at the end of the day about their own work. While they are off, it answers their teammates' questions from what they wrote, with a source under each answer, and when the answer is not there, it says so instead of guessing. The person stays a person. Their knowledge stops being a wall.