Before You Fire Anyone: The Three Sanity Checks

Letting someone go is one of the most emotionally expensive tasks in leadership. Before you decide, run these three checks. They prevent “accidental cruelty”
(firing someone for a problem you created) and “accidental chaos” (keeping someone when the team is paying the price).

1) Is the role clearand is it still the same role you hired for?

Startups mutate jobs like it’s their business model. The “scrappy generalist” you hired might now be expected to run a repeatable process, manage stakeholders,
and forecast outcomes like a tiny CFO. If the job is different, confirm you’ve re-set expectations in plain English:
What does great look like this month? What numbers or outcomes define “meeting expectations”?

2) Did they have a real chance to succeed?

Not a motivational poster chance. A practical one: onboarding, tools, access, context, and a manager who gives usable feedback.
If expectations were vague, feedback was annual-only, or priorities changed weekly, you might be looking at a system problem wearing an employee costume.

3) Are you confusing “not like me” with “not good”?

Some people are quiet and deadly effective. Others are loud and mostly decorative. Don’t reward charisma and punish calm competence.
When you evaluate someone, focus on outputs, reliability, and impactnot vibe, style, or whether they laugh at your jokes in Zoom.

The Signs It’s Time to Move On (Founder Edition)

There’s no single “fireable offense” required to justify moving on (legally and ethically, always follow HR guidance and local laws).
But there are patterns that reliably predict you’ll keep paying for the mismatch. Here are the clearest signsespecially in SaaS teams where speed,
trust, and ownership are oxygen.

Sign #1: You’re doing a lot of their job (and you’ve started calling it “helping”)

Coaching is normal. Chronic compensation is not. If you find yourself writing their emails, finishing their decks, double-checking every deliverable,
or “just taking that customer call” because it’s faster than explaining it againyour role has silently become “part-time manager, part-time substitute.”

Sign #2: Deadlines slip without warning (and the surprise is always on you)

Great people miss deadlines sometimes. Great people also raise a flag early, propose a new plan, and protect downstream teammates.
A consistent pattern of “Oh, I thought it was next week” is not time managementit’s reliability debt.

Sign #3: They refuse to own a measurable outcome

In SaaS, most roles can be connected to a number: retention, cycle time, pipeline quality, time-to-resolution, activation, NPS themes, feature adoption,
expansion motions, onboarding completionsomething. If someone won’t own a KPI, they’re often hiding from accountability.

Sign #4: They don’t ask for helpbecause they’re hiding the problem

This one is sneaky. The issue isn’t independence; it’s concealment. When someone disappears into silence instead of escalating risk,
they turn manageable problems into urgent crises. And the team learns a brutal lesson: “You only get attention when everything’s on fire.”

Sign #5: “I’m very busy” is their permanent personality

Everyone’s busy. High performers still find a way to unblock others, reduce friction, and move the ball forward.
A perpetual “busy” posture often means poor prioritizationor a habit of looking occupied instead of being effective.

Sign #6: They push back on core parts of the job

Healthy pushback is about priorities. Unhealthy pushback is “That’s not really my thing” applied to essential responsibilities.
If you consistently have to take core work off their plate, the role is already being re-written around their preferences.

Sign #7: They argue decisions in public and erode execution

Debate is good. Undermining is expensive. If someone turns every decision into a public trialespecially after the team aligns
you get a culture of hesitation. The team stops executing and starts spectating.

Sign #8: They get angry when they fall behind (instead of stepping up)

Under pressure, people reveal their operating system. Some ask, “What do we need to do to fix this?” Others get defensive, blame-y, and emotionally loud.
If the pattern is defensiveness over improvement, coaching becomes a treadmill: lots of motion, same location.

Sign #9: They blame othersor gossip becomes their side quest

Occasional venting is human. Persistent blame and gossip is corrosive. High performers notice when low performers stay protected by excuses.
Over time, you don’t just lose productivityyou lose standards.

Sign #10: They hire mediocre people under them (or lower the bar quietly)

One mediocre hire can be a mistake. A leader who consistently recruits weaker talent is a multiplier of mediocrity.
It’s also a sign they may feel threatened by excellenceor simply can’t recognize it.

Sign #11: They take excessive management time to keep “on track”

If a person requires constant follow-up, repeated re-explaining, and frequent rescue missions, the team is paying an invisible tax.
At some point, you’re not managing performanceyou’re performing the job through them.

Sign #12: Trust breaksespecially through dishonesty

Here’s the line in the sand. If someone lies about progress, deadlines, results, or who did the work, you no longer have a performance problem.
You have a trust problem. Trust problems don’t scale. They explode.

