There is a strange compliment hidden inside a lot of owner dependence.
People keep bringing you problems because you are good at solving them.
You see things faster.
You recognize patterns they miss.
You remember what happened three years ago.
You know which customer is actually dangerous.
You can tell when an employee’s explanation does not quite add up.
You understand the economics.
You know which detail matters and which one is noise.
After twenty or twenty-five years, you should be better at some of this than everybody else.
That is not the problem.
The problem is when the company keeps using twenty-five years of experience to solve problems that should no longer require twenty-five years of experience.
A scheduling exception.
A routine customer dispute.
A familiar pricing decision.
A normal personnel issue.
The same question you answered last month.
And six months before that.
Your best thinking is valuable.
Which is precisely why the business should stop spending it so cheaply.
Some problems deserve the owner
There are decisions I would expect an experienced owner to make.
A major acquisition.
A large capital allocation.
Changing the company’s strategic direction.
Hiring or removing a critical executive.
Entering a new market.
Taking a risk that could materially damage the company.
A complicated situation where the facts are genuinely unusual.
Those decisions may deserve decades of accumulated judgment.
That is one of the reasons the owner is valuable.
But then there are questions like:
Can we give this customer a $400 credit?
Should we work Saturday to catch up?
Can this manager approve another technician?
What do we do when an employee is late three times?
Can we make this pricing exception?
If those decisions routinely require the same person who decides how millions of dollars of capital should be deployed, something is probably wrong.
Not necessarily with the owner.
With the way the organization is using him.
Owners are usually very protective of expensive company resources.
You would not use a $500,000 machine for work a $5,000 machine could do just as well.
Yet established companies routinely use their most experienced person to make decisions a properly designed organization should be able to make without him.
There is an escalation tax
Every time an ordinary problem travels upward unnecessarily, the company pays a tax.
The obvious cost is time.
Five minutes here.
Ten there.
A phone call.
A message.
A text.
An interruption.
But the time itself is not always the expensive part.
The expensive part is what happens to your attention.
You can be thinking through something important and then get pulled into:
Can we refund Mrs. Johnson $275?
You answer.
Then you have to reconstruct whatever was in your head before the interruption.
Do that ten or twenty times throughout a day and the owner may technically work eight hours while never having ninety uninterrupted minutes to think.
That matters.
Because the higher the owner’s role becomes, the more his valuable work depends on sustained thought.
Strategy rarely arrives in seven-minute fragments.
Neither does good capital allocation.
Neither does thinking deeply about people, positioning, risk or where the company should go next.
Routine escalation does not merely consume time.
It consumes the kind of attention from which higher-level work is made.
Ordinary problems can feel more productive than important work
There is another reason ordinary problems are so good at consuming an owner’s day.
They are satisfying.
A customer problem has an answer.
A scheduling issue can be fixed.
An employee question can be resolved.
Something was broken at 10:00.
By 10:15 it is not.
You did something.
You can see the result.
The higher-level work of ownership is often less satisfying in the moment.
Thinking about where the company should go next may produce no visible result today.
Developing a leader takes months.
Evaluating a strategic risk may leave you less certain than when you started.
Thinking through capital allocation does not give you the immediate satisfaction of fixing a customer problem.
So there can be a subtle temptation to stay where you already know you are effective.
Ordinary work lets a capable owner feel productive. Important work often requires him to tolerate ambiguity.
That is another reason the business can keep pulling him downward.
Not because he is lazy.
Because fixing things feels like work.
Thinking can sometimes feel like you did nothing at all.
The smartest answer can create the dumbest organization
This is one of the paradoxes of being good at solving problems.
The owner sees the answer.
He gives it.
Everybody moves on.
Efficient.
Except the company may have learned almost nothing.
The owner solved the problem.
The organization did not become any better at solving that kind of problem.
Then a similar situation appears two weeks later.
Someone asks again.
The owner answers again.
And because he answers quickly, there is never much pressure to improve the organization.
The owner’s competence becomes the company’s shortcut.
That can go on for years.
The smarter and faster the owner solves ordinary problems, the easier it is for the company to avoid learning how to solve them.
And if every difficult question ends with the owner, the company gets the answer without acquiring the ability that produced it.
That is where decision debt begins.
Decision debt
There is a form of debt that never appears on the balance sheet.
Suppose a customer problem happens.
You solve it.
The customer is handled.
Everyone moves on.
But the company still does not know how to handle that category of problem the next time.
The instance was solved.
The underlying decision was not.
So it returns.
Another customer.
Another manager.
Another interruption.
You solve that one too.
Nothing changes structurally.
It returns again.
That is decision debt.
Decision debt is what accumulates when today’s problem gets solved without making tomorrow’s version easier.
The owner paid today’s bill with his judgment.
But the organization never eliminated the future obligation.
Like other forms of debt, it compounds.
More customers create more occurrences.
More employees create more questions.
More locations create more variations.
The problem that required five owner decisions a month eventually requires twenty.
Each one seems small.
Together they can consume the owner.
A hard decision should become an easier decision next time
The first time something unusual happens, maybe it genuinely deserves you.
Fine.
But once you solve it, the company should get something from your answer besides today’s answer.
A principle.
A boundary.
A process.
A threshold.
A pricing rule.
A piece of institutional memory.
A manager who now understands how to think about it.
Something.
Because a mature company should get smarter whenever an experienced person solves a difficult problem.
Yesterday’s hard decision should become tomorrow’s easier decision.
If the tenth occurrence requires the same amount of owner thought as the first, the organization did not learn very much from the first nine.
The opposite of decision debt is a decision asset
A good owner decision should sometimes produce two things:
today’s answer
and
tomorrow’s decision asset.
A decision asset is whatever remains after the immediate problem disappears.
It might be:
a principle,
an approval limit,
a pricing threshold,
a process,
a training example,
a new data point,
a decision tree,
a dashboard,
a documented precedent,
or a manager who now understands the reasoning well enough to handle the next one.
The exact form does not matter.
What matters is that the next occurrence requires less owner thought.
That is how the organization begins retaining the value of your experience.
A solved problem should leave something behind
This may be one of the simplest operating habits an owner can develop.
After solving a recurring problem, ask:
What should exist now that did not exist before this happened?
Maybe the answer is nothing.
Some situations really are unique.
But often something should remain.
If you resolve the same pricing question repeatedly, perhaps a pricing boundary should remain.
If you solve the same customer exception repeatedly, maybe a service principle should remain.
If the same employee problem keeps reaching you, maybe management clarity should remain.
If somebody keeps asking for information you have in your head, maybe the information should remain somewhere other than your head.
The point is not documentation for the sake of documentation.
The point is organizational memory.
A solved problem that leaves nothing behind is easy for the company to turn back into a new problem.
Experience is wasted when the company cannot reuse it
Owners accumulate an enormous amount of knowledge that is difficult to see.
Not just facts.
Patterns.
You know that one kind of customer complaint usually means something else is wrong.
You know a certain margin looks good until labor hits.
You know which employee behavior tends to become a larger problem.
You know that a particular kind of opportunity is usually a distraction.
You know when a salesperson’s forecast is too optimistic.
You know what happens when production gets more than two weeks behind.
That knowledge has economic value.
But if it exists only as instinct inside you, the company can use it only when you are available.
That makes experience personal.
A stronger company makes more of that experience reusable.
Not every instinct can be written down.
Not every judgment should become an SOP.
But far more can be transferred into principles, information, boundaries and organizational memory than most companies ever attempt.
Rules are not the same thing as judgment
This is where companies can overcorrect.
The owner gets tired of questions.
So the business writes a rule for everything.
Then you end up with a 200-page manual and employees who cannot think unless someone previously wrote a paragraph about the exact situation they are facing.
That is not maturity either.
The goal is not:
Replace judgment with rules.
The goal is:
Use rules, principles, information and boundaries so good judgment can happen without requiring the owner’s immediate involvement.
There is a difference.
A rule might say:
Never refund more than $500 without approval.
A principle might say:
We spend reasonable money to correct problems we clearly caused, but we do not pay customers simply to make unreasonable demands disappear.
The rule establishes a boundary.
The principle helps somebody think.
Strong organizations need both.
Principles carry more experience than procedures can
A procedure tells somebody what to do when the world behaves as expected.
A principle helps when it does not.
Businesses are full of exceptions.
A good manager does not need an SOP for every possible customer problem.
He needs enough clarity to understand:
what the company values,
what outcome matters,
which risks are acceptable,
how much authority exists,
and when a situation becomes serious enough to move upward.
The goal is not creating ten thousand answers.
It is transferring enough of the thinking behind the answers that competent people can handle the ten-thousand-and-first situation intelligently.
That creates a decision asset far more valuable than another checklist.
Repeated questions are data
Owners often experience repeated questions as annoyances.
I would look at them differently.
They are information.
If five people keep asking the same thing, there is probably something missing.
Maybe authority is unclear.
Maybe the policy is unclear.
Maybe the necessary information is unavailable.
Maybe two priorities conflict.
Maybe a manager has not been trained.
Maybe the process itself generates exceptions.
Maybe everybody actually knows the answer but nobody believes he is allowed to act on it.
Those are different problems.
The individual question is not the important thing.
The repetition is.
Every repeated escalation is telling you something about the design of the organization.
Stop answering the same question as though it is new
Suppose a manager asks:
Can I approve overtime this weekend?
You answer yes.
Two weeks later:
Can I approve overtime this weekend?
Yes.
Next month:
Can I approve overtime this weekend?
At some point, the problem is no longer overtime.
The problem is that the company has failed to resolve the decision structurally.
Maybe the manager needs authority within a labor target.
Maybe overtime is acceptable when backlog reaches a certain point.
Maybe gross margin needs to remain above a floor.
Maybe there is a production principle that should guide the decision.
But repeatedly asking the owner is not a process.
It is decision debt being serviced one interruption at a time.
The first escalation may be a decision problem. The fifth is probably something else.
The first occurrence:
We have never seen this before. What should we do?
Reasonable.
Second:
This looks like the last situation. Does the same thinking apply?
Also reasonable.
Fifth:
What should we do?
Now I would start asking why the company still does not know.
Not angrily.
Diagnostically.
What failed to transfer?
Information?
Authority?
A principle?
Training?
Confidence?
A system?
That’s how you stop treating recurring problems as isolated events.
And start paying down decision debt.
Growth makes decision debt expensive
This is one reason growth can make a company feel dramatically heavier.
At $2 million, an owner can personally absorb a surprising amount of bad organizational design.
He remembers everything.
Approves everything.
Knows every employee.
Fixes every exception.
Then the company reaches $5 million.
Or $10 million.
The same habits remain.
Only now there are twice as many situations.
The owner thinks:
Why has this business become so difficult?
Part of the answer may be that growth did not create all the complexity.
Growth exposed all the places where the organization had been borrowing the owner’s brain.
The owner subsidy grew.
And the decision debt came due.
This is different from delegation
Delegation asks:
Who should own this decision?
Decision debt asks:
Why does this category of decision still require fresh thought every time it appears?
Those are related questions.
But they are not the same.
Sometimes the solution is developing a person.
Sometimes it is defining a principle.
Sometimes it is changing a process.
Sometimes information needs to become visible.
Sometimes authority needs to become explicit.
Sometimes the recurring decision should disappear entirely because the underlying process is badly designed.
The point is not simply to push the question down the org chart.
It is to make the company better at the category of problem.
That is organizational learning.
Not every decision should move downward
None of this means pushing every decision as low as possible.
That is another slogan that sounds better than it works.
Some decisions belong high in the organization.
Because the downside is large.
Because they cross several departments.
Because they involve reputation.
Because they alter strategy.
Because they commit meaningful capital.
Because the organization sees only part of the information while the owner sees the whole.
The objective is not maximum decentralization.
It is appropriate decision placement.
The right decision.
Made by the right person.
With the right information.
At the right level.
And with the company learning something from important decisions as they happen.
Your best thinking should be reserved for problems that deserve it
Imagine two owner workdays.
In the first, you make thirty decisions.
Twenty-five are things a capable organization could have handled or already learned how to handle.
Five genuinely required you.
In the second, the company handles the twenty-five.
You spend most of your day on the five.
Same owner.
Same experience.
Same eight hours.
Completely different economic value.
That is what leverage eventually looks like for an experienced owner.
Not merely doing less.
Using yourself differently.
The owner should become a scarce resource
This can sound strange because most founders spent years doing the opposite.
In the beginning, you were everywhere.
Everybody could get you.
Every problem deserved you because there was nobody else.
That was appropriate.
But as the company matures, access to owner-level judgment should become more intentional.
Not because you want to act important.
Because the resource actually is important.
If twenty-five years of experience is freely available for every $200 decision, the company will happily consume twenty-five years of experience on $200 decisions.
Organizations use the resources made easily available to them.
Part of maturing the company is teaching it:
This problem does not deserve that resource.
Audit the decisions that keep coming back
For one week, pay attention every time somebody asks you to make a decision.
Do not try to fix everything yet.
Record it.
Then ask five questions:
1. Has this type of decision reached me before?
2. Did it genuinely require owner-level judgment?
3. What information was missing?
4. What principle, authority or capability would have allowed this to happen without me?
5. What decision asset should exist after this is resolved?
Then sort the decisions into three buckets:
Owner-level: It genuinely belongs with you.
Capability gap: Someone else should eventually be able to handle it, but the judgment has not been developed yet.
System or clarity gap: The organization should not need fresh owner judgment for this at all.
Now look for repetition.
You may discover that what felt like twenty separate interruptions was really three structural problems.
That is useful.
Because one improvement can eliminate dozens of future decisions.
A mature company should compress experience
You may spend twenty years learning a lesson.
Your organization should not need twenty years to learn it again.
A principle can compress fifty customer situations.
A pricing model can compress hundreds of pricing decisions.
A hiring scorecard can preserve years of painful hiring lessons.
A dashboard can compress thousands of data points into something people can actually act on.
A capable manager can absorb dozens of daily decisions.
A precedent can prevent the same debate from starting over every month.
That is what a mature organization does.
It turns accumulated experience into something reusable.
And the more your experience becomes reusable, the less the company needs the original owner present for every application of it.
Imagine a Monday morning where the company knows more
Imagine getting to work Monday morning.
No one needs you for the normal pricing questions.
Customer exceptions are handled within clear boundaries.
Managers resolve ordinary personnel issues.
The information people need is available without asking you.
The company remembers what happened the last time.
You still get involved.
But when you do, it is because something is genuinely difficult.
Unusual.
Consequential.
By noon, you have spent two uninterrupted hours thinking about something that could materially change the company.
Maybe an acquisition.
A new market.
A major executive hire.
A strategic risk.
Something that actually deserves the experience you spent decades accumulating.
That is not an owner doing less.
That is the company finally using the owner for what he is actually good for.
Your role should move toward novelty
Eventually, the owner should spend more time where the company has not already learned the answer.
The unfamiliar acquisition.
The new market.
The executive who could change the company.
The emerging threat.
The unusual opportunity.
The difficult strategic trade.
Problems without precedents.
Decisions where the answer really is not obvious.
That is where deep owner experience becomes unusually valuable.
Ordinary decisions should increasingly be handled using the capability created from yesterday’s extraordinary ones.
A mature business converts yesterday’s hard thinking into today’s organizational capability.
That may be one of the clearest signs that the company is actually growing up.
The company should get smarter when you solve something
That is the standard I would use.
Not only:
Did we fix today’s problem?
Also:
Did solving today’s problem make tomorrow’s version easier?
If yes, your judgment created leverage.
You paid down decision debt.
Maybe you even created a decision asset.
If no, you may simply have rented your brain to the company one more time.
There will always be exceptions.
Always surprises.
Always problems worth escalating.
That is business.
But the same ordinary problems should not require your best thinking forever.
Because your experience is too valuable for that.
And because a mature company should eventually be able to carry more of what you know without carrying you into every decision.