I Liked Being Needed.

That’s why founder dependency sticks around longer than it should.

There’s a version of being “over-responsible” that looks respectable. It looks like leadership. Like heart. Like being the founder who gives a damn. And sometimes it is. But sometimes… it’s something else. Sometimes over-responsibility is just an addiction to being needed.

I don’t even mean that in an arrogant way. I mean it in the most human way possible. Being needed is immediate proof you matter. Ping. Question. Fire. “Do you have a sec?” You answer and the room calms down. You fix it and everyone breathes again. And you get that little internal hit like… okay. I’m still useful. I’m still the one who can hold this. That’s the part nobody wants to admit to because it sounds like ego. But most of us aren’t doing it for ego. We’re doing it because the business is stressful and being the one people rely on makes it feel stable, even if it’s a fake kind of stable.

The morning I couldn’t ignore it

I remember one morning that made it impossible to ignore. I was in a hotel room at a conference. The whole point of the trip was to network, be present, build relationships. The team was supposed to handle everything back at the office.

I woke up and checked my phone while the glow lit up the room. I kept the lights off because my husband was still sleeping. And within seconds I knew I wasn’t really there.

A new sales rep was sick and there were important calls on the calendar. So I’m sitting on the edge of the bed trying to decide if I’m going to be late to the first speaker so I can reschedule everything… or just take the calls myself.

At the exact same time, my office manager is texting me about someone’s commission and asking me to verify it for payroll. And then a sales rep who had been on the team for six months is asking me how to quote something… still. Not asking the team. Asking me.

Even when someone would try to protect my time and say, “Don’t bother Summer, ask me instead,” they’d still come to me if they didn’t get the answer they wanted.

I remember looking at my husband and saying, “This has to change. I can’t even go on a work trip without being needed.”

How founders train dependency

That’s when it hits you: you’re not the founder. You’re the emergency contact. Not just for the big things… for everything. Little decisions. Little questions. Little “quick checks.” Little approvals. The kind of stuff a team should be able to handle without the owner getting pulled in.

And the messed up part is… you trained it. Not intentionally. Just slowly, one “I’ll handle it” at a time.

A manager asks something they should know and you answer because it’s faster. A decision stalls and you jump in because you don’t want it sitting there. A customer is upset and you take the call because you can smooth it over. A new hire is shaky and you “support” them by doing half of it.

Every time you do that, you teach the same lesson: if we wait long enough, it comes back to her.

Even good people learn that. And no, they’re not lazy. You just made it the safest path.

The part nobody wants to admit

For a long time I thought founder dependency was a hiring problem. Like I just needed “better people,” or more experienced people, or someone who had “done it before.”

But founder dependency isn’t usually created by a lack of talent. It’s created by a lack of ownership. And ownership doesn’t exist if there’s no consequence for not owning. If the founder always catches it, there is no consequence.

So yeah, you can build a business where everyone likes you, where everyone feels supported, where everyone feels “safe.” And at the exact same time, you’re building a prison. You’re the one locking the door every time you say, “It’s fine. I’ll handle it.”

What really hit me the hardest was that sometimes I didn’t step in because I had to. Sometimes I stepped in because I liked the feeling of being the one who could handle it.

And that scared me.

Because if that’s true, the problem isn’t just the team. It’s me. It’s my identity inside the business. It’s how I measure my value.

And this is why “freedom” isn’t just a scheduling issue. It’s an identity shift. Because if you’ve been the hero for long enough, stepping back doesn’t just feel like letting go.

It can feel like disappearing.

Where I draw the line now

So I started doing something that felt small but actually changed everything. I stopped answering “quick questions” the old way. I didn’t do it by ignoring people or by acting too busy, but by refusing to be the default.

Now when someone brings me something, I ask three things:

• Who owns this?

• What does the outcome need to be?

• What do you suggest?

If they can’t answer those, I don’t take it back. I treat it like a signal. Either the role is blurry, the standard is unclear, or we never defined “done.”

And that’s what I fix.

I’m not trying to be the most helpful person in the company anymore. I’m trying to build a company that can think without me.

That’s leadership.

Not being available for everything and building people who can hold the line.

The punch line

If you’re reading this and you’re tired, I’m not going to tell you to “delegate more.” You already know that.

I’m going to ask the harder question: where are you stepping in because it’s necessary… and where are you stepping in because it makes you feel important?

Both can be true. But if you can’t tell the difference, you’ll stay stuck.

And here’s the punch line:

If your business can’t make decisions without you… it’s not a team.

It’s a dependency.

And you’re the drug.