Somebody asks you how to handle a certain kind of refund. You answer. Twenty minutes later, somebody else asks you the same thing. You answer again. Three weeks later, it comes up again in a different context. You answer a third time.
Each answer takes less than a minute. The problem is not the minute. It is that you have now burned three separate windows of your day explaining the same thing, and you will burn three more next month, because the answer is still only in your head.
There is a rule I use with most of the businesses I work with. If you are explaining the same thing three times, that is the signal to document it. Not the fifth time. Not the tenth. The third. Three is enough data to know that it is a recurring pattern, not a one-off.
Why the same questions keep coming back
This is not a team problem. This is a geography problem. The information exists, but it lives in a place only you have access to, which is your head. So every time anyone needs it, they have to come to you to get it. That is not lazy. That is rational behavior inside a system that has no other source.
A few things tend to keep the questions coming.
The business grew faster than the documentation. When you were a two-person operation, "just ask Rock" was a working system. At five or eight people, the same system is interrupting you every forty-five minutes.
There is no place to put answers. Even if you wanted to write something down, there is no shared home for it. No wiki, no pinned channel, no doc. So questions stay in Slack threads that get buried by lunchtime, and the next person who has the same question has no way to find last week's answer.
People learn by asking you because that is the culture. If the first thing a new hire learned was to ask you, that is what they keep doing. The second and third person down the line learn from them. The asking reflex is baked in before anyone notices.
Writing things down feels slower than just saying them. It is, in the moment. It is much faster over a month. But you are always in the moment, so you keep choosing the faster short-term option and paying the long-term tax.
The real cost of the repeat question
Each interruption is worth more than the thirty seconds it takes to answer, because context switching has a real cost. Studies on focused work put the reset after a significant interruption at fifteen to twenty minutes. Get interrupted ten times in a day and you have lost most of a day's deep work to answer-giving.
Your team cannot train itself. New people cannot learn from the answers you gave last quarter, because those answers are not written anywhere. So they ask you, or they ask the senior staffer, who asks you. The onboarding load lands on the same few people every time. The senior staff gets worn down by being the backup answer desk.
Decisions get made with incomplete information. When people cannot find the answer, they sometimes just guess. Sometimes the guess is fine. Sometimes it is wrong in ways you only discover later, which turns into more of your time cleaning up something that would have been prevented by a two-sentence note.
Your business cannot run without you. If every question lives in your head, then a sick day is a business outage. A vacation is a slow-motion outage. Not being able to leave is not the consequence of having an unusual role. It is the consequence of being the only place the answers live.
The three-times rule
Here is the rule, in its simplest form. When you have answered the same question three times, you owe the business a document.
Not a polished one. Not a formal one. A short, plain-language answer, in a shared place, that the next person can find and use without asking. Think of it as a running FAQ for your actual operation.
The first time somebody asks, just answer. Maybe it is a one-off.
The second time, note it. Make a mental mark or, better, a written note somewhere you will see again.
The third time, before you answer, open a doc and write down the answer. Then point the person at the doc. Next time the same question comes up, you are not the answer. The doc is.
You will be amazed how fast this adds up. Most small businesses, when they actually follow this rule for a month, find that twenty to thirty recurring questions cover the vast majority of what their team keeps asking. Write those answers down, and you have reclaimed a real chunk of your week.
Where to put the answers
The specific tool matters less than you think. Notion, Google Docs, a pinned Slack channel, a shared Apple Note, whatever your team already uses. The rule is one known place, not a new one.
A few things make the doc actually get used.
Make it searchable. If it is a Google Doc with thirty sections, use headings so search works. If it is Notion, tag things. If it is a pinned Slack channel, keep it short.
Keep entries small. A question and a two-to-six-sentence answer. Do not write an essay. This is a reference, not a manual.
Link to it from the places people already ask questions. If the team asks in a specific Slack channel, pin the doc there. If they ask by email, the auto-reply has the doc linked. Make the doc the path of least resistance, not a detour.
Update it when the answer changes. The fastest way to destroy a knowledge base is to let it go stale. If a process changes, the doc changes that day.
What you will notice in a few weeks
The interruptions thin out. Not all at once, but steadily. In the first week people will still ask you. You will point them at the doc. After two or three pointings, they start checking the doc first.
Your senior staff starts checking the doc too. That is the quiet moment the pattern actually shifts, because now the knowledge is not just flowing out of your head. It is flowing across the team.
New hires get faster. They have a place to go that is not a person. A lot of their first-two-weeks questions turn into ten-minute self-serve moments. Your onboarding tax drops.
And your head gets quieter. You are not carrying the "I need to remember to tell so-and-so about that thing" load around all day. The doc is remembering for you.
This is not about building a corporate knowledge management system. It is about getting the operating memory of the business out of one person's head and into a place where the team can use it. That is the Deming principle in small-business form, most of the problems in the business are system problems, and this is one of the cheapest, highest-leverage systems you can build.
The Monday action
Open a fresh doc somewhere your team already looks. Title it something obvious, like "Things We Keep Asking."
This week, every time you answer a question, ask yourself if this is the third time. If it is, write the answer into the doc before you even answer the person. Point them at the doc.
Do that for one week. At the end of the week, count how many entries the doc has. Do not be surprised if there are seven or eight.
Next week, do the same thing. By the end of a month, you will have a small but real reference that covers the bulk of what used to interrupt your day. You did not take a Saturday to write a manual. You took a month to respond slightly differently to the questions that were already coming in. Same effort, different result.
If you want an outside eye on where the biggest interruption costs live in your business and what to document first, a Flow Check is the simplest place to start. For the deeper read on why good teams still ask the same questions, good people, bad systems is a natural companion.