Owner at a desk watches a phone stack up with message bubbles, thumb resting without tapping

What Does Your Team Text You About Most?

November 09, 2026•10 min read

TL;DR: A question your team keeps texting you, asked by the same person more than once, points to a missing document, because without a written answer the person has no reliable place to check and has to ask again. The fix is to find the one question you answer most often and turn it into a short written rule that lives where the team already looks. Do that and the repeat texts should drop, which is the test of whether the document was actually missing.

Key Takeaways

  • A repeated question from the same person signals that an answer was never written down.
  • This creates rework when the same question gets answered again, because each repeat costs the owner time and leaves the employee waiting on a reply instead of acting.
  • The fastest fix is to identify your single most frequent team question and convert it into a one-page written answer stored where the team already looks for information.
  • Asking an employee what they think the answer is, before giving one, builds the habit of deciding and surfaces whether the gap is information or confidence.
  • A written answer removes the judgment calls that have a fixed, repeatable answer and should never have required a text in the first place.

The Text You Get Every Week

If you run a small team, you know the exact question. It might be about which vendor to call for a specific repair, how to handle a return outside the standard window, or what to quote a customer who wants a rush job. The person asking is usually capable, reliable, and otherwise doing fine work. The question just keeps coming back, and answering it for the fifth or fifteenth time wears on you.

This is the core problem behind repeated team questions: the answer lives only in the owner’s head, so the questions keep coming. A missing document (a written answer, rule, or reference that does not currently exist anywhere the team can find it) is the actual gap. The team member and the owner are both doing exactly what the situation allows. One has a question with no fixed answer to check. The other is the only reference source available, which makes the owner a bottleneck by default rather than by choice.

Treating this as a performance issue misses the point and can make things worse. The employee stops asking, guesses instead, and now you have a wrong answer instead of a repeated question. The better move is to name the gap accurately and close it once.

Why the Same Question Keeps Coming Back

A repeated question keeps coming back because nothing was ever written down the first time it was answered, so the employee has no record to check and has to ask again. The owner answers verbally, by text, or in a hallway conversation, and the answer exists only in that one exchange. Without a stored version, the next time the situation comes up, the employee faces the same choice: interrupt the owner again, or guess. The safer option is to ask, which is the correct choice given what they have to work with.

The rework is not dramatic on any single occasion, a minute here, a pause there, but it compounds across a team and across months. The real cost is the decision that stalls until the owner responds.

A repeated question is a signal that no document exists where the answer should be.

Finding Your Most Repeated Question

The most repeated question is usually obvious once you track it for a week or two, because one topic will show up far more often than any other across texts, calls, or in-person interruptions. An owner tracking this often senses which question it is before counting anything. The counting step matters anyway, because it confirms the target and keeps you from documenting something that only came up once.

A simple way to find it:

  1. Keep a running list for one to two weeks of every question a team member brings to you, noting who asked and what the topic was.
  2. Sort the list by topic, not by person, since the same gap can surface through more than one employee.
  3. Identify the single question that recurs most often across that window.
  4. Set that one aside as the first document to write. Everything else waits.

This matches a pattern SCORE describes in a small business where an owner is repeatedly asked questions that staff could answer themselves, and where asking the employee what they think the solution is, before answering, helps build the habit of deciding rather than defaulting to the owner.

Writing the Answer Once

Turning a repeated question into a written answer means capturing the decision rule in plain language, in one place, so the next person who has the question can find it without texting anyone. The format does not need to be elaborate. A short paragraph, a numbered list of conditions, or a simple table covering the common variations is usually enough to close the gap.

The steps that make this stick:

  1. Write the answer as a decision rule, not a story, so it reads as “if this, then that” rather than a narrative of what happened last time.
  2. Keep it to one page or less. A document nobody reads in full is as useless as no document.
  3. Store it where the team already looks (the shared location, binder, or system staff already check for other information), not in a new tool created just for this.
  4. Tell the team directly that the answer now lives there, and point to it the next time the question comes up instead of answering verbally.
  5. Review it after a month to confirm it still matches how the business actually operates.

Write the answer once, store it where the team already looks, and the repeated question has nowhere left to go.

Old Way vs. New Way

Old way New way
Where the answer lives In the owner’s memory In a written document the team can check
Who answers the question The owner, every time The document, most of the time
Cost of a repeat A text, a pause, a wait for reply None, the person checks and moves on
What builds over time Owner fatigue and a longer queue of interruptions A small, growing reference the team trusts

