When and How to Let Someone Go at a Startup

Most founders wait too long to let someone go. Not because they're heartless — because they're the opposite. They give the benefit of the doubt, hold out for improvement that never comes, and in the meantime, the rest of the team notices and adjusts their expectations downward. A firing that happens six months too late is almost always more damaging than one that happens at the right time.

Performance vs. Culture Fit: Different Problems, Different Process

Before you can handle a departure well, you need to be clear which kind of problem you have.

Performance issues are about capability or output. The person isn't delivering results against a defined standard. These are addressable through a structured improvement process and should be documented.

Culture fit issues are different. The person is technically capable but their behavior is misaligned with how the team needs to work — they undermine trust, create drama, communicate in ways that damage relationships, or can't operate with the autonomy the role requires.

Culture fit issues are often harder to articulate but easier to act on quickly. You don't have to run a performance improvement plan for someone who's eroding team trust. Document the specific behaviors, give clear feedback once that this is serious, and if nothing changes, move.

The Pattern to Watch For

The clearest signal that it's time to act: you've told them something once, directly, and you're watching the same behavior repeat. A second conversation is appropriate. A third means you've lost the thread.

When Is It Actually Time?

Some questions that clarify the decision:

• Would you hire this person again today, knowing what you know? If no, that's your answer.
• Are you keeping them because of their future potential or their current contribution? Potential that hasn't materialized in a reasonable timeline isn't a reason to stay.
• How are others on the team behaving because of this person? If they're compensating, avoiding, or disengaging, the cost is already real.
• Have you been honest with them about the problem? If not, that's your next step — not a termination.

One important distinction: if the issue is clear-cut misconduct (harassment, dishonesty, something that creates legal exposure), don't run a performance process. Talk to an employment lawyer and move quickly.

The Conversation

There's no kind way to deliver this news, but there are less traumatic ways. A few principles:

Be direct and don't bury the lede. Start with the decision: "I need to let you know that today is your last day." Not: "There are some things I've been thinking about that I want to share with you..." People know what's coming and the delay only extends the pain.

Be honest about the reason, without being brutal. "This role isn't the right fit for where the company is" is true and doesn't require a detailed catalog of their failures. If they want specifics, give them honestly and without malice.

Keep it short. 15-20 minutes is appropriate. This is not a negotiation or a feedback session. Be clear, be kind, be done.

Logistics matter. Have a plan for access (when do they return equipment, when does access get revoked), severance if applicable, and what you'll say publicly. Don't leave them guessing.

Documentation

For any performance-related termination (not misconduct), you should have a paper trail: written feedback shared, specific expectations set, any formal PIP if you ran one. This isn't just for legal protection — it means the person can't credibly claim the termination came out of nowhere, because it didn't.

For culture fit departures, document the specific behaviors you flagged in your conversations. Keep it factual, not interpretive.

Protecting the Team's Morale

How you handle the departure is being watched by everyone who stays. They're asking: would they treat me this way?

Be respectful in exit. However you feel about the departure, handle it with dignity. Your team will remember that.

Communicate quickly and clearly. Don't let rumors fill the vacuum. Inform the team the same day, with a short message: "[Name] is no longer with the company. I'm not going to share details, but I'm available to talk if you have questions." Don't overshare.

Don't badmouth the person. Even if the departure was ugly, publicly criticizing someone you let go tells the team you'll do the same to them.

Be available. People often need a few days to process. Check in with key team members individually, especially if the departed person was close to them.

---

The hardest part of letting someone go is usually the anticipation, not the conversation itself. Founders who delay often describe the aftermath as a relief — and are surprised to learn that the team already knew something was wrong and is relieved too. Move when it's clear. The kindest version of a difficult decision is a timely one.