The System That Made You Successful May Be Keeping You Stuck

A leadership system can keep delivering results long after it stops serving the leader who built it. That is why I think some of our most successful systems deserve a harder examination.

You may have built a team that trusts your judgment. Problems get solved. Standards are protected. Customers get answers. The operation works. And yet, somehow, nearly every consequential decision still finds its way back to you.

At first, that was probably necessary. You were closest to the work, you knew what could go wrong, and the cost of a poor decision was real. Your involvement protected something worth protecting.

Twenty years later, the same arrangement may be preventing the next generation of leaders from learning what you already know.

When the system quietly becomes you

Imagine a small business owner reviewing an unusual customer discount. He knows the customer, remembers the last exception and understands what giving an inch here could mean six months from now.

He makes the call in three minutes. Everyone moves on. From the outside, that looks efficient.

But the next exception comes back to him. And the next. His managers learn the correct answer without learning how he reaches it. They are becoming excellent at consulting him.

That's the hidden bill. The company receives the decision. It does not receive the judgment that produced it.

The system can even make that dependency look like a virtue. People praise the owner's accessibility. He takes pride in being dependable. Then he begins to wonder why nobody makes decisions without him.

I have seen a version of this problem across leadership environments over many years. People often build their responsibilities around the person whose judgment they trust most. It feels sensible until the demands multiply.

Eventually, the organization's confidence in one person becomes another person's permission to stop thinking independently.

If you want more leadership thinking like this in your inbox, subscribe free to Todd's Mid Career Leadership. I publish useful teaching without requiring you to become a paid member.

The trade that once made sense

I don't think the right response is to criticize the leader for building this way. Some seasons genuinely require close supervision. A new team, a fragile organization or an expensive mistake can justify tighter control.

The trouble begins when the season changes but the operating rules do not.

A leader who once needed to approve every exception may now have experienced managers capable of handling most of them. Yet nobody has revised the authority boundaries or described what a good exception decision requires.

And the leader has a personal stake in keeping the old system alive. He has become the reliable answer, the person others seek out when the stakes rise.

That identity is difficult to set down. It was earned through years of responsibility, and it often carries real affection for the people who depend on him.

We can love the people, believe in the mission and still admit that the way we have been carrying the work has reached its limit.

Leadership systems should carry judgment, not just instructions

Most organizations know how to write procedures. They can document who submits a request, which box gets checked and where an approval goes. Those instructions are useful, but the hardest leadership work lives between the boxes.

The problem is rarely a routine request. It is the customer whose circumstances do not fit policy, the employee who makes a promising decision with incomplete information, or the budget choice with two legitimate answers.

A mature leadership system makes the reasoning visible. What mattered most? Which risk could we accept? What would have changed the decision? When should someone ask for help instead of deciding alone?

Without that reasoning, transferring a task is often just relocating the paperwork. The real authority stays where it always was.

It is also possible to go too far. Handing over a difficult decision without adequate preparation is not development. It is abandonment dressed up as empowerment.

The goal is to give another leader enough context, permission and feedback to exercise sound judgment, including the opportunity to make a different defensible choice than you would have made.

What a decision-ready system actually contains

Before transferring an approval, I would ask a manager to explain four things. First, what outcome are we protecting? A discount policy might protect margin, customer trust, and consistency among accounts. Those can pull in different directions. Second, what boundaries cannot be crossed? Sometimes the boundary is financial. Sometimes it is a safety standard, a promise already made, or a legal obligation.

Third, what information changes the decision? The age of the customer relationship may matter; a compelling story alone may not. Fourth, when should the manager bring the issue back? Escalation is not a failure if the conditions requiring it were agreed upon beforehand.

None of these questions requires a forty-page manual. A short conversation, followed by a written example, can transfer more judgment than another approval form. The real test is whether the next person can explain a sound decision without borrowing your reputation to justify it.

The cost of keeping the old approval habit

