I have a strange hobby. I travel the world and lift historic stones.

A few years ago I was in the Scottish Highlands working through a list of stones I'd wanted to lift for years. Long drives between farms. Bad weather. The kind of solitude you don't get in business.

At 12:30 in the morning, my phone rang. 4:30 PM back home.

One of my store managers was calling because he wasn't sure how to handle a customer issue.

My first reaction was annoyance.

This is ridiculous. He shouldn't need me for this.

My second reaction took longer, and it mattered more.

If a store manager I had hired, trained, and trusted with a multi-million-dollar operation couldn't make this call without me, that wasn't his failure. It was mine.

For years, I thought I was being a strong leader by staying constantly available. Phone always on. Every escalation routed through me. Every fire handled personally, no matter where I was in the world.

I wore it like a badge.

I told myself it meant I cared about standards. The truth was simpler: I didn't fully trust the business to operate without my judgment in the loop.

So I became the operating system the business ran on.

An operating system that has to be physically present to function isn't a system. It's a bottleneck with a job title.

When I came back from that trip, I started looking at my team differently.

There was one manager I'd quietly been frustrated with for months. Smart. Capable. Respected by his people. But he was hesitant. Slow to make decisions he should have been making on his own.

I had interpreted it as a leadership limitation.

It wasn't.

He knew what to do. He was afraid to do it.

He was afraid to make, and defend, a decision I wouldn't have made. So he escalated. He waited. He brought me decisions I should never have seen.

And honestly, he was right to.

Every time I overrode a manager's call, "helped" by stepping in too quickly, or inserted myself into a decision that should have stayed local, I taught the organization the same lesson:

Waiting for me was safer than ownership.

That's the part most founders and executives miss.

You cannot evaluate your team's behavior until you've ruled out the possibility that the behavior is a rational response to you.

Founder dependency rarely feels dangerous from the inside. It feels responsible. It feels like high standards. It feels like leadership.

But there's a simple test.

If you disappeared for thirty days, no calls, no Slack, no email, would the business grow, hold steady, or stall?

Most leaders know the answer immediately.

Decisions would pile up. Revenue would soften. Customers would feel the hesitation. The business would survive temporarily on momentum and muscle memory while everyone waited for the founder or executive to come back and restart the engine.

That's not a scalable business.

That's centralized decision-making disguised as operational excellence.

The fix is not "more delegation." Most leaders misunderstand delegation entirely. They hand off tasks while retaining authority, then wonder why nobody takes ownership.

Real scale only happens when authority transfers with responsibility.

That means allowing people to make decisions you wouldn't have made yourself. Coaching judgment instead of controlling outcomes. Building leaders instead of creating approval chains.

It also changes how you respond when mistakes happen.

If someone on your team makes a reasonable decision that you personally wouldn't have made, and your reaction is to subtly punish the outcome, you've just trained hesitation into the organization.

If you coach the decision without reclaiming authority, you build capacity.

The systems part is straightforward.

The difficult part is admitting that the thing you've been calling leadership may actually be the ceiling on the business.

If your team keeps waiting for you, they are listening carefully to how you've trained them. Most founders aren't willing to teach them something different. That's why most businesses never scale past their founder.