The Decision Log: How to Find Out Which Decisions Actually Need You
The short answer
You are the bottleneck when routine decisions require you, not when hard ones do. The fastest way to find out is not reflection — it is a log. Write down every decision that reached you over five business days, sort each into three buckets, and the pattern is usually undeniable by Wednesday. Most owners discover that the majority of what reaches them is not owner work at all. It is an undocumented threshold.
This is the WHO question in the Five W diagnostic, and it is where most engagements start.
Why does this matter right now?
Because the environment is punishing slow decisions. In the Federal Reserve's 2026 Small Business Credit Survey, which collected 6,525 responses from employer firms with 1 to 499 employees between September 3 and November 14, 2025, revenue growth expectations fell to an index value of 33, down from 39 a year earlier, and employment expectations fell to 23 from 26 — the lowest readings since the 2020 survey (Federal Reserve Small Business Credit Survey).
The same survey found reaching customers and growing sales was the most commonly reported operational challenge, with hiring and retaining qualified staff second. Both of those are throughput problems. When demand is soft, the companies that win are the ones that can decide and act faster than the market shifts — and a business where every decision queues behind one person cannot do that.
How do you run the decision log?
For five business days, write down every decision that reached you. Not tasks. Decisions — moments where someone needed a yes, a no, or a number from you. Do not filter. Do not improve your behavior because you are measuring it.
At the end of the week, sort each entry into one of three buckets:
Only you can decide. Capital allocation, partnerships, senior hires, strategic direction, anything that changes what the company is. This is real owner work.
Someone else could decide, with a rule. Pricing exceptions, discounts, refunds and credits, scheduling conflicts, vendor selection under a threshold. The decision is not hard. The authority is just undefined.
Someone else should already be deciding. It reached you out of habit, deference, or because it always has.
What the three buckets actually tell you
In most profitable-but-plateaued companies, bucket one is small — often fewer than five entries in a week. Buckets two and three are where the volume lives.
That distribution is good news, and owners rarely hear it that way. A large bucket one would mean the business genuinely requires you and change would be slow and expensive. A large bucket two means the constraint is documentation, not capability. Your team is not incapable of deciding. Nobody ever told them where their authority ends.
Bucket three is the most uncomfortable and the fastest to fix. Those decisions reach you because at some point you wanted them to, and nobody updated the norm.
How do you write a decision rule?
A usable decision rule has four parts, and it fits on one line:
The trigger. What situation invokes this rule.
The boundary. The range inside which someone else decides without asking.
The owner. The named person, not a role or a committee.
The escalation. What happens outside the boundary, and to whom.
Example shape: when a client requests a scheduling change inside 48 hours, the operations lead approves it at no charge up to one reschedule per project; beyond that it escalates. That single line removes a category of interruption permanently.
Start with your top three recurring exception types. In our experience across construction, landscaping, healthcare services, insurance and food service, pricing exceptions, scheduling conflicts, and refunds or credits account for most of bucket two. Writing three rules typically returns several hours a week to the owner — and, more importantly, returns those hours permanently, because a rule does not need to be re-decided.
What usually goes wrong
Delegating the task instead of the decision. Handing someone the work while keeping approval over the outcome moves effort but not load. The queue still ends at you.
Writing rules nobody can find. A rule that lives in a conversation is not a rule. It needs one location everyone knows.
No tolerance for a wrong call. If the first decision made without you gets overturned publicly, the rule is dead and everything routes back through you — this time with resentment attached.
Skipping the log and going from memory. Memory over-weights the dramatic decisions and forgets the twenty small ones. The log exists because your recollection is not the data.
Frequently asked questions
How long should the decision log run? Five business days is enough to see the pattern. Longer produces better data but rarely changes the conclusion, and the delay costs more than the precision is worth.
What if my week was unusual? Run it anyway. Owners describe most weeks as unusual, which is itself a finding — if every week is an exception, the exceptions are the process.
Should my team know I am logging decisions? Yes. Tell them it is about finding where the business is slowed by needing you, not about evaluating them. Hidden measurement reads as surveillance and corrupts the data.
What if bucket one really is large? Then the constraint is structural rather than procedural — usually a missing layer of leadership. That is a hiring and design conversation, not a documentation one.
Where CINCO fits
The decision log is the first exercise in the WHO stage of our Strategic Growth Partnership, where we spend twelve months building the structure the log exposes. If the log surfaces decisions stuck because information lives in three systems and nobody trusts any of them, that is a technology and digital assets problem instead. Run the log first, then start here.
Next in this series: which service line actually produces the profit.
Source: Federal Reserve Small Business Credit Survey, 2026 Report on Employer Firms (fielded September 3 to November 14, 2025). Client examples are described at the industry level only.
Comments