If you're interrupted a dozen times a day by questions you've answered before, the problem isn't that your team won't think. It's that the answer only exists in one place — you.
The cost of being the answer
Each interruption is maybe two minutes of talking and ten minutes of getting back to what you were doing. A dozen a day and you've lost most of a working day to something that produces nothing.
Worse, it's unpredictable, which means you can't do focused work at all — you're permanently on call within your own business.
The reframe that helps: people asking questions are trying to do the job right. The interruption is a symptom of missing information, not of poor initiative. Blaming the asking is the wrong response; removing the need to ask is the right one.
Find out what's actually being asked
For one week, keep a note every time someone asks you something. Just the question, roughly. At the end of the week you'll almost certainly find the same six or seven questions dominate — and that's a very solvable list.
The four categories, and what each needs
Fact questions
"What's the price for X?" "Where do we keep Y?" "Who supplies Z?" These need somewhere to look, not you. A shared document, a pinned note, anything findable.
Process questions
"How do I do X?" These need a written process. See getting what's in your head written down.
Permission questions
"Can I do X?" These need boundaries. If someone has to ask whether they can offer a customer a small goodwill discount, you haven't told them the limit. Set the limit and the question disappears.
Judgement questions
"What should we do about this awkward situation?" These genuinely need you — and once the other three categories are handled, you'll have time for them. These are the ones worth being interrupted for.
The one-hour fix
Take your list of recurring questions. Write the answer to each one — properly, once, in a form someone can find. An hour gets you most of the way, and it's an hour that pays back every week.
Prompt — building the answers
Here are the questions my team asks me repeatedly: [paste your list]. For each, write a clear answer document a team member could follow without asking me. Assume no prior knowledge. Where I need to supply specific information like prices or supplier details, mark it clearly as a placeholder rather than guessing. Add a 'when to ask the boss instead' note where judgement is genuinely needed.
That last instruction matters — you want to remove the routine questions while making it explicitly safe to escalate the real ones.
Then make people use it
The documents only work if the habit changes. When someone asks a question that's now written down, don't refuse to answer — answer, then point them to where it lives. After a couple of weeks people check first.
Be careful with tone here. "It's in the folder" said sharply teaches people not to ask anything, including the things they should. You want fewer routine questions, not a team that's afraid to speak.
What changes
Owners who do this typically get several hours a week back and, more valuably, get uninterrupted stretches — which is where the actual thinking happens. The team usually prefers it too: most people would rather look something up than interrupt the boss.
Interrupted all day?
An hour spent writing down the recurring answers pays back every single week. AskColin works with small businesses on exactly this — low-cost monthly support with one-to-one help whenever you need it. No jargon, no hard sell, and we'll tell you honestly if we can't help.
Have a free, no-obligation chatFrequently asked questions
Why does my team keep asking me the same questions?
Because the answer only exists in one place — you. People asking are trying to do the job right; the interruption is a symptom of missing information rather than poor initiative. Removing the need to ask is the fix, not discouraging the asking.
What does a constant stream of questions cost?
Each interruption is roughly two minutes of talking plus ten minutes regaining focus. A dozen a day loses most of a working day, and because it's unpredictable you can't do focused work at all — you're permanently on call within your own business.
How do I stop being the bottleneck?
Track the questions for a week — usually six or seven dominate. Fact questions need somewhere findable to look, process questions need a written process, permission questions need clear boundaries, and judgement questions genuinely need you.
How do I get the team to use written answers?
Answer the question, then point to where it lives. After a couple of weeks people check first. Watch your tone though — 'it's in the folder' said sharply teaches people not to ask anything, including things they should escalate.