The two-week problem

Every small business has a person like this. Ask where a job stands, what a client prefers, or why one supplier gets the call instead of another, and the answer comes from the same desk every time. Nobody planned it that way. It happened one question at a time, over years, until the business quietly organized itself around what that person remembers.

The trouble shows up the day they are out. A vacation, a sick week, or just a busy morning when three people need an answer and the one who has it is in a meeting. Work does not stop, but it slows to the speed of finding them.

That is not really a staffing problem. It is a knowledge problem wearing a staffing costume.

What is actually in their head

If you have a manual, it covers the process: the steps, who signs off, which form to use. What it misses is the part nobody wrote down, because it never felt like a rule while it was being learned. Things like which supplier says two days and means four, what a longtime client expects without being told, or why you stopped quoting a certain kind of job the old way. That is judgment, not procedure, and today it lives in exactly one place.

None of it is a secret. Nobody is hoarding it on purpose. It is scattered across a hundred small decisions, none of which felt worth writing down on its own.

Why the big document never works

The instinct is to sit that person down for a week and have them write everything out. It almost never survives contact with the calendar, for three reasons.

It takes time nobody has, so it gets pushed to "next month" and stays there
It goes stale fast. A document is a snapshot, and the business keeps moving the day after it is finished
Nobody opens a fifty-page file when they have a question right now. They walk over and ask, because that is still faster

Writing it down and making it usable are two different problems. The second one is the one that actually matters, and it changes how you should even start.

Capture it as it happens, not all at once

The fix is not a project with a deadline. It is a habit, and it starts the next time someone asks a question that only one person in the building can answer.

Write the answer down once
The moment someone asks and gets a real answer, that answer gets captured in a couple of sentences, in plain words, while it is still fresh. No separate meeting, no big write-up later. The question itself is the trigger.
Put it where the question gets asked
A shared folder nobody opens might as well not exist. The answer needs to live in the chat where people already ask, or in whatever drafts replies for the team, so an AI assistant loaded with your business can find it and hand it back in seconds.
Let it get corrected, not just repeated
The next few times that question comes up, the answer is already sitting there. If it is outdated or slightly wrong, whoever notices fixes it on the spot. That is what keeps the knowledge useful instead of slowly going stale, the way the old binder did.

Where you put it decides everything

A correct answer filed where nobody looks does the same job as no answer at all. Same content, one folder over, and the whole approach works or quietly fails.

The other half: the questions that repeat

Some knowledge lives in one head. A different kind lives in your inbox and your phone, in the same handful of questions that show up again and again in slightly different words. If you have never counted a week of these, it is worth doing once: for five working days, log every question that comes in, in your own words, and sort it at the end instead of as you go.

Most small businesses find the same shape when they do this: a short list of questions accounts for most of what comes in, and the honest answers to them are usually simple. They have just never been written down properly, or said the same way twice.

Once you have those answers, the same rule from before applies. They only help if they live where the question gets asked, whether that is the page a visitor lands on, the message an assistant drafts, or the words whoever picks up the phone actually uses.

What to leave alone

Not everything belongs in a system, and forcing it in costs more than it saves. Keep a person in charge of anything where being wrong is expensive or personal: the exception you make because you know a client, a discount that depends on the relationship, a decision that touches someone's pay.

Relationships: who to call, and how they like to be approached
Whether a client is quietly turning into a problem
Anything tied to someone's performance, pay, or standing on the team

An AI assistant is good at giving the standard answer fast, every time, without getting tired of the question. It is not the one who should decide when to bend your own rule, and it should never be asked to.

Say it out loud before you start

Tell your team what you are doing before you start capturing anything, in plain words: you are writing down the routine so it does not disappear when someone is out. Silence on this point gets filled in with the wrong story, and "we are documenting your knowledge" can sound a lot like "we are replacing you" if nobody says otherwise first.

Framed the right way, it is closer to the opposite. Getting the routine questions off one desk is what frees that person for the judgment calls only they should be making, instead of answering the same three things all week.

Where to start this week

Pick the one question that has come up more than once this month and that only one person can answer well. Write the real answer down in two minutes, in plain words. Put it somewhere your team, or an assistant working on your behalf, will actually see it the next time it comes up. That is the whole method. Everything after that is doing it again, one question at a time, until the desk that used to hold everything is just one more person on the team.

Get the Know-How Out of One Person's Head