There is something I hear from business owners all the time: Why does everything still come back to me?

You hire good people. You create roles. You delegate. You put people in leadership positions. And somehow you are still answering questions, catching things that get missed, solving problems, reminding people what needs to happen, managing conflict, and stepping in when something starts to go sideways. After a while, it can become incredibly frustrating. You start wondering why no one seems to take the same level of ownership you do.

The truth is, they probably never will. It's your business. You created it. You carry a different level of responsibility for it. But there may also be something happening underneath that frustration that is worth looking at.

In systems theory, there is a concept called overfunctioning and underfunctioning. Essentially, when one person in a relationship or system consistently takes on more responsibility, the people around them can begin taking on less. The more one person compensates, reminds, rescues, anticipates, and fixes, the less opportunity everyone else has to develop responsibility for themselves. Founders are especially vulnerable to this dynamic, and I think there are some very understandable reasons why.

Overfunctioning isn't the same as working hard

Founders work hard. That alone isn't overfunctioning. Overfunctioning happens when you start taking responsibility for things that actually belong to someone else.

Maybe you remind an employee about something they should be tracking themselves. Maybe you redo work because fixing it feels easier than having another conversation about it. Maybe two people on your team are having a problem and somehow you end up in the middle. Maybe someone brings you a question and, even though they could probably figure it out themselves, you give them the answer because it's faster.

Sometimes it's even harder to recognize. You delegate something, but continue thinking about it, checking it, and anticipating everything that could go wrong. Technically, someone else owns it. Psychologically, you still do.

Founders can overfunction emotionally too. You monitor the mood of the team. You worry about how people are going to react to a decision. You spend too much time trying to communicate difficult information in a way that guarantees no one will be upset. You absorb other people's anxiety and then work harder to make everything feel okay again.

The tricky part is that none of this necessarily looks unhealthy. It can look like being a really responsible founder. And often, that's exactly how it started.

In the beginning, you really did have to do everything

This is one of the reasons I have a lot of compassion for this pattern in founders. When you start a business, you usually do have to do everything. You answer the emails. You find the clients. You pay the bills. You solve the problems. You make the decisions. You figure out things you have absolutely no idea how to do because there isn't anyone else to do them.

You become incredibly resourceful, and that resourcefulness may be part of what allowed you to build the business in the first place. But then the business grows. You hire people. You create positions. You give people responsibility. Sometimes the business changes faster than your relationship with responsibility does.

You may have delegated the job without really letting go of responsibility for the outcome. If I give you responsibility for something but continue checking it, reminding you, correcting you, anticipating what you might miss, and stepping in whenever something goes wrong, have I really given you ownership? Probably not.

Attachment can be part of the story

Attachment theory gives us another interesting way to understand why some founders are particularly prone to overfunctioning. Attachment isn't only about romantic relationships. Our attachment patterns can influence how we experience trust, dependence, uncertainty, conflict, rejection, and responsibility in many kinds of relationships, including the ones we have at work.

For someone with more anxious attachment tendencies, overfunctioning can become a way of maintaining connection and reducing uncertainty. You may be highly attuned to changes in other people. You notice when someone seems unhappy, disengaged, frustrated, or distant. You may work harder to repair things quickly, keep everyone connected, or prevent someone from becoming dissatisfied. In leadership, that can translate into taking too much responsibility for how other people feel.

An employee is unhappy with a decision, and instead of allowing them to be unhappy, you feel compelled to fix it. Someone seems disengaged and you immediately start wondering what you need to do differently. Someone is struggling and you step in quickly because watching them struggle activates your own anxiety.

But overfunctioning can come from the other direction too. Someone with more avoidant attachment tendencies may have learned that relying on other people isn't particularly comfortable or reliable. Their overfunctioning may sound less like I need everyone to be okay and more like I'll just do it myself.

Hyper-independence can look a lot like competence in a founder. You don't ask for help. You don't trust other people with the things that really matter. You carry enormous amounts of responsibility without telling anyone how overwhelmed you are. You convince yourself that doing it yourself is simply more efficient. Sometimes it is. But if your answer to uncertainty is consistently I'll take care of it, you can eventually build a business that requires you to take care of everything.

Attachment patterns aren't destiny, and most of us don't fit neatly into one category all the time. But they can give us a useful question to ask: What happens inside me when I have to trust someone else with something that matters? For founders, the answer can tell us a lot.

This is where the system gets interesting

We tend to look at workplace problems as though they belong entirely to individuals. She doesn't take enough initiative. He needs too much direction. My managers won't make decisions. Everyone comes to me for everything.

Sometimes that assessment is completely accurate. Sometimes you really do have the wrong person in a role. But systems theory asks us to look at something else too: What is happening between us that might be helping this pattern continue?

If you always remind me, I don't have to become very good at remembering. If you catch every mistake before there is a consequence, I don't have much opportunity to learn what happens when I don't pay attention. If every difficult decision eventually ends up on your desk, I learn that difficult decisions belong to you. If you step in every time I struggle, I never really get to find out whether I could have figured it out myself.

