Person at a desk pulls a loose sticky note from a monitor crowded with notes

Which Questions Only You Can Answer Right Now?

November 07, 2026•9 min read

TL;DR: Owner-only knowledge is any answer that only the business owner can give because it was never written down, and you can surface most of it by reviewing the last two weeks of texts, calls, and interruptions that came directly to you. The pattern is the proof. If the same three or four questions keep landing on your desk, the issue is what isn’t documented yet.

Key Takeaways

  • Owner-only knowledge is any answer that exists only in the owner’s head and nowhere else in the business.
  • The questions that keep coming back point directly at what isn’t documented.
  • Reviewing two weeks of texts, calls, and interruptions is enough raw material to build a usable list in one sitting.
  • Each repeated question needs a source of truth, a single place where the answer lives so it doesn’t route back to the owner.
  • Sorting the list by frequency and risk tells you which answers to document first and which can wait.
  • This is a documentation exercise. Writing the answer down comes before deciding who else can use it.

What Is Owner-Only Knowledge?

Owner-only knowledge is any decision rule, exception, or answer that lives solely in the owner’s memory because it has never been written into a process, a policy, or a reference document. It is the specific, recurring answer that an employee or system cannot produce without asking the owner directly, because no other source of truth exists for it. The clearest sign is repetition. If a question has come up more than once in the last two weeks, from different people or the same person twice, it is a candidate for the list.

This differs from general business judgment, which genuinely requires experience and context an owner builds over years. Owner-only knowledge is narrower and more mechanical: a specific vendor’s return policy, a pricing exception for a particular account, the order in which two steps have to happen on a rush job. These are answerable in a sentence or two, and once written down, they stop needing the owner at all.

Why the Questions That Keep Coming Back Matter

The questions that keep coming back matter because each repetition is a measurable cost, not a one-time interruption, and the pattern tells you exactly where to document first. A question asked once might be a fluke, a new hire finding their footing, or a genuine edge case. A question asked three times in two weeks from different staff members is a gap in the source of truth, and it will keep generating the same interruption until someone closes it.

A question asked three times in two weeks is a documentation gap with a predictable cost.

The cost compounds in a specific way: every time the owner answers from memory instead of from a written source, the next person who needs that answer still has no document to check, so they ask again. The interruption itself never resolves the underlying gap. It only resolves that one instance.

The issue is what isn’t written down anywhere the asker could have checked first.

How to Build the List From Two Weeks of Activity

Pull the last two weeks of texts, calls, and interruptions into one place before trying to categorize anything. The goal at this stage is volume, not analysis. Open the three channels where questions actually land and work through each one in order.

  1. Texts. Scroll your phone for the last two weeks and flag every message where someone asked you something rather than told you something.
  2. Calls. Check your call log or voicemail transcript for the same window and note who called and what they needed an answer to.
  3. Interruptions. Think through in-person stops: someone catching you at your desk, in the parking lot, mid-task, to ask a question they couldn’t resolve on their own.
  4. Write each one down as a short phrase. Don’t summarize or group yet. One line per instance, even if two lines turn out to be the same question.
  5. Sort by repetition. Group the lines that are really the same question asked more than once, and count how many times each one appears.
  6. Rank by risk. For each repeated question, note what happens if the wrong person guesses the answer instead of asking: a refund given that shouldn’t have been, a job scheduled in the wrong order, a customer quoted the wrong price.
  7. Mark a source of truth for each. Next to each question, write where the answer will live once it’s documented: a shared document, a laminated sheet at the front desk, a field in your scheduling software.
Channel Example Question Risk If Guessed
Text “Can we price-match this one customer’s old rate?” (example) Inconsistent pricing, customer disputes
Call “What do we tell a vendor when a delivery is late?” (example) Damaged vendor relationship, missed follow-up
Interruption “Which supplier do we use when the usual one is out of stock?” (example) Wrong material ordered, delayed job

This table is illustrative. The actual questions and risks will come from your own two-week pull, not from this example.

Not everything on this list will be worth documenting right away. Some questions are rare enough, or low-risk enough, that writing them down can wait. The repeated, high-risk ones are the ones to document first. The specific cutoff for “worth documenting” needs testing in your own operation.

Separating Known Answers From Assumed Answers