Sign #13: Customers or security are at risk

If the employee’s behavior creates compliance risk, mishandles sensitive data, consistently harms customer relationships, or triggers safety concerns,
speed matters. You can be compassionate without being slow.

Fixable vs. Fatal: How to Tell the Difference

Not every underperformance story ends in termination. Some end in clarity, training, or a better-fitting role. The key is diagnosing the type of issue.

Usually fixable

• Skill gaps (they can’t do it yet): training, pairing, clearer examples, better tooling.
• Context gaps (they don’t know why it matters): connect work to customer and business outcomes.
• Priority gaps (too many “urgent” items): tighten the roadmap, define top 1–3 outcomes, reduce thrash.
• Role mismatch (right person, wrong seat): consider a different scope if performance history suggests strength elsewhere.

Often fatal

• Dishonesty (trust is gone).
• Repeated disrespect (toward teammates, customers, or boundaries).
• Persistent refusal to own outcomes (avoidance becomes the job).
• Culture erosion (gossip, blame, undermining leadership, chronic negativity).
• “Coaching immunity” (feedback doesn’t stick; the same issues return like a sitcom rerun).

A useful rule: if the problem is primarily capability, you can often improve it. If the problem is character or trust,
you’re usually negotiating with gravity.

A Fair Process That Doesn’t Turn Into a Soap Opera

The best terminations are rarely “sudden.” They’re the end of a clear, documented process that gave the employee a real shotand gave the company a clean record.
Work with HR/legal where possible, especially across states and countries. (Yes, it’s boring. It’s also cheaper than being interesting in court.)

Step 1: Build a “facts, not vibes” record

Write down specific examples tied to expectations: missed deadlines, quality issues, customer complaints, broken commitments, or behavioral problems.
Avoid moral judgments (“lazy,” “bad attitude”) and capture observable reality (“missed three committed delivery dates without notice”).

Step 2: Run a short, explicit improvement window

If improvement is plausible, use a structured plan (often 30–90 days). The plan should include:

• Clear goals (measurable outcomes, not vague intentions).
• Support (training, buddying, weekly check-ins).
• Milestones (what “good progress” looks like by week 2, week 4, etc.).
• Consequences (what happens if goals aren’t met).

Important: a performance improvement plan (PIP) should not be a theatrical prop. If you’ve already decided to terminate no matter what, don’t pretend it’s a
“development plan.” That’s how you end up with distrust, resentment, and a Glassdoor novella.

Step 3: Decide quickly once the pattern is proven

Once it’s clear the person isn’t meeting expectationseven with supportdelaying doesn’t become kinder. It becomes louder.
The cost shows up as rework, slow decision-making, stress on high performers, and a creeping sense that standards are optional.

Step 4: Prepare a transition plan before the meeting

Know who will own the work, what customers need coverage, what access must be removed, and how you’ll communicate internally.
This is not about being cold. It’s about not turning the company into a scavenger hunt the day after.

How to Run the Termination Meeting (Humanely)

The goal of the meeting is clarity and dignity. Not debate. Not therapy. Not a surprise episode of “Let’s Review Every Mistake Since Q1.”

Do this

• Pick a private place and a time that minimizes spectacle.
• Be direct early: don’t open with “How was your weekend?” unless you want the emotional whiplash award.
• Keep it brief and job-related.
• Have a witness (typically HR/People) when appropriate.
• Be prepared with final day details, benefits info, and next steps.

Don’t do this

• Don’t argue or relitigate. The decision is made.
• Don’t overload details. More words often create more hooks for conflict.
• Don’t outsource the discomfort entirely. If you’re the manager, you should lead the message (with HR support).

A simple script you can adapt

“Thanks for meeting with me. I need to let you know that today is your last day with the company.
The reason is that the role requires consistent performance in [specific expectations], and we haven’t seen the necessary improvement
after our feedback and support. This decision is final. Here’s what happens next: [final pay/benefits/returning equipment/access].
I know this is a lot to take in. Do you have any questions about the logistics?”

Notice what’s missing? A lecture, a rant, a motivational speech, or an invitation to negotiate. You can be kind and still be clear.

Offboarding: Protect the Company and the Human

Great offboarding is part security, part empathy, and part operational hygiene. When it’s done well, the team keeps moving and the departing employee leaves
with less confusion and fewer “What do I do now?” spirals.

Operational checklist

• Disable access to systems, email, and shared docs at the right time (coordinate with IT).
• Collect company property (laptop, badge, keys, devices).
• Confirm final pay timing and any accrued PTO rules (often state-specific).
• Provide benefits info and any required notices; explain next steps clearly.
• Transfer knowledge: projects, key contacts, open customer items, and where files live.

