Employees Keep Asking the Same Questions? Here's the Fix

Employees keep asking the same questions because asking a person is still faster than finding the answer themselves. The fix isn’t telling people to “check the wiki.” It’s making the written answer quicker to reach than you are.

If you run operations or founded a growing company, you probably know the feeling. Every company has a Sarah: the person who knows where the expense policy lives, how the holiday rules work and who approves a new laptop. “Just ask Sarah” is efficient for everyone except Sarah.

The numbers suggest this is mostly avoidable. Atlassian’s 2025 research on HR knowledge management found that more than half of HR and People leaders say at least 75% of employee requests are about information that already exists in their intranet or knowledge base. The answers are there. The path to them isn’t.

This guide covers why the same questions keep coming back, what they really cost, and six steps to get your time back.

Key Takeaways

• Repeat questions are a findability problem, not a people problem. Often the answer already exists somewhere; it just takes longer to find than asking you does.
• The cost isn’t only the minutes per answer. It’s the constant interruptions and the risk of all that knowledge living in one person’s head.
• The fix takes six steps: log the questions, write the top answers once, put them in one place, reply with links, let an AI knowledge base give the first answer with its source, and keep answers current.

Table of contents

Why do employees keep asking the same questions?

People ask a colleague when that feels faster or safer than looking it up. It usually comes down to one of four reasons.

1. The answer was never written down

A lot of company knowledge only exists in someone’s head. SHRM’s 2025 research among 1,912 HR professionals found that 83% document company policies, but only 32% document cultural norms and 43% document client relations. “How we do things here” is exactly the kind of question that lands on Sarah’s desk.

2. It’s written down, but nobody can find it

Documents spread across Google Drive, Notion, Slack threads and old email attachments. Atlassian’s State of Teams 2025 found that leaders and teams waste 25% of their time just searching for answers. When search fails, people ask the person who knows.

3. It’s found, but not trusted

Three versions of the travel policy, one of them from 2021. When people can’t tell which document is current, they ask you to confirm, which is a repeat question in disguise.

4. Asking is simply easier

A DM costs the asker ten seconds, while you pay for it in focus. New hires ask even more, and for good reason: in BambooHR’s 2023 onboarding survey, 65% of employees named a lack of clarity around who can answer their questions as a top onboarding frustration.

What do repeated questions really cost?

Repeat questions cost you focus, not just minutes. Microsoft’s Work Trend Index 2025 found that employees are interrupted every two minutes during core work hours, 275 times a day, by meetings, emails or chats.

The most detailed recent data on answering colleagues comes from developers. In Stack Overflow’s 2024 Developer Survey, 47% of professional developers spend 30 minutes or more a day answering questions at work, and 48.8% agree they often answer questions they’ve already answered before. Developers aren’t ops leads, but anyone who is “the Sarah” of their team will recognize the pattern.

About that “23 minutes to refocus” statistic. You’ll often read that it takes 23 minutes and 15 seconds to get back on task after an interruption. That exact number comes from a 2006 Gallup interview with researcher Gloria Mark, not from a published paper. Her 2005 field study found that interrupted work resumed the same day took about 25 minutes to get back to, on average after switching through about two other tasks. Her 2008 lab study found something more surprising: interrupted people finished faster, but reported significantly more stress, frustration and time pressure. The real cost of constant questions isn’t just lost minutes. It’s a more stressful day.

There’s a bigger risk too: key-person dependency. In a 2025 APQC survey of 1,000 professionals, 92% of respondents said their organization doesn’t consistently capture knowledge from employees who are about to retire. If Sarah goes on holiday or leaves, the answers go with her.

How to stop answering the same questions in 6 steps

You don’t need a big knowledge management project. You need a short list of the questions that actually come up, good answers to them, and a habit of pointing people there.

Step 1: Log every question for two weeks

By the end of this step, you’ll know which 10 questions cost you the most time.

Keep a simple log. A spreadsheet or a pinned note works fine. Every time someone asks you something, write it down:

After two weeks, sort by “times asked.” The top of that list is your roadmap. Also record the exact words people use: they’re the words your team will type into search later.

Step 2: Write the top 10 answers once

Write each answer so someone can act on it without asking a follow-up question.

For each question on your list, write one short page:

1. Use the question as the title, phrased the way people actually ask it.
2. Answer in the first sentence. “Yes, up to 10 working days a year, with your manager’s approval.”
3. Add the steps, links and exceptions below that.
4. Name an owner and a review date at the bottom, so people know the page is current.

