You can't hold everyone together and hold onto yourself at the same time.
Some leaders carry everything. Not because they have to, because they're terrified of what happens if they don't. They chase people down, absorb blame, and manage everyone's emotions before addressing anyone's behavior. It looks like dedication. Underneath, it's armor: a way to avoid the vulnerability of finding out what happens when you stop holding it all together.
Family systems theorist Murray Bowen called this over-functioning: one person in a system chronically doing more so the other can do less. It doesn't just exhaust the carrier. It trains everyone around them to stop carrying their own weight.
It starts early. In families where conflict meant disconnection, the child who learned "if I take care of everyone, no one leaves" becomes the adult who holds every relationship together by force of effort. The brain wires this into the threat-detection system, where unresolved tension registers as danger, and carrying the load becomes the fastest way to neutralize it.
Then it gets rewarded. Adam Grant's research shows givers are overrepresented at both the top and bottom of success, and the difference is boundaries. Caretakers are selfless givers: generous without limits until there's nothing left. The labels they earn ("dependable," "the glue") become identity. And once carrying is who you are, putting it down feels like losing yourself.
When one person carries it all, the whole team structure crumbles. Trust erodes because everyone sees the unfair dynamic but no one names it. Conflict gets avoided, commitment drops, accountability disappears, and results suffer. One person doing the work of three while others coast is a team health crisis.
The personal cost is just as severe. The caretaker's goals shrink. Their boundaries dissolve. They stop asking what they want because they're too busy managing what everyone else needs. The anxiety is two values at war: who you are versus who the system trained you to be.
Next time you feel the pull to fix, follow up, or smooth something over, pause. Ask one question:
Am I doing this because it's mine, or because I'm afraid of what happens if I don't?
If the answer is fear, put it down. Choosing discomfort over exhaustion is the brave move. Let the person who owns it feel the weight. Letting them feel the weight is respect. It's giving with boundaries instead of giving until there's nothing left.
It's when a leader takes on the work, problems, and emotional weight that belong to their team. Someone comes in with a problem and leaves without it, because the leader absorbed it. This looks like helpfulness. Over time it becomes a structural problem: the team stops owning things because the leader keeps picking them up. Nobody intends this. The caretaker trap usually starts with a leader who's genuinely skilled at solving problems and genuinely wants their people to succeed. The trap is that helping in the short term creates dependency in the long run.
Several reasons, and they're usually tangled together. Solving feels faster than coaching. Fixing feels like leadership. And for a lot of leaders, being needed is woven into their identity in ways they haven't fully examined. The leader who grew up as the capable one, the person who kept things together, who got things done, who could be counted on, and often becomes the leader who can't stop doing that even when it costs their team something. The pull toward caretaking is real and not malicious. It just needs to be named before it can be changed.
Ask questions instead of giving answers. When someone comes to you with a problem, your first move is "what have you tried?" and "what do you think the options are?" not "here's what I'd do." This feels slower. It is slower, in the moment. But the second time that person faces a similar problem, they solve it themselves, and the third time, they don't come to you at all. The shift from problem-solver to thinking partner is the single most practical thing a caretaker leader can do, and it starts with one conversation where you resist the instinct to just fix it.
Support builds their capacity. Rescue replaces it. When you support someone, you're giving them what they need to figure it out: a resource, a frame, a question, a connection. When you rescue them, you take the thing they were supposed to figure out off their plate and put it on yours. The distinction matters because rescue feels like support in the moment, to both parties. The way to test which one you're doing: ask whether they walk away more capable than when they came in. If the answer is no, it was probably rescue.
Go deeper → My Leaders Won't Take Ownership: Why Everything Escalates to You