‍

When protecting one top performer teaches everyone else the wrong lesson.

The Decision

Every founder knows exactly who I am talking about.

It's the employee you've convinced yourself is irreplaceable. The employee everyone else at the company has learned to work around because you haven't dealt with their behavior.

Maybe it's your best engineer. Or maybe they own your biggest customer relationships. Perhaps its a leader that has been with you since the very beginning and helped build the company. Every founder has a reason for keeping them. And that is what makes this decision so difficult.

Then you convince yourself this exception is temporary. We'll deal with it after the launch. After the fundraise. After we hire a few more people. Once things settle down. They are the realities of building a business.

But the organization thinks you've established a rule. Employees don't know what you've been weighing behind closed doors or why you've decided to wait. They're learning whether performance outweighs character and whether accountability is applied equally. Most importantly, they're learning what standards you are willing to tolerate.

This playbook isn't about a difficult employee. It's about the moment a founder realizes they're no longer managing one person's behavior. They are teaching an entire organization what is tolerated.

The Cost of Keeping Them

When founders think about letting someone go, they almost always start by calculating what they will lose.

Who will take over their work?

What happens to our biggest accounts?

How long will it take to replace them?

Can we afford to lose this much institutional knowledge?

Those are real questions. They're also the easiest ones to answer because they have numbers attached to them. Lost revenue. Delayed product launches. Recruiting fees. Time.

The harder question is this:

What is it costing you to keep them?

Over the last six months, how much leadership capacity has this one person consumed? Not just yours, but your leaders', who spend time coaching frustrated employees, resetting expectations, and managing around a problem they've stopped believing will change.

Those hours have a cost.

And they compound.

One leader decides it's easier to work around the problem than address it. Another stops giving difficult feedback because leadership already made the hardest exception. A B player quietly lowers their own standard because they've learned standards aren't applied equally.

The irony is that your top performer usually isn't the person changing your culture.

Your average performers are.

They're watching how you respond, then adjusting their own behavior accordingly. They're not asking themselves whether they should behave like your highest performer.

They're asking something much simpler.

"How serious are we about our standards?"

Ask Yourself These Questions

Before you decide what to do, stop thinking about the employee and start thinking about the company.

Take fifteen minutes.

Answer these questions honestly.

If this person interviewed for the role today, knowing everything you know now, would you hire them?

If your newest employee behaved the same way, how long would they last?

What have your leaders learned from watching you manage this person?

What has the rest of the company learned?

You might also be asking yourself whether they simply need a different role.

Maybe they do.

Sometimes the right decision isn't firing them. It's changing the role, the manager, or the environment.

Before you make that move, ask yourself a few more questions.

Are you solving the problem or just shifting it?

If this person moves to another team, does the behavior move with them?

Would your leadership team see this as a thoughtful business decision, or another exception?

Are you rewarding potential or avoiding accountability?

A new role should solve a business problem.

It should never become a reward for behavior you weren't willing to confront.

Why Wait?

Most Executives and Founders don't avoid difficult decisions. They postpone them. And postponed decisions have a habit of becoming permanent ones.

So put a date on it. Not "later." Not "when things settle down." A date.

Then ask yourself:

What has to be true by then for this person to remain on your team.

What specific behaviors must change?

What commitments must be met?

What would convince you this person has changed a corner?

Write those answers down.

Because if that date comes and nothing meaningful has changed, you haven't failed to make a decision.You've made one. You've decided the standard isn't worth enforcing.

Founders usually ask themselves one question.

"Can we actually afford to lose this person?"

It's the wrong question. The better question is:

Are your standards what you say they are, or what you tolerate? Your reputation is built on the difference.