You didn't lose the team. You solved them out of the picture.

Second Dad | E0019 | How You Lose the Team Without Noticing

You didn't lose the team in one moment. You solved them out of the 
picture. One rescue at a time.

This episode is about the solver identity that becomes a ceiling, 
the system that trained the team to stop bringing things, stop trying, 
and route around you instead. Not because they stopped caring. Because 
there was no point.

The team isn't the problem. The team is the proof.

Adult Question: What would have to be true about the team for the 
problem to actually be yours?

Website: https://seconddad.com/
Book: https://amzn.eu/d/01PFUl5f
Spotify: https://open.spotify.com/show/0ixmOqlkfssOSxMtrqE5vt?si=260b21dcc4254bfa
Apple: https://podcasts.apple.com/us/podcast/second-dad/id1870344356
YouTube: https://www.youtube.com/@Second-Dad

Transcript

SPEAKER_00 0:13

Episode nineteen.

SPEAKER_01 0:16

How you lose the team without noticing. You think it's the staff. You thought about it. You've looked at the numbers. You've had the conversations. You've had a new person in the role. Works for a while. Then the same thing. You've tried bonuses. You've tried salary. You've even tried restructuring roles. Still the same. I want I want to talk to you about something because I don't think it's the staff.

SPEAKER_00 1:09

You've built a place where you solve things. And that's not a criticism. That's just what happened. Early on, you solve the things because it was faster.

SPEAKER_01 1:26

Because you were better at it. It because it mattered that it got done right. And so the system learned. Bring it to you. You'll sort it. And that worked. For a while that worked. It worked well. But at some point, solving everything stops being a strength. It then becomes architecture. The team made a rational decision. Not so much a conscious one. Nobody sat in the room and agreed to start trying. It's it's quieter than that. They brought you something. You solved it. They brought you something else. And you solved that too.

SPEAKER_00 2:38

At some point, and and there's no single moment you can really point to.

SPEAKER_01 2:50

Not because they stopped caring, but because there's no point. You'd solve it anyway. Even when they didn't need you to. Actually, especially when they didn't need you to. So they waited. And they start rooting around you. And that's not resistance. That's a rational response to the system that you built. The team don't stop caring. They just stop bringing things to you. Because you solve it anyway. Even when they don't need you to. That's not a people problem. That's a system problem. And this is what really makes it hard to catch. You bring in someone new. You got fresh energy, different attitude. And it works. For a while, it genuinely works. But that new person hasn't learned the system yet.

SPEAKER_00 4:21

They're still trying.

SPEAKER_01 4:23

They're still bringing things. And then slowly the same pattern. So you obviously conclude it's the people. I think I need to rotate them. Maybe incentivize them. Give them more reason to care. None of it works.

SPEAKER_00 4:54

Because you haven't actually changed the one thing that makes all of this inevitable.

SPEAKER_01 5:04

Keep changing the people. But you haven't changed your position in the system. New hire works for a while. Same erosion, new hire, same erosion. You concluded it was the staff. But you haven't asked what stays constant. And there's a reason why it's hard to see.

SPEAKER_00 5:38

Because your identity is built on being the one who fixes things.

SPEAKER_01 5:46

But that's not nothing. It got you here.

SPEAKER_00 5:53

But that same identity that built the business is the same identity that's making it impossible for anyone else to function in it.

SPEAKER_01 6:06

You're not the solver anymore. You're the ceiling. And the ceiling doesn't feel like a ceiling to the person who is in it. It feels like standards. It feels like care. It feels like doing it properly.

SPEAKER_00 6:32

From inside that identity, the team looks like the problem.

SPEAKER_01 6:36

From outside it, you are the problem. I have had this conversation. Not this one specifically, but close enough.

SPEAKER_00 6:52

I've sat with someone who runs a business, and that person works harder than anyone in the business. Cares more than anyone else in the business. Is burning out while his team looks disengaged. And I'm told them what I'm telling you now. What came back was you can't trust them. They're not motivated. They don't take ownership.

SPEAKER_01 7:27

And all of that may be true. But the trust broke in the other direction first.

SPEAKER_00 7:39

They they stopped trusting that anything that they fixed will stay fixed. They stopped trusting that their efforts had any consequence.

SPEAKER_01 7:51

Because it didn't. You'd get there before them. You don't lose a team in one moment. You solve them out of the picture. One rescue at a time. You can't trust them. They're not motivated. They don't take ownership. All of that might be true. But ask yourself, when did the trust break first? And which direction did it go? There's no quick version of this.

SPEAKER_00 8:41

You can't announce that you're just stepping back. And you can't restructure your way out of this. You can't bonus your team into believing you've changed before you've actually changed.

SPEAKER_01 8:58

The erosion happened over years. The routing around it is now how the place runs. That's not a staff problem. That's not a culture problem.

SPEAKER_00 9:17

It's a structural consequence of a leader who couldn't leave a problem alone long enough for someone else to own it.

SPEAKER_01 9:29

The team didn't leave. They adapted. And that adaptation became permanent before anyone noticed it was happening. By the time you see the routing around, it's been true for a long time.

SPEAKER_00 9:55

I'm not telling you this to diagnose you. I'm telling you because I've watched someone else I respect burn themselves out of trying to fix a problem that they were the source of.

SPEAKER_01 10:11

The team isn't the problem. The team is the proof. You built the system that needed you at the center, and then you stayed there. And that made sense once. What would have to be true about the team for the problem to actually be yours?