You Can't Empower People Without Giving Up Some Control

Why delegating work isn't enough to build a business that can operate without you

There is a complaint I hear from leaders all the time:

“My team won't take ownership.”

They don't make decisions without asking. They escalate problems that should never have reached the leader. They wait for approval. They hesitate. And eventually, the founder or executive gets frustrated and concludes that the team simply isn't ready for more responsibility.

But before we decide we have an ownership problem, there's another question worth asking:

What happens when people actually try to take ownership?

Do they have the authority to make meaningful decisions?

Do they understand what the business is trying to accomplish and what a good outcome looks like?

Do they have access to the information and context necessary to make the decision well?

Can they make a reasonable mistake without immediately losing the authority they were supposedly given?

Or does every important decision eventually find its way back to the leader?

Because if everything still comes back to you, you may not have a people problem.

You may have a decision-making design problem.

That was the conversation at the center of this week's Connection Lab: Why do leaders struggle to let go of decision-making?

And the more we talked, the clearer something became.

Empowerment isn't something leaders give people by telling them they're empowered.

It requires giving up some control.

Why leaders hold on

There are plenty of legitimate reasons leaders become reluctant to delegate decisions.

Sometimes they've trusted someone before and been burned.

Sometimes they're accountable for the consequences and aren't convinced someone else understands the stakes.

Sometimes they're simply better at making a particular decision because they have years more experience.

And sometimes leaders have never actually been taught how to lead.

We talked about how often people become managers because they were excellent individual contributors. The best engineer becomes the engineering manager. The best salesperson becomes the sales manager. The strongest accountant becomes the finance leader.

Then, suddenly, the skills that made them successful are no longer the skills the organization needs most from them.

Their value has to shift from:

I know how to do this.

to:

I know how to help other people become capable of doing this.

And there's another transition underneath that one.

Many individual contributors build their careers by becoming exceptionally good at solving technical challenges: problems where expertise, experience, established processes or known solutions can tell us what to do.

Leadership introduces a different class of challenge.

Trust. Motivation. Conflict. Accountability. Resistance to change. Competing priorities. Behavior change. Ownership.

These are often adaptive challenges. There isn't necessarily one correct answer an expert can identify and implement. Progress requires people to learn, change, exercise judgment, negotiate competing needs and develop new capabilities.

That means becoming a manager isn't simply a promotion into responsibility for more work.

It requires learning a different way to solve problems.

The instinct that made you valuable as an expert—see the problem, diagnose it, fix it—can actually become a constraint when your job becomes developing other people.

For some leaders, being the person with the answer has also become intertwined with what leadership means. They are the expert. They solve the hard problem. They make the call.

So relinquishing decision-making can feel like relinquishing authority—or even relevance.

But if every important decision still requires the leader, the organization can only move as quickly as that leader can think, respond and approve.

Eventually, expertise becomes a bottleneck.

Delegating work isn't the same as delegating authority

One distinction from our conversation kept coming back to me:

You can delegate a task without delegating any real ownership.

A leader can say:

“I want you to handle this.”

But what they actually mean is:

“I want you to do this exactly the way I would do it.”

That's not empowerment.

That's execution with a longer leash.

One Connection Lab participant, Nick, described delegation as giving someone responsibility and letting them run with it. The person may approach the problem differently. Their solution may not be identical to yours.

That doesn't automatically make it wrong.

Michael Sattler brought up another useful way to think about this. What happens when someone's solution is 75% of what you would have done?

Do you override them to get the other 25%?

Maybe sometimes you should. There are decisions where the risk, consequence or quality threshold requires it.

But often, the leader needs to ask a different question:

Is the additional 25% worth taking ownership of the decision away from this person?

Because every time you override a reasonable decision simply because it isn't your decision, you're teaching people something.

You're teaching them that ownership has limits.

Eventually, they learn to wait.

Capability has to be built

Of course, this doesn't mean leaders should simply hand people authority and hope for the best.

That's abdication, not delegation.

People develop good judgment by having opportunities to exercise judgment—with context, feedback, coaching and appropriate guardrails.

I shared a practice during the Lab that I've used throughout my career.

