“Can you take this on?”

It sounds like delegation. Sometimes, it isn’t.

In a growing company, a founder may hand a project to a manager, ask someone to take over a process, or give an employee responsibility for a new area. On paper, the work has moved. In practice, the founder is still answering most of the questions, approving the important decisions and stepping in when the work takes a direction they would not have chosen.

A few weeks later, the founder is frustrated that the team is not taking enough ownership. The employee, meanwhile, has learned that “owning” something really means handling the work while continuing to look to the founder for approval.

This is one of the more common delegation challenges in startups and small businesses. The issue is not necessarily a lack of capable people. Often, responsibility has been transferred without giving the person enough authority, context or room to make decisions.

That distinction matters.

Delegating work is not the same as transferring ownership

Imagine a founder asking a newly promoted operations manager to take over scheduling. The manager quickly runs into a staffing gap, an overtime question and a recurring customer request that was never discussed when the responsibility was handed over.

Each time, the manager goes back to the founder. The founder starts wondering why a manager needs approval for everything. The manager starts wondering how much they are actually allowed to decide.

Neither person is necessarily doing anything wrong. The expectations were simply never made clear.

Good delegation starts before the task is handed over. It starts with deciding what the person is actually being asked to own.

Is the expectation that they complete the work, or are they responsible for the outcome? Which decisions can they make independently? What boundaries matter? When should they come back to the founder?

These conversations can feel unnecessary, particularly in a small company where everyone is moving quickly. But skipping them tends to create more work later. Without clear boundaries, employees either make decisions cautiously and seek approval too often, or make decisions without understanding what the founder considers important. Neither creates the kind of ownership a growing company needs.

There is also a difference between being available and being involved. A founder can remain accessible without remaining at the centre of every decision. In fact, that distinction is often what allows an employee to develop confidence.

A useful handover might sound like this:

“You own this outcome. Here is what success looks like. You can make decisions within these boundaries. If one of these specific situations comes up, bring it to me. Otherwise, I expect you to move it forward.”

The founder is still involved, but the employee knows where the responsibility sits.

Context has to be delegated too

This becomes particularly important because founders often have a level of context that others do not.

In the early stages of a company, that is an advantage. The founder knows why a process exists, which customer relationships are sensitive, what has already been tried and which decisions carry more risk than they may appear to.

The challenge comes when that knowledge stays with the founder while responsibilities are distributed across the team.

If employees have to come back to the founder for every decision because the necessary context was never transferred, delegation will always feel incomplete. The answer is not necessarily more oversight. Often, it is better context upfront.

Delegating responsibility without sharing the reasoning behind past decisions leaves employees responsible for outcomes they may not be fully equipped to navigate.

Different is not automatically wrong

There is another part of delegation that can be uncomfortable: accepting that someone else may do the work differently.

Founders are often close to the work because they have done it themselves. They know the shortcuts, the preferred approach and the standards they have developed over time. It is natural to notice when someone takes a different route.

But different is not automatically wrong.

If an employee reaches the agreed outcome, stays within the boundaries that matter and makes sound decisions along the way, there may be no reason for the founder to intervene simply because the approach is unfamiliar.

This is where delegation becomes a leadership skill rather than a productivity exercise. The question is no longer, “Would I have done it this way?” It becomes, “Is this person making good decisions and delivering what the business needs?”

That does not mean founders should delegate everything. Some decisions should remain with them, particularly those tied to company direction, major financial commitments, key people decisions or risks that require their level of accountability.

The problem is not founder involvement itself. It is when the founder becomes the default decision-maker because nobody else has been clearly given the authority to decide.

When the founder becomes the bottleneck

That pattern is especially costly in small companies. When every important question goes back to one person, employees wait, decisions slow down and the founder’s workload grows. The team also gets fewer opportunities to build judgment.

Eventually, the founder may conclude that the team is not ready for more responsibility. But the team may simply not have been given enough opportunities to develop it.

This is why taking work back is rarely a good long-term solution.

When something goes wrong, it can be tempting to say, “I’ll just handle it.” It is faster in the moment, especially when deadlines are tight. But if that becomes the default response, the team learns that mistakes lead to responsibilities being taken away. The founder ends up reinforcing the dependency they were trying to eliminate.

Accountability needs to work differently.

When a delegated responsibility does not produce the expected result, the conversation should focus on what happened. Was the outcome unclear? Was the person missing information or authority? Was a decision poorly made? Was the founder too involved, or not involved enough? What should happen differently next time?

Those questions are more useful than simply taking the work back.

They also make accountability more credible. People are much more likely to take ownership when they know they will be held responsible for an outcome, but also trusted to exercise judgment in getting there.

Delegation does not need to be complicated

For startups and small businesses, this does not require a complicated delegation framework. In many cases, a clear conversation, a defined outcome and a few agreed checkpoints are enough.

The founder can set the direction and establish the boundaries, then step back enough for the person responsible to actually operate within them.

If the responsibility changes as the company evolves, that should be discussed too. Roles in small businesses rarely stay static, and a delegation conversation from six months ago may no longer reflect what the business needs today.

Ultimately, effective delegation is not simply about getting tasks off a founder’s plate. It is about creating a company where more decisions can be made well without the founder being involved in all of them.

That takes time. People need opportunities to build judgment, make some mistakes and learn where the boundaries are. Founders need to resist the instinct to step back in every time the work looks different from how they would have done it.

The goal is not to make the founder less important. It is to make the business less dependent on the founder.

For a growing company, that is a much more meaningful measure of delegation than the number of tasks that have been handed off.