Stop taking over: how founders help their teams take responsibility

In the past, people have pointed out that I say yes to helping too readily.

I enjoy getting things done. If someone needs support and I can see a way forward, stepping in feels useful.

But that instinct has a cost when helping becomes taking over. My own priorities wait, while the other person loses an opportunity to develop their judgement and confidence.

For founders, this can become a familiar pattern. People bring you problems, you provide the answers and more decisions come back to you next time.

Changing that pattern involves looking at how you respond, what people need and whether they genuinely have the authority to act.

Notice when support becomes taking over

Think about the last few times someone asked for your help.

Did you clarify something so they could continue? Did you make a decision that genuinely belonged to you? Or did you leave the conversation owning work that had previously been theirs?

Taking over can happen in small ways. You rewrite the email, call the customer yourself or finish the proposal because explaining your thinking seems slower.

Occasionally, that may be necessary. If it happens repeatedly, examine what is creating the dependency.

The person may lack experience or information. The responsibility may be unclear. You may also be stepping in before they have had a chance to work through the problem.

Find out what they need from you

Before offering an answer, ask what would help.

They might need a decision, access to information, permission to proceed or another perspective. Sometimes they want reassurance that you will support a reasonable choice.

Try asking:

“What have you considered so far, and where are you getting stuck?”

Give them time to explain. If they have not considered any options, explore what is preventing them from doing so.

Avoid turning every request into a test. Someone who is new to the work may need direct teaching. Someone who understands it well may need you to confirm a boundary and leave them to act.

Match your support to the situation.

Make responsibility and authority clear

You cannot reasonably expect someone to take responsibility for an outcome if they need your approval for every meaningful decision.

Discuss what they own and what they can decide independently.

That might include spending limits, customer commitments or changes to how the work is carried out. Identify the situations where they should involve you and explain why.

Be clear about the result you need, any constraints and the timing.

Then check their understanding. Ask them to talk through how they see the responsibility and what they expect to need from others.

This can reveal differences before they become frustration on either side.

Teach the judgement behind the task

Instructions can explain how to complete a familiar task. People also need to understand how to respond when circumstances change.

Share the reasoning behind your decisions.

What do you look for? Which risks matter? How do you choose between competing priorities? What would make you pause and ask for help?

Where useful, work through an example together. Let the person explain what they would do before you add your perspective.

A short guide or checklist can help with recurring work. Keep it focused on the decisions and information that matter rather than trying to document every possibility.

The aim is to help someone handle the next situation with less dependence on you.

Agree when you will check progress

Handing over work does not mean disappearing until the deadline.

Agree check-ins that fit the person’s experience and the consequences of getting something wrong.

For unfamiliar work, an early review can catch misunderstandings before much time has been spent.

As the person becomes more capable, you can adjust the support.

Make those check-ins useful. Ask what is progressing, what has changed and where a decision is needed.

Avoid adding unplanned reviews simply because you feel uncomfortable being less involved. If you need more visibility, explain the reason and agree an approach that works for both of you.

Allow a different approach

Someone else may do the work differently from you.

Before intervening, ask whether the difference affects the outcome or simply your preference.

If the work meets the agreed requirements, there may be no reason to change it. You might even learn something from their approach.

If there is a problem, explain it specifically. “This isn’t how I would do it” gives little guidance. “The customer cannot see what happens after they sign” identifies something the person can address.

Where possible, let them make the improvement. Repeatedly correcting the work yourself keeps the knowledge and responsibility with you.

Respond constructively when something goes wrong

The way you respond to a mistake affects whether people bring you concerns early.

First understand what happened. Were expectations clear? Did the person have the information and support they needed? Was a risk missed or a decision poorly judged?

Agree what needs to happen now and what should change next time.

There may be occasions when you need to intervene quickly or address a serious performance issue. Be clear about that without treating every mistake as evidence that delegation cannot work.

People need to know both that standards matter and that raising a problem is preferable to hiding it.

Say no to taking over, while offering useful support

You can be helpful without accepting ownership of the task.

For example:

“I can give you twenty minutes to think through the options. I’d like you to remain responsible for the recommendation.”

Or:

“You have authority to decide within the budget we agreed. Talk me through anything that would take it outside that.”

Use language that fits your relationship and the person’s experience. A new colleague may need much more guidance than someone established in the role.

Be honest about your own capacity too. If you cannot help immediately, agree when you can or identify another source of support.

Look for the pattern when requests keep returning

If the same questions keep coming back, investigate rather than simply becoming firmer.

The person may be dealing with conflicting priorities, an excessive workload or inconsistent instructions. They may have learned that you overturn decisions, so checking first feels safer.

There may also be a genuine development need.

Ask what would help them handle the situation more independently. Agree a practical change and review whether it works.

If progress remains limited despite clear expectations and appropriate support, have a direct conversation about what is happening. Repeating the same cycle of rescue and frustration helps neither of you.

Start with one recurring decision

Choose a decision that regularly reaches you but could reasonably sit with someone else.

Discuss the outcome, authority and support required. Agree what the person will handle and when you will review it together.

Then pay attention to your own response. Can you tolerate a different approach? Can you give guidance without reclaiming the work?

Helping your team take responsibility requires development on both sides. They build their capability and judgement. You practise making room for them to use it.

If you would value space to explore delegation, difficult conversations or your habit of stepping in, explore working with me through founder coaching and mentoring.

Cheers,

Duncan