How to stop answering the same questions at work
The same questions keep landing in your DMs. Why it happens, what it costs your team, and five practical ways to make repeat questions stop for good.
"Where's the latest deck?" "What's our PTO policy?" "Who owns billing?" If you are the person people ask, you answer these several times a week, often the same one twice in a month. Each answer takes a minute, and the minute is not the problem. The interruption is, and so is the fact that the answer clearly exists yet keeps having to come from you.
Answering the same questions is a symptom, not a personality trait of your team. This post covers why it happens and five practical ways to make it stop.
Why the same questions keep coming back
Three things keep the loop going.
- The answer is not written down, so the only copy is in someone's head. That is tribal knowledge, and every question to that person is a withdrawal from an account only they can access.
- The answer is written down, but nobody can find it. It is in a Notion page three folders deep, or a Slack thread from March. Asking a human is faster than the search, so people ask the human.
- The answer changed, and no one trusts the written version. If the doc is sometimes stale, people stop relying on it and route around it, straight back to you.
What it costs
The cost is not the minute per answer. It is the context switch. Microsoft research published in Harvard Business Review found employees toggle between apps and websites nearly 1,200 times a day, and every "quick question" is one more toggle for whoever gets asked. Scale that across a growing team and you are funding a part-time job nobody applied for: keeping answers in their head and dispensing them on request. It also does not scale. The person who knows will eventually be busy, asleep, or gone.
Five ways to stop
- Write the answer once, where it will be found. When a question comes up twice, that is your signal to document it, ideally in the tool people already search, not a new place they will not think to look.
- Make answers findable, not just filed. Documentation only helps if people can retrieve it. If finding an answer is slower than asking a colleague, people will ask the colleague. Reduce the friction of retrieval, not just of storage.
- Capture the unwritten knowledge. Most repeat questions are for answers that were never written at all. Capture them at the moment they are asked, so the first answer becomes the last time anyone has to ask a person.
- Fix onboarding at the source. A large share of repeat questions come from new hires. Strong onboarding documentation, or a system that answers new-hire questions directly, stops the same twenty questions from recurring with every joiner.
- Put a company brain in front of it all. The durable fix is a single place people can ask that answers from your tools and, when nothing is written, asks the person who knows and saves the reply. That is what a company brain does: it turns each question into a one-time cost instead of a recurring one.
How Agentwork helps
Agentwork answers your team's questions across the tools you already use, with the source attached. When the answer is not written down, it asks the person who knows, captures the reply, and reuses it, so the second time someone asks, the answer comes from Agentwork instead of from you. Repeat questions stop being your job and become a growing record your whole team can draw on. It is free to start, with no seat minimum.
Frequently asked questions
Why do the same questions keep getting asked?
Usually because the answer lives only in someone's head, or it is written somewhere people cannot easily find, or the written version is stale enough that people stop trusting it.
How do I get my team to stop asking me directly?
Make the answer faster to find than to ask for. Document recurring answers where people already search, and use a tool that captures unwritten answers so they are reusable.
What's the difference between documentation and a company brain?
Documentation is answers you write and maintain by hand. A company brain answers live across your tools and captures answers that were never written, so it closes gaps that documentation alone leaves open.