Skip to main content

Why High Performers Build Jobs They End Up Hating

The Hidden Cost of Being the Person Everyone Depends On

Most high performers don't wake up one morning and decide they want a job they hate.

In fact, the opposite is usually true.

The people who end up feeling trapped by their role are often the most capable people in the organization. They're the ones who care deeply about outcomes. They're dependable. They solve problems. They get things done.

And because of that, they become indispensable.

At first, that feels like success.

People trust you.

Your team relies on you.

Customers appreciate you.

The business grows because of your efforts.

Everything seems to be working.

Until it isn't.

Because somewhere along the way, the role you originally wanted begins to change.

You stop leading the work and start carrying it.

You stop directing decisions and start making all of them.

You stop building systems and become the system.

And by the time you notice it, you're exhausted.

Not because you're incapable.

Because you've quietly built a role that depends entirely on you.

How It Happens

This shift rarely happens overnight.

It's a series of small decisions.

A quick approval.

A problem you solve because it's faster.

A conversation you join because you already know the answer.

A task you take back because it wasn't done exactly the way you would have done it.

Individually, none of these decisions seem significant.

In fact, they often feel helpful.

Responsible.

Efficient.

But over time, they create a pattern.

Your team learns that you're the fastest path to an answer.

Vendors learn you're the person who can make a decision.

Clients learn you're the person who can solve the problem.

And slowly, almost without realizing it, everything begins routing through you.

The business becomes dependent on your availability.

Why Working Harder Makes It Worse

When things begin slowing down, most high performers respond the same way they've always responded.

They work harder.

They stay later.

They answer more questions.

They become more involved.

They double-check more things.

From the outside, this looks like dedication.

From the inside, it feels like responsibility.

But operationally, it's often the exact opposite of what the business needs.

Because every time you step in, you reinforce the belief that important work requires your involvement.

You become the bottleneck without intending to.

Not because your team lacks capability.

Because you've unintentionally trained the organization to depend on you.

The Difference Between Ownership and Support

One of the most common leadership mistakes is confusing support with ownership.

Supporting your team means providing direction, resources, and accountability.

Owning everything means becoming the final decision-maker for every issue.

The difference seems small.

The impact is enormous.

When leaders own too much:

  • Decisions slow down.

  • Team confidence decreases.

  • Initiative drops.

  • Accountability becomes unclear.

  • Growth becomes harder.

Eventually, the organization reaches a ceiling.

Not because the market changed.

Not because the team isn't talented.

Because too much depends on one person.

The Property Management Version of This Problem

We see this constantly in property management companies.

A broker-owner starts by doing everything.

Leasing.

Maintenance approvals.

Owner communication.

Vendor management.

Escalations.

Hiring.

Financial oversight.

As the company grows, some of those responsibilities get delegated.

But the decisions don't.

Every unusual situation still gets escalated.

Every difficult conversation still lands on the owner's desk.

Every exception still requires approval.

The workload may be distributed.

The ownership isn't.

The result is predictable.

Growth slows.

Teams become hesitant.

Owners become overwhelmed.

And everyone wonders why adding more people didn't solve the problem.

The Real Problem Isn't Capacity

Most leaders assume they're overloaded because they have too much work.

Often, the real issue is that they've become the point through which work must pass.

That's a design problem.

Not a capacity problem.

Hiring more people won't fix it.

Better software won't fix it.

More meetings definitely won't fix it.

What fixes it is redesigning how decisions move through the organization.

Who owns what?

Who decides what?

Who is accountable for outcomes?

And most importantly:

What truly requires your involvement?

Questions Worth Asking

If you're feeling overwhelmed, start here:

What decisions am I making that someone else could make?

What approvals am I giving that shouldn't require my approval?

What work keeps coming back to me?

Where have I become the default answer?

What would stop if I disappeared for two weeks?

The answers are often uncomfortable.

They're also incredibly revealing.

Because they show you where dependency has quietly replaced leadership.

Building a Role You Actually Want

The goal isn't to stop caring.

The goal isn't to become less involved.

The goal isn't to remove yourself from the business.

The goal is to create a role that focuses your attention where it creates the most value.

Strategy.

Direction.

Vision.

Leadership.

Those are difficult to scale when you're buried in operational decisions.

And those are often the first things leaders sacrifice when everything depends on them.

The irony is that the harder you work, the less capacity you have for the work that actually matters.

That's why so many high performers eventually find themselves trapped in jobs they never intended to create.

Not because they failed.

Because they succeeded in becoming indispensable.

And then built a business that couldn't move without them.

The question isn't whether you're working hard.

The question is whether the business works because of you—or whether it can work without you.

Because those are two very different things.

And one of them scales.

back