The trade-off is upfront time. Writing the first document takes longer than answering the question one more time. It pays back as soon as the question comes up a second time after the document exists.

A written answer pays back the first time the same question comes up again.

In Practice: Documenting a Repeated Question

Situation: An office manager keeps texting the owner to ask how to price a rush order, because the standard price list does not cover jobs needed sooner than the normal turnaround.

Steps:

  1. Track every version of the rush-order question for two weeks, noting the circumstances each time it comes up.
  2. Identify the pattern across those instances, such as which turnaround times trigger a surcharge and by how much.
  3. Write a short rule covering the common cases, for example a percentage add-on (example amount) for same-day requests and a lower one for next-day requests.
  4. Store the rule in the shared pricing reference the office manager already opens for every other quote.
  5. Tell the office manager the rule now lives there and ask them to check it before texting next time.
  6. Confirm after two weeks whether the texts about rush pricing have stopped.

Result: A one-page pricing rule exists in the shared reference, and the test of success is whether the same question stops arriving by text.

Common mistake: Writing the rule somewhere new instead of the place the team already checks, which means the document exists but never gets used. Fix this by adding it to the existing reference instead of creating a separate one.

If it goes wrong: If the questions keep coming after the document is in place, check whether the employee knows it exists and knows where to find it before assuming the document itself is the problem.

This is an illustration, not a report of an actual client result.

FAQs

Why does my employee keep asking the same question?

An employee keeps asking the same question because no written answer exists anywhere they can check, so each time the situation comes up they have to ask again rather than look it up. This does not reflect poor attention or weak judgment on their part. It reflects a gap in what the business has documented, and the fix is to write the answer down once rather than repeat it verbally each time.

How do I stop answering the same question over and over?

You stop by identifying the question you answer most often, writing it up as a short decision rule, and placing it where the team already looks for other information. Once the document exists, you can point to it instead of answering from memory, which shifts the reference point away from you and reduces the number of times you’re interrupted for the same topic.

What counts as a missing document?

A missing document is any answer, rule, or piece of information an employee needs regularly that currently exists only in the owner’s head or in a one-time conversation, not in a stored, checkable place. It can be a pricing rule, a vendor contact, a return policy exception, or any other recurring decision that has a consistent answer but no written record of it.

Should I just tell my employee to stop asking and figure it out?

No, because without a written reference the employee has nothing reliable to figure it out from, and guessing without one increases the risk of inconsistent answers to customers or vendors. The better approach is to ask what they think the answer is first, which surfaces whether they need information or just reassurance, then follow up with a written rule they can use going forward.

How long should a written answer be?

A written answer should be as short as possible while still covering the common variations of the question, often a single page or less. Longer documents get skipped, and a document nobody reads defeats the purpose of writing it in the first place.

What if the question doesn’t have a fixed answer?

Some questions genuinely require judgment every time, and those should stay as questions rather than get forced into a rule that does not fit the situation. The distinction matters: if the answer has been the same every time it came up, it belongs in a document, and if it has varied, it belongs with a person making a case-by-case call.

Where should I store the written answers?

Store them in the location your team already checks for other operational information, such as a shared drive folder, a pricing sheet, or an internal reference page, rather than creating a new tool just for this purpose. A new location adds a step people are likely to skip, while an existing one keeps the habit consistent with how the team already works.

Next Steps

The next time the same question comes in from the same person, resist answering it from memory and write it down instead, in the place your team already checks. That one document will not fix every gap in how your business runs, but it closes the loop on the question costing you the most time right now. Share this with a business partner who gets the same texts.

repeated team questionsprocess documentationdelegationsopowner dependency
May Fundora
May Fundora|Founder | Great Lakes Business Support|LinkedIn logo iconInstagram logo icon
May Fundora founded Great Lakes Business Support (GLBS) to bring structure to the parts of a small business that usually run on guesswork — scheduling, follow-up, intake, the stuff that falls apart when nobody's watching it. Her background is in healthcare IT and airline operations, two industries where a missed step has real consequences and there's no room to wing it. She built GLBS around that same standard: test the process, fix what's actually broken, and only add a system if it makes the business more dependable. If something on this blog sounds practical instead of flashy, that's on purpose.
Back to Blog

Your business doesn't need more ideas. It needs the right next step.

GLBS helps small service businesses identify the operational gaps costing them time, consistency, and revenue.