Nobody has to consciously create this dynamic. It just develops. Then something frustrating happens. The more the employee underfunctions, the more anxious the founder becomes. The more anxious the founder becomes, the more they step in. The more they step in, the less opportunity the employee has to function independently.

Eventually, both people have evidence for what they believe. The founder thinks, See? If I don't do it, it won't get done. And the employee learns, I should probably check with them first.

Now you have a system.

Sometimes competence is also anxiety

This is the part I think founders can miss. Overfunctioning often looks like competence because, frankly, you are competent. You know how to fix the problem. You probably can do it faster. You may even do it better. But that doesn't necessarily mean you should do it.

Sometimes stepping in is less about what the business actually needs and more about how difficult it is to tolerate the possibility that something could go wrong. A client might be unhappy. An employee might make a mistake. Something might cost money. Someone might disagree with you. Someone might think you made the wrong decision.

When you're the founder, those things don't feel theoretical. The consequences really can land on you. So you step in. The problem gets solved and your anxiety goes down. That works beautifully in the short term. Unfortunately, it can also reinforce the idea that the only way to feel safe is to stay in control.

One question I think is incredibly useful for founders is: Does this actually require me, or am I stepping in because it's uncomfortable to watch someone else handle it differently than I would?

Those are two very different things.

You may have been doing this long before you had a business

For some people, overfunctioning feels incredibly familiar because they learned it long before they became founders. Maybe you were the responsible kid. Maybe you were good at reading the room. Maybe you learned to anticipate what other people needed. Maybe achievement was rewarded. Maybe conflict made you uncomfortable, so you became the person who kept everyone happy. Maybe the adults around you were overwhelmed or unpredictable and being competent gave you a sense of stability. Or maybe you learned early that depending on other people wasn't particularly reliable, so you became very good at depending on yourself.

Those adaptations can create incredibly capable adults. They can also create founders who have a very hard time putting anything down.

The child who learned I'll take care of it can grow into the founder who is still saying I'll take care of it twenty or thirty years later. Only now there is an entire organization willing to let them.

Sometimes overfunctioning is easier than making a hard staffing decision

There is another reason founders overfunction that I don't think we talk about enough. Sometimes it's easier to keep doing more yourself than to acknowledge that someone on your team simply isn't working out.

Making a staffing change is hard. It means having difficult conversations. It means asking whether you have been clear enough about expectations and whether you've given someone a reasonable opportunity to improve. It may mean recruiting, hiring, and training someone new when you already feel stretched thin.

So you compensate. You check their work more closely. You pick up what doesn't get done. You move responsibilities to stronger employees. You give another reminder. You have another conversation. You create another process. You lower an expectation. You tell yourself that once things settle down, you'll deal with it.

And because founders tend to be resourceful, we can keep a situation going for a remarkably long time.

The problem is that you're rarely the only person paying the price.

The rest of your team knows when someone isn't carrying their share. They know when they are being asked to compensate for someone else. They know when expectations aren't being applied consistently. Your strongest employees may become frustrated because their competence earns them more responsibility while someone else's underperformance earns them more accommodation.

That can damage trust. It can create resentment. Over time, it can change the culture of the organization.

Culture isn't simply the values you put on your website or talk about in a team meeting. Culture is what people experience you consistently expecting, reinforcing, addressing, and tolerating.

If excellence matters but poor work is repeatedly tolerated, people notice. If accountability matters but some people aren't held accountable, people notice. If collaboration matters but the same people are continually expected to compensate for someone else, people notice that too.

Eventually, your best people may start asking a reasonable question: Why am I working this hard if this is what we're willing to accept?

Your clients can feel it too

There is another consequence that matters even more. Eventually, your clients can feel the effects of a poor fit.

When someone isn't performing at the level your work requires, the impact doesn't necessarily stay inside the organization. Communication gets missed. Details fall through the cracks. Quality becomes inconsistent. Other employees become overloaded. Clients may have very different experiences depending on who happens to be serving them.

For a mission-driven business, I think this distinction is especially important. Your mission isn't protected simply by hiring people who say they believe in it. Your mission is protected by having people who can consistently deliver on it.

Someone can be a perfectly good person and still not have the skills, judgment, reliability, initiative, or alignment a particular role requires.

I've learned that not everyone is going to be a fit for what you're building, and trying to force a fit can become incredibly costly. Financially, yes. But also in the quality of the work, the experience of your clients, the morale of your team, and the culture you're trying to build.

Sometimes the founder needs to change. Sometimes expectations haven't been clear enough. Sometimes an employee genuinely needs more support or training. And sometimes the person simply isn't the right fit.

The maturity is learning to tell the difference.

Are you supporting someone or working around them?

There is a difference between supporting someone while they develop and continually redesigning the organization around what they aren't doing.

