Back to Insights

    Which Decisions in Your Business Only Exist in Your Head?

    The decisions that never got written down are the ones that stop work when you are unreachable. Three categories to inventory in an afternoon, before you hire around the problem.

    August 18, 20266 min read
    workflow design
    operations
    smb operations
    owner-led business
    delegation
    process documentation
    operational efficiency

    Why does everything stop when I am unreachable?

    Because a set of decisions in your business exists only in your head, and nobody can look them up. Not tasks, decisions: the judgment calls that determine what happens when a situation does not match the normal path.

    Work does not stop because your team lacks ability. It stops because they hit a fork nobody documented and correctly decided that guessing was riskier than waiting.

    How would I even find them?

    Picture an owner who goes off-grid for five days to test whether the shop can run without him. It makes it to Tuesday. Then a customer changes specs mid-run and nobody knows how to reprice the job.

    That is the diagnostic. Not the outage, the specific thing that caused it. Every interruption you field is evidence of a decision that lives nowhere but with you, and the fastest inventory is to write down what people interrupt you about for two weeks.

    What are the categories that usually come up?

    Most of what surfaces falls into three buckets:

    • Pricing exceptions. When can someone discount, by how much, and what makes a job worth repricing mid-run.
    • Vendor and spend approvals. Who can commit money, up to what number, and which suppliers are pre-cleared.
    • Escalation and exception rules. What happens when an order is late, a customer is unhappy, or the normal sequence breaks.

    Three categories, one afternoon. That is genuinely the scope for most companies, which is why it is frustrating that it stays undone for years.

    Is this a people problem or a systems problem?

    Neither yet, and that is the useful part. It is a documentation gap, and it is the cheapest thing on the list to fix.

    Owners often jump straight to hiring an operations manager. That can work, but it is an expensive way to discover that the new hire also has to interrupt you, because the decisions still are not written down. Hiring around an undocumented decision just adds a person to the queue.

    What does writing it down actually look like?

    Two sentences per decision type, stating the threshold and who owns it past that point. Discounts under this figure, approve it. Above it, come to me. Rush orders inside this window, accept them. Outside it, ask.

    Resist the urge to make it a manual. A manual will not get written, and if it does it will not get read. A one-page list of thresholds gets used because it answers the question someone actually has at the moment they have it.

    What if the honest answer is that it depends?

    Then write down what it depends on. That is the real content.

    When an owner says a call is judgment, the judgment is usually two or three named factors weighed in a consistent order. Customer relationship, margin on the job, capacity this week. Naming those three does most of the work, even without a formula, because it lets someone else reason the way you would.

    How do I know it is working?

    The interruptions change shape. You stop being asked what to do and start being told what was done.

    That is the actual goal. Not fewer decisions reaching you, but fewer decisions requiring you. As of 2026, this remains the least expensive operational improvement available to most owner-led companies, and the one most likely to still be sitting undone next year.

    Curious how we think about operations work?

    Our alignment framework shows where strategy, work, and systems drift apart — and how to close the gap.

    See the framework

    Related Insights

    Yes, There Is an API. Does It Carry the Numbers You Need?

    The software has an API. The numbers you want may not be in it. What to ask before anyone promises an integration, and what an honest scope looks like.

    Why Can't We Use the Feature the Demo Showed?

    The demo showed it working. Your account does not. The three forms the demo gap takes, and the checks to run before you plan anything on a system.