When someone brings me a plan that isn't quite there, I try not to immediately tell them what's wrong with it.

Instead, I start with:

“Talk me through your plan.”

Then I ask questions.

What are you trying to accomplish?

What assumptions are you making?

What happens if this goes wrong?

Who else is affected?

What haven't we considered?

Often, somewhere in that conversation, the person sees the gap themselves.

That's a very different outcome from me simply correcting their work.

In one scenario, I've made the decision.

In the other, I've helped build someone who can make better decisions next time.

That distinction matters.

Because the goal isn't simply to get today's decision right.

The goal is to increase the organization's capacity to make good decisions tomorrow.

Context before control

But coaching alone isn't enough.

One of the most important responsibilities leaders have is making sure people understand enough about the organization to make decisions on its behalf.

Years ago at NPR, I encountered this with engineering teams.

There was frustration that engineers didn't always understand what customers actually needed.

But there was an obvious problem with that expectation:

We hadn't given them enough exposure to customers.

So we changed the system.

Engineers spent time working directly with customer service, answering calls and hearing what customers were actually experiencing.

Suddenly, the customer wasn't an abstract requirement on a backlog.

They were a person with a problem.

If we wanted engineers to make better customer-centered decisions, telling them to “think about the customer” wasn't enough.

We had to give them the context required to do it.

The same principle applies throughout an organization.

If you want people making decisions closer to where the work happens, they need to understand:

• What are we trying to accomplish?

• What matters most right now?

• What does success look like?

• What constraints are real?

• What tradeoffs are acceptable?

• Who is affected by this decision?

• When does this decision need to be escalated?

You can't ask people to make better decisions while withholding the context they need to make them.

Something interesting happens to accountability

One of the fears leaders have about distributed decision-making is that accountability will disappear.

I think the opposite can happen.

In a highly centralized organization, accountability tends to travel vertically.

Employee → Manager → Executive.

People look upward for permission, validation and resolution.

But when decision-making authority moves closer to the work, another form of accountability becomes possible:

peer-to-peer accountability.

If my decision affects your work, I need to consider that.

If our priorities conflict, we need to resolve it.

If I commit to something the team depends on, the team has a legitimate expectation that I'll deliver.

That changes the role of the manager.

The manager no longer needs to referee every disagreement or resolve every competing priority.

Instead, the manager helps create the conditions where people can work through those issues together.

This doesn't eliminate accountability.

It distributes it.

And that's an important organizational capability.

The leader's job has to change

This is ultimately why letting go of decision-making is so difficult.

It isn't merely a change in workflow.

It's a change in what leadership is for.

If leadership means being the smartest person in the room, having the answers and making the important decisions, then distributed decision-making feels threatening.

But there's another way to define the job.

The leader establishes direction.

The leader makes priorities clear.

The leader defines what success looks like.

The leader makes sure people have the information and resources they need.

The leader develops capability.

The leader establishes guardrails.

The leader coaches judgment.

And then the leader creates enough space for other people to lead.

That doesn't make leadership less important.

It makes leadership more scalable.

Because there is a limit to how many decisions one person can make.

There isn't the same limit on how many capable decision-makers an organization can develop.

If everything depends on you, start with the decisions

Founders often recognize that their business has become too dependent on them.

The instinct is usually to delegate more.

That's useful, but I don't think it goes far enough.

Instead of only asking:

“What work can I delegate?”

Ask:

“What decisions shouldn't require me anymore?”

Then work backward.

What does someone need to know to make that decision?

What authority do they need?

What guardrails matter?

What capability needs to be developed?

What mistakes are acceptable while they learn?

How will you coach without taking the decision back?

That's how a business begins becoming less dependent on its founder.

Not because the founder disappears.

Not because leadership matters less.

But because leadership has done its job well enough that good decisions can happen throughout the organization.

The goal of leadership isn't to become better at making all the decisions.

It's to build an organization capable of making good decisions without requiring you to be in the middle of every one.

---

Is your business too dependent on you?

If too many decisions still come back to you, delegation may not be the real bottleneck. The free Business Bottleneck Assessment will help you identify the operating constraint making your company more dependent on you than it should be—and show you what needs attention first.

Take the Business Bottleneck Assessment