This is where GitLab’s approach helps. Its handbook-first guidance states that any answer that isn’t documented yet should be documented immediately. You write it once, and it serves everyone who asks after that.

Step 3: Put everything in one place

Pick one home for answers and make it the only official source.

Answers spread across five tools are almost as bad as no answers at all. In a 2024 Gartner survey, the most common reason customers failed at self-service (43% of cases) was that they couldn’t find content relevant to their issue. That research is about customers, but the lesson carries over to your own team: a document nobody can find doesn’t prevent a single question.

Policies and “how we work” pages belong in a single handbook. If you’re setting one up, see our guide to employee handbook software and a free template. Delete or clearly archive old versions, because two conflicting answers are worse than one.

Step 4: Reply with a link, not a paragraph

From now on, every repeat question gets a link, not a typed-out answer.

This is the step that changes behavior. If you keep typing the answer, people will keep asking you. Some replies that stay friendly:

• “Good question, it’s all here: [link]. Let me know if anything’s unclear and I’ll improve the page.”
• “That’s not written down yet. I’ll add it today and send you the link.”

Two habits make this stick. First, move questions out of DMs and into a shared channel like #ask-ops. Private messages aren’t searchable for anyone else, so the next person asks again. That’s the argument behind Jonathon Belotti’s case against Slack DMs. Second, for complex questions, offer office hours instead of instant replies. Engineer Nicholas Zakas found that people often got themselves unstuck while waiting for the scheduled slot.

Step 5: Let an AI knowledge base give the first answer

Once your answers are written down, let people ask a question in plain language and get the answer straight from your documents.

A search box still makes people guess the right keyword and open five documents. An AI knowledge base lets them ask “can I work from Spain for a week?” and get a direct answer. The one requirement: every answer must show its source. In the 2025 global study by KPMG and the University of Melbourne, two-thirds of people using AI at work said they rely on its output without evaluating its accuracy. With the source next to the answer, anyone can check the actual policy in one click, and you stop being the person who has to confirm it.

This is what we built Fylos for (full disclosure: it’s our product). Answers come only from your company’s documents, with the exact document and section shown in a side panel. For an honest comparison with Notion AI, Confluence, Copilot and others, see our guide to the best AI knowledge base tools.

Step 6: Keep answers current and measure the drop

Treat your answers like a product: they need owners, updates and a success metric.

Outdated answers bring the questions right back, because people stop trusting the source. Every page should have an owner and a review date, and changes to a policy should update the page on the same day.

To see whether it’s working, keep your question log from step 1 running, one week per month. Track three numbers:

• Repeat questions per week that reach you personally
• Share of questions answered with a link instead of a typed answer
• New questions without a page yet, which is your writing backlog

If repeat questions don’t drop, check step 3 first (can people find the answer?), then step 4 (is a DM still faster?).

Frequently asked questions

Isn't replying with a link a bit rude?

Not if you’re friendly about it. A link with a short, warm line (“It’s all here, shout if anything’s unclear”) is faster for the asker than waiting for you to type a reply. It also tells them where to look next time. Rude is sending “RTFM.” Helpful is sending the exact page.

How long does it take to see fewer repeat questions?

Plan on about a month for steps 1 to 4: two weeks of logging, then a few hours to write the top 10 answers. How quickly the questions drop depends on how consistently you reply with links. Your question log is the honest measure, so compare the first two weeks with the same period a month later.

What about questions that are personal or sensitive?

Keep them personal. Salary conversations, health situations and conflicts belong with a person, not a knowledge base. The goal is to free up your time for exactly those conversations by taking the “where’s the expense form?” questions off your plate.

Do we need special software for this?

Not to start. A shared doc and a Slack channel get you through steps 1 to 4. Software starts to pay off once you have more than a few dozen answers, need permissions, or want people to get answers without searching. Then a handbook tool or an AI knowledge base saves real time.

Stop being the human search engine

Employees keep asking the same questions because asking you is the fastest route to an answer. Change that, and the questions change.

• Log the questions for two weeks and pick the top 10.
• Write each answer once, in one place, with an owner.
• Reply with links, and move questions out of DMs.
• Let an AI knowledge base give the first answer, with the source attached.
• Keep it current and measure repeat questions monthly.

If you also need proof that people actually read the policies you’re linking to, see our guide on how to prove employees read a policy.

Ready to hand the first answer to your documents? Try Fylos free for 15 days: answers from your own documents, with sources you can check. No credit card needed.