Even when information is accessible, decisions can pile up in ways that slow the business and exhaust the people making them. This chapter examines how decisions flow through a business, why that flow often concentrates at you, and what it would mean to distribute decisions more effectively.
The Problem Is Not Bad Decisions
When you reflect on what makes your work difficult, the weight of decision-making is often near the top. Every day brings questions that require judgment: how to handle this customer situation, whether to approve this expense, how to prioritize competing demands. The decisions accumulate, and by the end of the day, the capacity to think clearly is diminished.
The common assumption is that the difficulty lies in making good decisions. But most decisions, taken one at a time, are straightforward enough. The difficulty is the volume. You make dozens or hundreds of small decisions each week, and that volume creates a system-level burden: attention that could be directed toward high-value work is instead absorbed by questions that do not require your unique judgment.
The pattern is recognizable. The inbox fills with “quick questions” and “just checking” messages. Employees stop by with requests that seem small but require approval. Decisions that should take seconds accumulate into hours of fragmented attention. No single question is unreasonable; taken together, they form a current that pulls you away from work that matters more.
Why Decisions Concentrate at the Owner
Many of the decisions that reach you should not require your involvement. A routine situation, a standard expense, or a choice between options that all fall within acceptable bounds: these decisions arrive at your desk not because they require your unique judgment, but because the structure of the business has not defined who else can make them.
This connects to the earlier chapters. When information is scattered, decisions flow to whoever has the necessary context. When authority has not been distributed and processes are unclear, decisions flow to whoever can resolve the ambiguity or has the power to approve. In each case, that person is you.
The result is that you spend significant time on decisions that do not benefit from your involvement. A routine approval takes the same amount of attention whether it is made by you or by someone else. But when routine approvals flow to you, they consume capacity that could be spent on decisions that actually require judgment, experience, or strategic thinking.
Routine Decisions and Judgment Calls
Not all decisions are the same. Some require genuine judgment: weighing competing considerations, interpreting ambiguous situations, or making trade-offs that depend on values or priorities. These decisions benefit from experience, context, and careful thought. They are the decisions that owners should be making.
Other decisions are routine. They follow a pattern. Given the relevant information, the right answer is predictable. Should this expense be approved? If it falls within the budget and serves a legitimate purpose, yes. How should this customer request be handled? If there is a standard process and the request fits within it, follow the process.
Routine decisions feel like decisions because someone has to make them. But they do not require judgment in the meaningful sense. They require information and a rule. When the information is available and the rule is clear, the decision can be made by anyone who has access to both. It does not need to wait for you.
The distinction matters because it suggests where relief is possible. Judgment calls will always require human attention, and often yours specifically. Routine decisions do not. If routine decisions can be made without your involvement, your attention is freed for work that actually requires it.
Designing Decisions Out of the Flow
One way to reduce the volume of decisions is to establish defaults. A default is not merely a suggestion; it is a designed absence of a decision. Instead of requiring someone to choose each time, the default determines what happens in the ordinary case. Decisions are only required for exceptions.
Defaults work because most situations are not exceptional. A standard payment term, a standard response time, or a standard process for handling a particular type of request. When these are established, the decision has already been made for the typical case. The person handling the situation does not need to decide; they need only recognize that the situation is typical and apply what has already been determined.
Guardrails serve a related purpose. A guardrail is a designed boundary of authority: it defines where someone can act without seeking approval. An employee authorized to resolve customer complaints up to a certain value does not need to ask permission for complaints below that threshold. They have authority to act within the guardrail. Only situations that exceed the boundary require escalation.
Together, defaults and guardrails are forms of system design. They reduce the number of decisions that require active thought not by automating judgment, but by defining in advance what should happen in predictable situations. The goal is not to remove humans from the process, but to reserve human attention for the situations that genuinely need it.
Protecting Judgment, Not Replacing It
The word “automation” sometimes raises concerns for business owners. It can suggest replacing human judgment with rigid rules, or removing the personal touch that makes a small business distinctive. These concerns are reasonable, but they rest on a misunderstanding of what is being proposed.
The goal is to reduce the number of decisions that require active attention so that attention can be focused where it is most valuable. A business that requires you to approve every routine matter is not more personal or more careful. It is slower, and it exhausts the person whose judgment matters most.
When routine decisions are handled through defaults and guardrails, your judgment is protected rather than replaced. You still make the decisions that require your experience and perspective. You simply stop making the decisions that do not.
The Three Flows Together
The three flows that shape how a business operates — work, information, and decisions — each have their own dynamics, but they are interconnected. Work stalls when information is unavailable. Information stays scattered when no one has defined where it should live. Decisions pile up when authority is concentrated. You remain at the center when all three flows route through you.
The next section turns from understanding these flows to designing systems that address them: what it means to build structure that fits the realities of a small business, with limited time, limited budget, and constraints that cannot be wished away.
