From control to oversight: why capable teams keep coming back to the founder

Where’s this up to? What happened with that client? Has someone dealt with this yet?

There was a period in my business when I kept asking those questions. Sometimes I would call a meeting just to get the answers.

I knew I was getting in the team’s way. They knew it too. But I wasn’t comfortable letting go, and we hadn’t built a reliable way for me to see what was happening without asking.

The problem reached beyond my habit of checking. Client expectations, spending decisions and operational questions still needed information or judgement that sat with me. People could carry their own part of the work while relying on me to connect it to everything else.

Learning to change that became part of my transition from entrepreneur to CEO: moving from personal control to oversight.

The business had grown around what I could carry

It took entrepreneurial drive to start the company: backing my judgement, using my skills, winning clients and taking responsibility for making things happen.

In those early years, I was close to the money, the operations, the sales conversations and the client relationships. Much of the business worked because I could connect those things personally.

As we grew, that became harder to sustain.

I remember the strain becoming clear at around 28 to 30 people, with revenue somewhere around five to six million dollars. That was the point in my business when it felt too big for one person to hold.

I thought I was working on the business. But client relationships and day-to-day decisions still occupied me, leaving too little room to stand back, examine the information and think about where we were going.

The skills that got us started still mattered. But I needed to get better at explaining where we were going, encouraging people to take responsibility and coaching them through decisions I used to make myself.

Why capable people still came back

Managers would come back to check what I wanted. Some issues needed my involvement. Others returned because people were trying to work out the decision I would make.

A person can understand a task and still lack the context to exercise judgement.

A client expectation formed in an early sales conversation might never have reached the delivery team. A manager might have permission to spend, but little confidence that their decision would stand when I saw it. Someone could own an account while knowing the client still expected me in the room.

These gaps could sit between roles and functions. I supplied the missing connection, and the business kept relying on me to supply it again.

My own behaviour reinforced that pattern. Each extra check or questioned decision could suggest that responsibility still rested with me.

At first, I didn’t recognise how much of my discomfort was about losing control. I had delegated work without fully accepting what it meant for someone else to carry it.

I had to look at what the team was missing, and what I was doing that kept bringing the work back.

The decision I let someone else make

One client issue stayed with me.

Normally, I would have answered it. This time, I asked a manager what she wanted to do and let her take the lead.

Her approach wasn’t what I would have chosen.

But we had worked together for a long time. She understood the business, knew how I thought and had shown me that she cared about what we were building. She had also developed her own relationship with the client.

I needed to give that relationship room.

Afterwards, the client began calling her.

She had earned my confidence. When I stopped stepping in, the client had room to build that same confidence in her.

What oversight made possible

I still needed to know what was happening across the business. As CEO, I needed a way to remain accountable for its direction and performance while others made decisions within their roles.

We worked on delegated authority, the responsibilities of the management team and the information I needed to see. We built feedback into milestones, weekly coaching conversations and monthly management reviews.

Together, we learned to clarify the decisions people could make, the expectations they were working towards, the promises they needed to carry through and when an issue needed to come back.

Those arrangements gave the team room to work and gave me a reliable place to ask questions. I could review progress, understand concerns and intervene when needed without repeatedly interrupting the work.

The change was noticeable. Fewer emails. Fewer phone calls. Much less of the daily noise coming through me.

Some matters still required my involvement. But at the monthly management meeting, I could see across the business without having made every decision along the way.

That was the power of oversight in practice: visibility and accountability that supported other people’s authority.

Only later, as I reflected and wrote my book, did I clearly articulate the shift I had been making.

The bottleneck can move down a level

As I passed responsibility to senior managers, I could also pass my pressure to them. Unless they learned to delegate, we were simply moving the bottleneck.

The coaching therefore continued through the business. I worked with my managers, and they worked with their teams.

What are you finding difficult to let go of? What are you worried will happen? What does the person taking this on need to understand? How will you stay informed without taking the work back?

Helping people understand where we were going and why their contribution mattered was part of my leadership. So was the patient work of helping them develop the judgement to carry responsibility.

Responsibility needed to reach the appropriate person, supported by context, authority and review. Delegation became an ongoing practice as the company grew and its systems changed.

Start with the dependency you can see

When capable people keep coming back, look closely at one recurring decision.

Does the person understand the intended outcome? Do they have the history behind it? Is their authority clear? Does the decision cross a boundary between teams that nobody owns? Have you agreed when to review progress and when to escalate?

Then there is the question I had to ask myself: am I prepared to let them make a sound decision that isn’t the one I would have made?

In the Two Icons approach, founder dependency is a signal to investigate. Growth Architecture explains how gaps in context, authority and the connections between functions can keep a growing business reliant on its founder.

That experience informed the Oversight diagnostic framework. I use it to understand where the business still relies on the founder and why, before deciding what needs to change. The aim is to help the founder gain the kind of oversight I needed: knowing how the business is doing and where attention is needed, while other people carry their decisions.

For me, becoming a more effective CEO meant developing that capability alongside my team’s ability to act. I could remain responsible for the business while giving others genuine room to lead within it.

Where to go next

• What Is Founder Dependency? Signs to Look For — recognise the pattern behind recurring reliance on you.

• How to Systemise Your Business Without Everything Coming Back to You — explore how context, authority and leadership can move into the business.