The Moment I Put the Tools Down — and Finally Understood What Leadership Actually Is

I was alone in a factory on a Sunday afternoon, wiring a cabinet.

I was alone in a factory on a Sunday afternoon, wiring a cabinet.

We were behind schedule. So I did what I had always done when things got tight — I stepped in and handled it myself. I had not taken a single day off in six months. At the time, I called that commitment.

Looking back, I call it something else.

It took standing in that empty factory, doing work that wasn't mine to do, for something to finally land:

This isn't my job. My job is to get this work done through other people. And if I'm standing here doing their work, that's not a sign of commitment. It's a sign that I'm failing at what I'm actually supposed to be doing.

That moment changed how I understood leadership. And it's something I've watched dozens of new leaders miss — not because they don't care, but because the habits that got them promoted are exactly the habits that hold their teams back.

The Trap That Feels Like Responsibility

Before I was promoted, doing well meant something simple: you hit your numbers, you produced, you delivered. If something fell behind, you stepped in and moved it forward. That was the standard — and it worked. It's what earned me the promotion.

So when I became a supervisor, my instinct was the same. Things falling behind? Step in. Problem not getting solved? Handle it. Teammate struggling? Jump in and fix it.

It felt responsible. It felt productive. It felt like I was doing my job.

I was wrong about all three.

What I didn't see — what's almost impossible to see when you're in the middle of it — is that every time you step in and take over, you remove the opportunity for someone else to learn. You also send a signal to your team, whether you intend to or not: when things get hard, I'll come in and take control.

Once that signal is in the environment, people respond to it. They stop pushing through problems on their own. Not because they're lazy — because they've learned that if they wait, you'll come in and handle it. You trained them to wait. And you didn't realize you were doing it.

What It Actually Creates Over Time

Here's what makes this pattern so difficult to catch: nothing looks wrong at first.

The work gets done. Problems get solved. Things move forward. From the outside — and even from the inside — it can look like strong leadership. A supervisor who's always in the middle of things, always has the answers, always knows what's happening.

But underneath that surface, something else is building. The team starts to rely on you in ways that aren't healthy. You start carrying more of the load than you should. And the gap between what the team is capable of and what you're actually doing keeps growing.

The system only works when you're present for everything.

That's not a team. That's a fragile arrangement that breaks the moment you're out sick, on vacation, or pulled into something else.

The Question That Changes Everything

When I put the tools down that Sunday and walked out of the factory, nothing was fixed overnight. The team didn't suddenly become high-performing. The problems didn't disappear.

What changed was the question I started asking.

Before that moment, I was asking: Is this getting done?

After, I started asking: Who's doing it — and are they getting better at it?

Before: Is this problem solved?

After: Do we have a consistent way to handle this when it comes up again?

Those are different questions. They lead you to different places. And they reflect a fundamentally different understanding of what leadership is actually for.

Your performance as a leader is not what you personally produce. It's what your team produces — and more importantly, whether your team is becoming more capable over time. Whether the operation can function when you're not there. Whether you're building something, or just carrying something.

The Instinct Never Goes Away — But What You Do With It Does

I want to be honest about something: the pull to step in never fully disappears. Forty years in, I still feel it. Something goes sideways and every part of me wants to walk over there and just handle it. That instinct doesn't leave you just because you've been doing this a long time.

What changes is what you do with it.

Now, when I feel that pull, I pause. I ask where it leads. I've already seen the outcome of following it over and over again — a team that depends on me more than it should, a system that only works when I'm involved in everything, and a ceiling on how far the team can grow.

The goal is not for you to be the one who can always get it done.

The goal is for the team to be able to get it done without you.

Where to Start

If you find yourself stepping in constantly — especially when things get tight — it's worth asking not just what you're solving, but what you're creating.

Pay attention to the small moments, not just the big ones. The quick answers. The immediate fixes. The situations you take over without thinking. That's where the pattern starts.

And once you see it, you have a real choice: keep doing it and carry more over time, or step back — even when it's uncomfortable — and start building something that doesn't depend on you being there for everything.

That Sunday in the factory was the first time I saw it clearly. Not as a concept. As a reality I was living.

Leadership isn't about doing the work.

It's about building something that works without you doing it.

This article is drawn from Chapter 1 of Nobody Tells You This Part: Real Patterns From Forty Years in Leadership That New Leaders Learn Too Late by Timothy G. Ferguson.

https://www.amazon.com/dp/B0GX2FM73M