Human checklist

• Treat them like an adult: direct, respectful, no humiliation.
• Offer practical support where appropriate (references depend on policy and situation).
• Close the loop: how the team will proceed, who they can contact for benefits/questions.

One more founder note: “We’ll figure it out later” is a lie you tell yourself. If the employee holds institutional knowledge, plan a clean handoff.
If you can’t, that’s a hiring and documentation lesson for next timenot a reason to delay a necessary decision forever.

What to Say to the Rest of the Team

The team will notice. They’ll speculate. Some will be relieved. Some will be anxious. Your job is to restore clarity and safety without oversharing private details.

Keep it simple

“X is no longer with the company. We appreciate their contributions and wish them well. Here’s how responsibilities will be covered:
[plan]. If you have questions about priorities, come to me.”

Reinforce standards and support

If the departure follows performance issues, you can reinforce that the company sets clear expectations, provides feedback, and holds the bar.
That combination builds trust. People don’t fear accountability; they fear randomness.

A Founder’s Shortcut: The “Two Questions” Test

When you’re stuck, ask:

1. If I were hiring for this role today, would I hire this person again?
2. If a top performer came to me privately and said “Why are we keeping this?” what would I say?

If the honest answers are “no” and “I don’t have a good explanation,” you’re likely past the point of helpful waiting.
You’re in the zone where delaying quietly punishes the people who are performing.

Experience-Based Lessons to Help You Nail This Next Time (An Extra )

The hardest part of letting someone go is that it rarely feels like a single, dramatic moment. It’s usually a slow drip of evidence:
one missed deadline, then another; one weird customer call; one team complaint you “assume will pass”; one more week where you’re personally patching the gap.
In founder stories, the regret is rarely “I moved too fast.” It’s almost always “I waited until it was obvious to everyone.”

Lesson 1: Speed isn’t crueltyconfusion is

People can handle hard news better than they can handle ambiguous, ongoing disappointment. When expectations are unclear, employees often feel punished without
understanding the rules. When expectations are clear and the decision is timely, the employee can move forward faster (even if they’re upset in the moment).

Lesson 2: The team experiences your delay as a policy choice

High performers watch what you tolerate. If one person repeatedly misses commitments and nothing changes, the signal is not “We’re compassionate.”
The signal is “Commitments are optional.” That’s how strong cultures quietly weakennot through a dramatic scandal, but through a thousand small exceptions.

Lesson 3: The most expensive cost is the work you don’t see

Underperformance creates invisible work: rechecking, redoing, translating, smoothing customer relationships, and “just in case” status meetings.
Founders often underestimate how much time the team spends compensatingbecause the compensation work is scattered across Slack threads and late-night fixes.
A single low performer can quietly slow multiple people.

Lesson 4: “Good enough” doesn’t scale when the company changes shape

Early-stage companies can survive on heroic effort and improvisation. Later, you need repeatable systems and predictable execution.
A “good enough” employee may have been fine when the scope was smaller. As the business grows, the same performance becomes a bottleneck.
That’s not moral failure. It’s mismatch at a new stage.

Lesson 5: PIPs work best when the employee still believes they can win

When improvement plans succeed, it’s usually because the employee is motivated, the goals are measurable, and the manager is actively supportingnot just monitoring.
When they fail, it’s often because the plan is vague (“be more proactive”), the targets are unrealistic, or the relationship is already poisoned by distrust.
A PIP should feel like a structured rescue attempt, not a paperwork parade.

Lesson 6: Your language matters more than your speech length

In tough conversations, leaders sometimes ramble to soften the blow. Unfortunately, rambling creates loopholes:
“So… am I fired or not?” Aim for fewer words, clearer meaning, and calmer tone. You can acknowledge emotion without inviting negotiation:
“I understand this is difficult” is kind. “Maybe in a few months…” is chaos.

Lesson 7: Build the “exit ramp” into your hiring and management system

Many messy terminations begin with fuzzy hiring and fuzzy onboarding. The fix is boringand it works:
define success metrics early, run 30/60/90-day checkpoints, document feedback, and maintain regular 1:1s with clear next steps.
When performance isn’t there, you won’t be guessing. You’ll be confirming.

Final thought: letting someone go is not a victory lap. It’s a leadership responsibility. Do it with clarity, fairness, and respectand you protect the business,
the team, and the person’s ability to find a role where they can thrive. The point isn’t to be ruthless. The point is to be real.