Operations Analysis

Why Your Team Keeps Asking You the Same Questions

D
Author
DOMS Global LLP
Published
August 12, 2026
Read Time
6 min read
Why Your Team Keeps Asking You the Same Questions

Someone asks you how to handle a situation you explained last month. You answer, patiently. Two weeks later, a different person asks the same thing.

By the third time, you start wondering whether you hired the wrong people. It is a quiet, uncomfortable thought and most owners have had it.

They are almost never the problem.

What the repeated question actually means

A question asked repeatedly means the answer lives nowhere except in your head. Every time you answer, the knowledge transfers to one person for one situation and then evaporates. There is nothing for the next person to consult, so they consult you.

This is not a memory failure. It is a storage failure, and the storage is you.

If the same question keeps arriving, the answer is not being kept anywhere. That is a system gap, not an attitude problem.

Why writing it down has not fixed it

You may have tried this. Someone wrote a document, it went into a shared folder, and people kept asking anyway.

The document failed because of where it lives. To use it, a person must stop what they are doing, remember it exists, work out what it might be called, find it, and read enough to locate the specific answer. Asking you takes eleven seconds.

They are not avoiding the document. They are choosing the faster path, which is exactly what you would do.

Put the answer where the question happens

The rule that works: the answer must be closer than you are.

  • In the tool. A note on the job card, a required field, a template that opens with the guidance already in it.
  • At the handover. A standard message format that carries the answer with the work.
  • One page, one topic. Not a manual. A single page a person can scan in twenty seconds.
  • In the first week. New joiners should meet it during onboarding, not discover it after their first mistake.

Start with the questions you actually get

Do not document your business. Document your inbox.

For two weeks, write down every question anyone asks you. Do not answer differently, just note them. At the end, three or four will have come up repeatedly. Those are the only ones worth writing, and they will cover a surprising share of the interruptions.

Everything else is genuinely one-off and does not need a system.

The part owners find hardest

Writing the answer down means writing the reasoning, not just the conclusion. "Charge 15% extra for urgent jobs" without saying why leaves the person stuck the moment a situation is slightly different. Include the thinking and they can handle the variation you did not anticipate.

That is the difference between a rule and judgement, and judgement is what you are actually trying to transfer.

What you get back

The obvious return is your attention. The larger one is that your team stops feeling like they are bothering you, and starts making decisions with confidence — because they can check rather than ask.

People who can find answers act faster. People who must ask wait, and waiting is invisible until you count it.

If you recognised yourself answering the same thing again this week

That is a signal, not a frustration. It is telling you precisely which piece of knowledge is trapped in one place — and that is the most useful thing a business can learn about itself.

Frequently asked questions

Why does my team keep asking the same questions?

Because the answer lives nowhere except in your head. Each time you answer, the knowledge transfers to one person for one situation and then evaporates, leaving nothing for the next person to consult. It is a storage failure rather than a memory or attitude problem.

Why do documented procedures still get ignored?

Because of where they live. Using a document means stopping, remembering it exists, guessing what it is called, finding it and reading enough to locate the answer. Asking you takes eleven seconds. People choose the faster path, which is what anyone would do.

What should a business document first?

Document your inbox, not your business. For two weeks note every question anyone asks you. Three or four will recur, and those are the only ones worth writing — they typically account for a large share of the interruptions. Everything else is genuinely one-off.

What makes written guidance actually useful?

Including the reasoning, not just the conclusion. A rule such as "charge 15% extra for urgent jobs" leaves someone stuck the moment a situation differs slightly. Writing the thinking behind it transfers judgement, which is what lets people handle variations you did not anticipate.

knowledge managementSOPteam trainingprocess documentationdelegation

Recognise any of this
in your business?

Most of what we write about started as a problem someone brought to us. If something here sounded familiar, a conversation costs nothing and usually makes the constraint obvious.