If the Same Question Reaches You Twice, Document the Answer Once

The first time someone asks you a question is information. The second time is a signal. The third time is a system problem.

Pain: The same question keeps reaching you because the answer only lives in your head.

Almost every owner of a growing manufacturing or engineering business has the same daily experience. A steady drip of questions that come to you because the answers are only in your head. A pricing exception. An override for a specific customer. The reason a particular machine setting is set the way it is. None of these are big problems individually. Each one takes you out of whatever you were doing, costs the team a few minutes of waiting, and resets quietly. You absorb the cost and move on.

The cost is real, even though it is invisible. Every question that reaches you twice is a small piece of the business that depends on you to function. It is operational risk in its purest form: knowledge that has not been externalised.

Fix: Next time a question reaches you twice, write the answer down in two or three sentences and share where the team checks.

Two things happen the moment you do this. First, that specific question stops coming back to you. Second, the team picks up a new pattern: there is a place we check before asking the founder. Repeat the move a few dozen times and you have built a small reference library that handles the steady-state questions without your involvement.

Operational risk reduction is rarely about big initiatives. It is about turning what is in your head into what is on the page, and that is exactly what Beyond the Founder: The Silent Killer of Scaling Businesses walks through in more depth.

What repeated question reached you this week that could have been documented the first time you answered it?

More in the Friday Fix series.