Once the list exists, go through it a second time and mark each item as either known (you’ve confirmed the answer is consistent and correct) or assumed (you’ve been answering it the same way out of habit, but haven’t verified it’s still accurate). This second pass matters because documenting an assumed answer just moves the guesswork from the owner’s head into a written document, without actually fixing it.

A documented wrong answer spreads faster than an undocumented one.

For assumed items, take the extra step of verifying before writing the final version down. Check with a vendor contract, confirm a policy actually still applies, or test the decision rule against a recent example before it becomes the official source of truth. Skipping this step is a common mistake in this process: treating “I’ve always said X” as equivalent to “X is correct.”

In Practice: Building the Question List

Situation: An office manager at a small service business notices that the same handful of questions keep coming back to the owner by text, even when the owner is out for the day.

Steps:

  1. Export or scroll the owner’s text and call history for the prior two weeks using the phone’s built-in search or call log.
  2. List every incoming question on a shared spreadsheet, one row per instance, without summarizing yet.
  3. Group duplicate questions and count how many times each one appeared in the window.
  4. Rank the grouped list by frequency, then by what happens if someone guesses wrong.
  5. Assign a source of truth for each of the top five questions, such as a shared document or a reference sheet at the point of use.
  6. Write the actual answer into that source of truth, verifying it rather than copying it from memory.
  7. Share the source of truth’s location with everyone who asked a version of that question in the two-week window.

Result: A short, ranked list exists with a written answer and a named location for each of the top recurring questions. You’ll know it worked when the same question stops routing back to the owner within the next two-week window.

Common mistake: Skipping verification and writing down the habitual answer instead of the confirmed one. Fix this by checking each assumed answer against its actual source, a contract, a policy, a current price list, before finalizing it.

If it goes wrong: If the same questions keep coming back after the source of truth is published, the problem is usually that no one knows it exists, so pair the document with a short announcement of where to find it.

This is a generic illustration of the process, not a report of a specific client result.

FAQs

How do I know if something is owner-only knowledge?

You know it’s owner-only knowledge if an employee has to ask you directly, by text, call, or in person, rather than finding the answer written down somewhere. A good test is to ask whether a new hire with no prior history at the business could find the answer without interrupting anyone. If the answer only exists because you remember it, it belongs on the list.

What is a source of truth in a small business?

A source of truth is the single place where a correct, current answer lives, whether that’s a shared document, a policy sheet, or a field in your scheduling software. The point of naming one source is to stop an answer from existing in multiple places with slightly different versions, which is what causes two employees to tell a customer two different things.

Why do the same questions keep coming back to me?

The same questions keep coming back because the answer has never been moved out of your memory and into a written, shared location that others can check on their own. Each time you answer from memory instead of pointing to a document, the next person with the same question still has nothing to check first, so the interruption repeats indefinitely.

How long does it take to build this list?

The raw list can be pulled in one sitting, by reviewing two weeks of texts, calls, and voicemail from a phone and call log. Sorting and ranking that raw list by repetition and risk takes additional time, but the initial capture step is intentionally fast and doesn’t require special software.

What’s the difference between owner-only knowledge and a trade secret?

Owner-only knowledge is operational detail, like a pricing exception or a vendor substitution rule, while a trade secret is proprietary information the business deliberately protects from competitors. Owner-only knowledge is rarely sensitive. It’s simply undocumented, meaning no one wrote it down, not that it was ever meant to be kept confidential.

Should I document every question on my list right away?

No single list item needs to be documented immediately unless it’s both frequent and high-risk, so rank the list first and start with the items that combine the two. Low-frequency, low-risk questions can wait, since the time spent documenting them may exceed the time saved by having them written down.

Can this process work for a solo owner with no employees yet?

Yes, because the same two-week review surfaces decision rules you’ll eventually need to hand off, even if no one is asking you those questions yet. Building the list early means the source of truth already exists by the time you bring on the first employee who would otherwise be asking you directly.

Next Steps

Building this list by hand tells you what’s undocumented. It doesn’t always tell you why certain gaps keep reappearing even after you’ve written the answer down once. See how a Systems Review finds what only you know: https://qualify.greatlakesbusinesssupport.com/systems-review

owner-only knowledgebusiness operationsdocumentationdelegationstandard operating procedures
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.