There is an expense we rarely put into a budget: the number of minutes an organization spends waiting for somebody else's judgment. That expense becomes obvious when the owner travels, gets ill, takes a day off or simply needs uninterrupted time to think.

The subtler expense is what the next leader never gets to practice. They can learn to gather information, make recommendations and anticipate your preferences while still never becoming accountable for the final call.

Over time, that creates two weaknesses. You cannot leave without causing friction, and the people around you cannot grow without repeatedly seeking your permission. Both may be disguised as loyalty.

A stronger system should make room for a manager to be responsible for a defensible decision, even when the result turns out imperfectly. Review the thinking, the boundaries and the evidence. Don't judge development solely by whether their answer matched yours.

The question behind every approval

Next time a decision arrives that everyone assumes belongs to you, resist the urge to answer immediately. Ask what made you the necessary person in that moment.

Is it information no one else has? An actual authority limit? A relationship only you maintain? Or a habit created years ago that nobody has thought to question?

Those answers lead to different responses. If the information is missing, share it. If the authority is unclear, define it. If the relationship matters, introduce someone else. If the habit is outdated, retire it.

Sometimes the decision must stay with you. A legal, financial or ethical responsibility cannot always be delegated. That is precisely why we need to distinguish real accountability from personal preference.

The leader who keeps everything may feel safe in the short run. But he is also teaching his people that responsibility ends at the point where his comfort begins.

What this means in the contribution years

There comes a season when accumulated experience ought to be doing more than helping us make another hundred decisions ourselves.

We have spent years recognizing patterns, recovering from mistakes, reading people and learning which risks matter. Some of that knowledge is difficult to explain because we have practiced it for so long that it feels obvious.

That is exactly what makes it worth the effort to explain.

If your experience can only help others when you are physically present to settle the issue, the reach of that experience is limited by your calendar, health and available attention.

For an experienced leader, this raises a personal question as much as an organizational one. Can you still see your value when people no longer need to bring every problem to your desk?

A leader who releases that dependency may gain room for work that has been set aside for years. His team may gain the confidence and responsibility it has been waiting to exercise.

Of course, that shift can feel uncomfortable. The first successful decision made without you may produce pride and a little sadness at the same time.

There is no reason to pretend otherwise. Being needed has probably been part of how you measured a good day for a long time.

A simple test before you change the system

Take three decisions that reached your desk recently and sort them into categories: decisions that must remain yours, decisions another leader could own with clearer boundaries, and decisions that have come to you only because they always have.

Now ask the person closest to the work how they would handle one decision in the third category. Listen through their reasoning before offering your own. Where do you genuinely know something they don't? Where have you simply never allowed them to decide?

You may discover the system needs a new approval threshold, a better shared record of past exceptions or a change in who meets with a customer. You may also discover that the obstacle is your reluctance to let a good leader choose an approach that differs from your preferred one.

That last possibility is worth examining carefully. A system built around one person's instincts can preserve quality for a season. It cannot develop an independent leadership bench unless the instincts become visible, teachable and open to thoughtful challenge.

Subscribe free for the next leadership article if you want to continue examining the decisions that shape your work.

A decision to make this week

Choose one recurring decision that came to you during the last seven days. Not your biggest decision. Choose one that should have been within a capable colleague's reach.

Before you answer it again, write down what you considered: the information you used, the competing risks, the boundary you would not cross and the result you were trying to protect.

Then talk that reasoning through with the person who could reasonably own the next decision. Agree on when they may decide, what they must tell you afterward and what would require escalation.

When the next case comes, allow them to make the call inside those boundaries. Review the reasoning afterward, even if their answer differs from yours.

One decision is a small place to start. But it will reveal whether your system is transferring judgment or merely organizing requests for your approval.

And it will tell you something about what you are ready to release.

If you are sorting out what your experience is meant to contribute in this season, Ask Todd is a free place to bring one specific leadership question. Start with the decision you have been carrying longer than you should.

This article also went to the newsletter on Substack