If someone needs reasonable training, give them training. If expectations haven't been clear, clarify them. If you haven't provided meaningful feedback, provide it. If you've been micromanaging them so intensely that they haven't had a chance to take ownership, step back and see what happens.

But if you've done those things and you are still continually stepping in to make the role work, it's worth asking a harder question: Am I supporting this person, or am I doing their job around them because I don't want to make a difficult decision?

That's uncomfortable. It's also leadership.

Your responsibility isn't only to one employee. You have a responsibility to the clients who trust your business, to the rest of the team who are doing excellent work, and to the health of the organization you're asking people to believe in.

Sometimes protecting those things means accepting that a fit isn't there.

A mismatch doesn't require a villain. Someone can be talented, caring, hardworking, and successful somewhere else and still not be right for what your organization needs. Trying indefinitely to force the fit doesn't necessarily make you a more compassionate leader. Sometimes it just makes everyone else carry the consequences.

"Just delegate" misses the point

Business advice loves to tell founders to delegate. That's good advice, but it doesn't go nearly far enough.

You can delegate a task without letting go of it psychologically. You can hand someone responsibility and then watch every move they make. You can tell someone you want them to take initiative and then correct them every time their approach differs from yours. You can say you trust someone while communicating in a hundred subtle ways that you don't.

The harder part of delegation isn't always handing something over. Sometimes the harder part is tolerating what happens after you do.

They may do it differently. They may make a mistake. They may disappoint you. They may need to experience the consequences of not following through. And you may have to sit with your own discomfort long enough to find out whether another capable adult can figure something out.

That's a very different skill from delegation.

We can overfunction emotionally too

Not all overfunctioning is about tasks. Sometimes founders become responsible for the emotional functioning of the company.

Everyone comes to you when they're upset. Someone has a problem with a coworker and tells you instead of talking to the coworker. Someone doesn't like a decision and you feel compelled to make them understand it. You spend an enormous amount of time anticipating how people will react before you communicate something difficult.

This is where another systems concept becomes useful: triangulation. A triangle happens when tension between two people gets managed by pulling in a third. Founders are particularly easy to pull into that third position because you have authority.

But if you continually become the person who manages tension between other adults, two things happen. You become exhausted, and they don't develop the capacity to manage the relationship themselves.

Again, this doesn't mean a leader should never intervene. Of course there are times when you need to. The question is whether you are actually needed or whether you've simply become accustomed to being needed.

When you change, the system changes

When someone stops overfunctioning, the people around them don't necessarily love it. If you've always been available to solve every problem and suddenly you're not, someone may think you're being less supportive. If you've always mediated disagreements and start asking people to speak directly to one another, they may resist. If you've always rescued people from consequences and stop doing that, things may actually get messier for a while.

That doesn't necessarily mean you're doing something wrong. Sometimes discomfort is what happens when a system that has organized itself around one pattern has to find a new one.

The answer isn't to stop caring or swing to the opposite extreme and become disengaged. Good leadership still requires direction, support, accountability, feedback, and intervention when it's appropriate. It's about getting clearer about what belongs to you and what doesn't.

Caring deeply isn't the same as carrying everything

You can care about your employees without being responsible for every feeling they have. You can support someone without solving the problem for them. You can be an empathetic leader and still hold someone accountable. You can recognize someone's strengths and still recognize that they aren't the right fit for your organization.

Compassion and discernment can exist at the same time.

You can allow someone to be disappointed with a decision without deciding the decision was wrong. You can care deeply about your team without making yourself responsible for everything that happens within it. And you can care deeply about your business without personally carrying every piece of it.

Eventually, carrying everything has a cost. You become exhausted and resentful. Your team can become increasingly dependent on you. Strong employees can become frustrated. The quality of the work can suffer. Clients can feel the consequences. And the culture you worked so hard to build can slowly become something you never intended.

At some point, you may have to consider a difficult possibility: Maybe the system has learned to function this way because you've been functioning this way too.

I don't see that as blame. I actually see it as hopeful. Because if you're part of the pattern, you also have some power to change it.

What is actually yours to carry?

One of the biggest shifts in becoming a more sustainable leader may have very little to do with productivity. It may be learning to tolerate uncertainty, letting other people solve problems, allowing someone to be disappointed, staying out of conflicts that don't belong to you, and letting capable people develop competence by actually giving them enough room to do it.

It may mean getting curious about your own attachment patterns and why depending on other people, disappointing them, or letting go of control can feel so uncomfortable. And sometimes it means being willing to make a difficult decision when you realize you have spent far too much time compensating for something that simply isn't working.

The goal isn't to care less about what you've built. It's to stop confusing caring deeply with carrying everything.

I work with founders, entrepreneurs, and business owners who are navigating these kinds of patterns around leadership, burnout, boundaries, delegation, conflict, identity, and responsibility. If this resonates, individual therapy for founders is one place to start.

Sometimes the most useful question isn't, How can I get better at managing all of this?

It might be: How much of this is actually mine to manage?