How to Measure Owner Dependence in Your Business
Ryan thought things were getting better.
He wasn't opening the shop anymore.
His managers ran the morning meeting.
He'd stopped working most nights.
He'd even started leaving early on Fridays.
That felt like progress.
Then one Friday afternoon, his operations manager, Jess, asked him a question.
“How many times did we need you today?”
Ryan shrugged.
“Not much.”
Jess pointed at his phone.
“Look.”
So he did.
At 9:12, sales had asked him to look at a proposal.
At 9:47, somebody needed approval for a customer credit.
Around 10:30, two managers needed him to settle a schedule problem.
A customer called him before lunch.
After lunch, a supervisor wanted help with an employee.
Then somebody needed the story behind an old customer deal.
Before Ryan left, the team asked him which project should go first next week.
Ryan looked up.
“Huh.”
None of it had felt like work.
A few minutes here.
A quick answer there.
He'd still left early.
Jess smiled.
“You left early. The business didn't.”
That one stung a little.
Because she was right.
The Short Answer
You don't measure owner dependence by counting how many hours the owner works.
You measure it by watching what happens to the business when the owner isn't involved.
What waits?
What slows down?
What can't move?
The question isn't just:
“How much am I doing?”
It's:
“What still needs me before the business can move?”
That's how you start seeing owner dependence.
Want a faster starting point? Take two minutes and see how the Scorecard works.
Ryan Had Been Measuring the Wrong Thing
Ryan had been proud of his calendar.
And he should've been.
A year earlier, he'd been working all the time.
Now he wasn't.
But Jess had shown him something his calendar couldn't.
Ryan was doing less work.
He was still required for a lot of work.
Those aren't the same thing.
He didn't build the proposal.
He approved it.
He didn't make the schedule.
He settled the fight about it.
He didn't handle the customer issue.
He became the person everybody wanted when the answer got uncomfortable.
Ryan wasn't doing all the tasks anymore.
But a lot of those tasks still had a string tied to him.
That's what they needed to measure.
Because an Owner Bottleneck isn't about whether the owner works hard.
It's about how much normal business still requires that owner personally.
So Ryan Tried Something Simple
Jess told him to stop guessing.
For the next two weeks, every time normal work came back to Ryan, he wrote it down.
Nothing fancy.
He kept a note on his phone.
When somebody needed him, he added a line.
“Chris needed price approval.”
“Jess asked about schedule.”
“Customer wanted me.”
“Needed to explain old deal.”
By the third day, Ryan thought he already knew the answer.
Jess told him to keep going.
So he did.
And something strange happened.
The little interruptions stopped looking little.
Patterns started showing up.
Sales kept coming back for the same kind of price decision.
Customer service kept asking about the same kinds of credits.
The schedule only got to Ryan when two good choices fought with each other.
Ryan hadn't been dealing with dozens of random problems.
He'd been seeing the same few problems over and over in different clothes.
One interruption was just a story.
Repetition showed the system.
“Why Did They Need You?”
A few days in, Ryan showed Jess his notes.
She read them.
Then she pointed to one.
“Why did they need you?”
Ryan looked at it.
“It says right there. Pricing.”
Jess shook her head.
“No. Why did they need you?”
Ryan paused.
He read it again.
The salesperson already knew what price they wanted.
They weren't asking Ryan to build the quote.
They wanted permission to go outside the normal range.
“Approval,” Ryan said.
Jess nodded.
She pointed to another.
“Customer wanted me.”
“Why?”
Ryan thought about it.
The customer had already talked to the account manager.
The account manager knew what had happened.
But the customer didn't feel settled until Ryan got involved.
“Trust, I guess.”
Jess pointed to the schedule problem.
Ryan already knew.
Neither manager knew who had the final say when two important jobs needed the same crew.
“Authority.”
Now the note was getting useful.
Because “sales needed me” didn't tell Ryan much.
Neither did “operations needed me.”
The better question was:
What did the business need from me that it couldn't carry on its own?
That got much closer to the truth.
Not Every Call Counted
Ryan almost made another mistake.
He started counting everything.
An employee asked what he thought about a new truck.
A manager sent him an update.
A salesperson asked him to join a call with a huge new prospect.
Ryan wrote all of it down.
Jess crossed some of it out.
“Why doesn't this count?” Ryan asked.
“Because they didn't need you.”
Ryan frowned.
“They called me.”
“That's not the same thing.”
She was right again.
The salesperson could've handled the call without Ryan.
Ryan joined because his experience might help.
That's contribution.
The manager who sent the update wasn't waiting for Ryan to do anything.
That's communication.
Healthy companies don't stop talking to the owner.
That's not the goal.
The question is whether the business needs the owner before normal work can keep moving.
Ryan could be useful without being required.
In fact, that's what he wanted.
He didn't want to become less valuable.
He wanted the business to become less dependent.
Then Ryan Found the Work Nobody Asked Him to Do
About a week into the experiment, Ryan thought his note was pretty complete.
Then Jess asked:
“What about the stuff nobody asks you for?”
Ryan didn't know what she meant.
So she gave him an example.
That morning, Ryan had walked through the shop and noticed a job was falling behind.
Nobody had called him.
Ryan just saw it.
He found the supervisor.
They moved a person.
Problem solved.
Ryan hadn't written it down.
Later that afternoon, he noticed a good customer hadn't gotten an update.
Nobody asked him to check.
He just remembered.
So he sent the message.
That wasn't in the note either.
Then there was the project Ryan checked every Thursday because, if he didn't, things had a habit of slipping.
Nobody officially needed Ryan to do it.
But if Ryan stopped noticing, remembering, checking, and following up, some of those things might not happen.
That counted too.
The dependence wasn't always loud enough to ring his phone.
Some of it lived quietly in Ryan's head.
That's often the hardest kind to see.
Nobody says:
“Ryan, we need your memory to make this business work.”
They don't have to.
Ryan remembers.
So the business keeps moving.
Until he doesn't.
The Quiet Phone Test
Ryan decided to try something.
The next Friday, he told the team he'd be unavailable for most of the morning.
Real emergency?
Call him.
Normal business?
Handle it.
Then Ryan did something that was much harder than it sounds.
He stopped checking.
No quiet peek at Slack.
No answering an email because “it'll only take a second.”
No seeing a text and fixing the problem before anybody else had to think.
He left it alone.
Around noon, he came back.
Nothing had exploded.
Ryan smiled.
“See?”
Jess wasn't impressed.
“What happened?”
“Nothing.”
“No. What happened?”
So they looked.
A quote hadn't gone out.
One manager had pushed a schedule decision until the afternoon.
A customer issue had been handled.
Good.
A small credit had been approved without Ryan.
Also good.
The team had made a couple of calls Ryan would've made differently.
But they were reasonable calls.
That mattered too.
Ryan finally saw why a quiet phone wasn't enough.
The goal wasn't silence.
The goal was capability.
If nobody called Ryan because everybody was sitting around waiting for Monday, that wasn't independence.
It was just a quieter Owner Bottleneck.
The Pattern Finally Had a Shape
At the end of two weeks, Ryan and Jess looked through everything he'd written down.
The issues weren't all the same.
Some came back because people weren't sure who could make the decision.
Some came back because customers trusted Ryan more than the company.
Some came back because important knowledge still lived in Ryan's head.
Some showed that managers had work, but not enough ownership yet.
And some showed how much business value was still tied to Ryan personally.
Those are the five places I look for owner dependence: Decision, Sales, Operations, Team, and Value.
Ryan didn't need to fix all five.
He needed to find the one creating the most trouble now.
That was the point of measuring.
Not to create a giant report.
To find where to start.
The Number Wasn't the Point
Ryan had logged a lot of owner touches.
At first he wanted to know if the number was bad.
Jess asked a better question.
“Which ones matter?”
There isn't some magic number where seventeen owner touches means you're fine and eighteen means you've got a problem.
One strange decision that comes to you once a year may belong with you.
A two-minute approval that comes back every day may matter much more.
Ryan stopped worrying about the total.
He looked for the repeated dependency that was slowing the business down.
That pointed him right back to pricing.
Ryan Found His First Attack
Chris, his sales manager, knew how to price normal work.
He understood the customer.
He understood margin.
He wasn't asking Ryan because he couldn't think.
He was asking because nobody had made the line clear.
How far could Chris go?
What really needed Ryan?
When was something unusual enough to bring to the owner?
Most of those answers still lived in Ryan's head.
There was the dependence.
So they started there.
Not with the whole company.
Pricing.
Ryan and Chris made the boundary clearer.
Chris got more room.
Ryan kept the few decisions that really belonged with him.
Then they kept watching.
Two weeks later, fewer normal pricing decisions were coming back.
Quotes were moving faster.
Chris was making more of the calls himself.
That was progress.
Not because Ryan's phone was quieter.
Because the business could now carry something it used to need Ryan for.
And Ryan wasn't done.
He'd just moved one dependency enough to start seeing what might need attention next.
That's the bigger job.
The business gets stronger.
Then you look again.
If you want to see what owner dependence like this may actually be costing you, read What Does an Owner Bottleneck Actually Cost?.
Start With What Keeps Coming Back
You don't need a giant dashboard to measure owner dependence.
Pay attention to the normal things that keep finding their way back to you.
Then ask one question:
Why did this need me?
Not why did they call me.
Not why was I helpful.
Why did the business need me before this could move?
Watch long enough and the pattern usually starts showing itself.
Then don't attack everything.
Find the dependence that matters most.
Figure out what the business is missing there.
Give it what it needs.
Then look again.
Find it. Attack it. Level up. Repeat.
Want a Faster Place to Start?
If you're not sure where to look first, the Owner Bottleneck Scorecard can help you see where owner dependence is showing up across Decision, Sales, Operations, Team, and Value.
It won't tell you everything that's wrong with the business.
That's not its job.
It'll help you see where the business may still depend too much on you.
And that's a much better place to start.
