You answer the same question ten times
TL;DR
The same questions keep coming back because the answers live only in your head.
Each answer costs a few minutes, but ten of them a day cost your whole morning.
Answers given from memory change slightly each time, and that drift causes rework.
The fix is simple: write each repeated answer once, in one place everyone can find.
Start with the ten questions you hear most. That list alone frees hours a week.
A team member messages you: how do we price this job? A client calls: what is included in the package? Another team member asks the same pricing question on Thursday, because they never saw your Monday answer. You answer all three, patiently, and by Friday you have answered the same question ten times.
Nobody is being lazy. The answer simply does not exist anywhere except in your head. So every person who needs it has only one way to get it: ask you. Your phone becomes the help desk for your own business, and the business waits in line behind your replies.
This is the quiet version of the chaos behind the answer is somewhere in the chat. There, the answer exists but nobody can find it. Here, the answer was never written down at all. Both end the same way: work stops until the founder replies.
Why does the same question keep coming back?
Because answering feels like solving, but it solves nothing for the next person.
When you answer in chat, the answer helps one person, once, and then sinks under new messages. The next person with the same question cannot find it, so they ask again. You answer again. The cycle repeats, and each round feels small. Five minutes here, three minutes there. Nobody notices the total until the day is gone.
The deeper cause is that your business has no written memory. Prices, package details, delivery steps, refund rules, and who handles what: all of it lives in your head, because you built it there. A new team member cannot read your head. A client cannot search it. So they do the only thing they can. They ask.
That is also why nobody owns the follow-up hurts in the same way. A job that lives in memory gets forgotten. An answer that lives in memory gets asked again. Memory is a fine place to think, and a terrible place to store a business.
How much time does answering cost, really?
More than the minutes suggest, because every interruption costs the work around it.
A Panopto survey of 1,001 American employees found workers spend an average of 5 hours every week waiting to get hold of people with the knowledge they need, and 8 hours a week pushing ahead on their own when they cannot get it. The waiting is your team, standing still until you reply. Read the Panopto knowledge sharing survey.
The search side is just as heavy. McKinsey research widely cited in workplace studies puts time spent searching for and gathering information at roughly 20 percent of the workweek, about one full day a week. Atlassian research pushes it further, with teams losing up to 25 percent of their time searching for answers, and 56 percent of employees regularly needing to ask someone or book a meeting just to find what they need. See the time wasted searching for information summary.
Your firm is smaller than those surveyed companies, but the shape is the same. Ten questions a day, at five minutes each, is nearly an hour of answering. Add the time your team waits for the answer and the time you take to get back into your own work, and the real cost is double that. The founder becomes the bottleneck not because the team is weak, but because the answers have only one source.
Why do your answers change each time you give them?
Because memory edits itself, and nobody notices.
Answer the pricing question on Monday and you mention the discount. Answer it on Thursday, in a hurry, and you forget the discount. The client hears one price. The team quotes another. Now you have a version of the same problem as you quoted three prices to the same client, except the cause is not chat. The cause is that the answer was never fixed in writing, so every retelling is a new draft.
The same drift hits delivery. One team member remembers the package includes two revisions. Another remembers three. Both are sure, because both heard it from you, on different days, in different words. The client hears the bigger promise and holds you to it. You did not mislead anyone. You simply answered from memory ten times, and memory gave ten slightly different answers.
Written answers stop this drift. Not because writing is magic, but because writing freezes one version. When the answer changes, you change the written version, and everyone reads the new one. The argument about what was said ends, because the answer is a document, not a memory.
What does "write it once" actually look like?
It looks like a short list, not a manual.
Nobody needs a 50 page handbook. You need one page per repeated question, with the answer in two or three lines, kept in one place the whole team can open. When someone asks, you send the link instead of typing the answer again. After a few weeks, people stop asking you and start opening the page first. That is the whole system.
| Question you keep hearing | What to write down | Where it should live |
| How do we price this job? | The rate, what is included, what costs extra | One pricing page, linked from every quote |
| What is included in the package? | The exact list, in plain words | The same page the client sees before they buy |
| Who handles this kind of job? | One named person per job type | One team page, not five chats |
| What happens if the client changes the brief? | Log it, price it, then build it | The brief itself, as in the brief changed in chat |
| When will the client hear from us? | The update day, and who sends it | The job page, so clients keep asking for updates slows down |
Notice what is not on this list: a training program, a new tool, or a wiki project. Ten short answers, written plainly, beat a grand system that nobody opens. The tool matters far less than the habit. One place, short answers, kept current.
How do you start on Monday morning?
Start with the questions, not the system.
First, write down the ten questions you answered last week more than once. You will know them without thinking. They are the ones that made you sigh when the phone buzzed, because you had answered them on Tuesday already. Second, write a two or three line answer for each, in the words you actually use when you say it. Third, put all ten on one page, and send that page to the team with one line: check here first, and tell me if an answer is wrong or missing.
Then keep one rule for yourself. When someone asks a question that is on the page, send the link, not a fresh answer. When someone asks a question that is not on the page, answer it, then add it to the page the same day. The page grows by one line at a time, and each line is one fewer interruption next week.
This also fixes the hiring problem quietly. A new hire who can read ten written answers does not need to shadow you for a month to learn how the business works. They read, they ask about what is missing, and they start doing real work sooner. The page is not just saved time. It is the business, written down, in a form that survives you being busy, away, or simply tired of answering the same question for the eleventh time.
And when the repeated questions stop eating your mornings, the next problem becomes visible: the enquiry that never got a reply. That is a good trade. Answering the same question ten times keeps you busy. Answering a new enquiry once brings in work. One leak at a time, in the order the money actually flows.
Frequently Asked Questions
My team asks because they want my judgement, not just facts. Does writing answers down remove that?
No. Written answers handle the facts: prices, inclusions, steps, owners. Judgement calls still come to you, and that is right. The point is to stop judgement time being spent on facts. When the facts are written down, the questions that reach you are the ones only you can answer, and there are far fewer of them.
What if the answer changes often? Won't the page go out of date?
It will, and that is fine, as long as one person owns the page. Change the written answer when the real answer changes, and tell the team. An out of date page is still better than ten different memories, because everyone reads the same version and you can fix it once. Ten memories need ten fixes.
Who should write these answers in a small team?
You, at first, because the answers are in your head. Keep each answer to two or three lines, and do ten of them, not a hundred. After that, let the person who owns each job type keep their own answers current. You check the page once a week, not every line. Ownership per page beats one person owning everything.
My clients ask the same questions too. Do I share the page with them?
Share the client-facing answers, not the internal ones. Prices, inclusions, timelines, and what happens on a change: clients should read those before they buy, because a client who read the answer asks fewer questions later. Internal answers, like who handles what, stay on the team page. Two pages, same habit.
Does this mean I need new software?
No. A document, a note, or a single page on your existing site all work. Software helps only after the habit exists. If the team does not open one page, they will not open a new tool either. Start with the page. Buy the tool later, if the page outgrows it.