How to Fire a Friend (and Actually Stay Friends)

I knew for four months before I said anything.

He was employee number four, and he was my friend before he was anything on an org chart — the guy who helped me move a couch in my twenties, who was at the hospital the night my first kid was born. I'd hired him into a role the company was outgrowing faster than he was. Everyone could see it. He could see it. And I sat on the decision for a full quarter because firing him felt like firing the friendship, and I wasn't willing to lose the friend.

Here's what those four months actually bought me: a weaker team, a guy who knew he was failing and got to marinate in it, and a friendship that was already curdling under the avoidance. The thing I was protecting was dying anyway — I was just letting it die slowly. This is the part nobody tells you about how to fire a friend: the longer you wait, the more damage you do to the exact relationship you're trying to save.

How do you fire a friend and still keep the friendship?

How do you fire a friend and still keep the friendship? You separate the two relationships out loud: the role is ending, the friendship is not. Decide privately and firmly before the meeting, deliver the news plainly without hiding behind process, be generous on the exit, and name a specific way you'll stay in each other's lives afterward.

That's the whole move, and every word matters. The role is ending — not the person, not the bond, not the years. Most founders fail because they let the two blur, so the friend hears "you're not good enough for me anymore" instead of "this seat isn't right for you." Keep those two things in separate hands and never let them touch.

Why founders end up firing friends in the first place

Nobody hires a friend planning to fire them. It happens because of how early companies actually get built. In the first eighteen months you don't hire the best person available — you hire the person who'll answer the phone at 11pm and work for equity and a prayer. Almost always someone who already trusts you. A friend. The buddy from your last job.

It's the right call at the time. The problem is that startups change job descriptions every six months, and friendships don't come with performance reviews. The role sprints ahead; the friend stays the friend you hired. One day the company needs a VP where you have a guy who's great in a crisis but can't build a system, and you're the one who has to notice.

This isn't a character flaw in him or in you. It's structural. The reasons that made him the perfect early hire — loyalty, trust, history — are the exact reasons you'll struggle to let him go when the seat outgrows him.

The core mistake: treating the role and the friendship as one thing

The single error underneath every botched friend-firing is collapsing two separate relationships into one. There's the professional relationship — boss and employee, a job with requirements. And the personal one — two men who'd show up at each other's funerals. They overlap, but they are not the same circle.

Avoid the decision and you're treating them as one circle — ending the job feels identical to ending the bond, so you do neither. Fire badly — cold, over Slack — and you're treating them as one circle from the other side, letting the professional cut sever the personal tie.

The men who pull this off hold the line between the two circles on purpose. Harvard Business Review's guidance on firing with compassion makes the same point from the management side: don't outsource the conversation, don't wait for a "firing offense," and be willing to let go of friends and family when the role demands it. The compassion isn't in softening the decision. It's in owning it cleanly and treating the person with respect on the way out.

The Clean Cut: a five-step framework for firing a friend

When I finally did it — and in the handful of times I've coached other founders through it since — the same five steps held. I call it the Clean Cut, because the whole goal is one decisive line instead of a slow tear.

1. Decide privately, and make it final. Walk into the room having already decided. If part of you is still hoping he'll talk you out of it, you'll signal that, and you'll turn a clean cut into a negotiation. The decision is made before the meeting starts.

2. Name the two relationships in the first thirty seconds. Open with it: "I'm here as your boss, and this is hard because you're also my friend. I need to talk about the job, and I want to protect the friendship while I do it." Now both circles are on the table, named, and separated.

3. Deliver the news plainly — no fog. Say the role is ending and say why, in two sentences, without a ten-minute windup. Vagueness isn't kindness; it's you managing your own discomfort at his expense. He already knows. Confirm it cleanly.

4. Be generous on the exit. This is where the friendship is actually saved or lost. Real severance, a runway to land somewhere, a genuine reference, and a story you'll both tell the same way. Generosity here is the apology you can't make in words for keeping him in the wrong seat.

5. Name the next touchpoint before you leave the room. "Dinner in three weeks — you and me, no shop talk." A specific commitment, not a hand-wavy "let's stay in touch." The friendship survives on the calendar, same as any relationship you actually mean to keep.

Run a gut-check over the whole thing: the Thanksgiving Test. Picture this man at your table two Thanksgivings from now. If the way you're handling the exit would make that table awkward, fix it until the table stays warm.

What the conversation actually sounds like

When I finally sat down with employee number four, I didn't do it perfectly. But I did the one thing that mattered: I led with the friendship instead of the spreadsheet. I told him I'd kept him in a role that was hurting us both because I was scared of this exact conversation — and that the fear had cost him months. I owned the delay as my failure, not his.

Then I told him the role was ending, gave him a real package, and asked him to dinner in three weeks before either of us stood up. He was angry. He was also relieved — he'd known for longer than I had, waiting for me to be brave enough to say it. The anger lasted a month. The friendship is fifteen years old now and intact.

Contrast that with a founder I know who did the opposite: let HR deliver the news, ducked the guy's calls afterward, and told himself the silence was "giving him space." He didn't lose an employee. He lost a friend. It was never the firing that ended friendships — it was the cowardice on either side of it.

Where it goes wrong

A few failure modes kill more of these friendships than the firing itself.

Slow-walking the decision. Every week you wait, the friend absorbs more failure and more proof you don't have his back. Speed is a form of respect.

Hiding behind process. "The board decided." "HR's handling it." He can smell the dodge, and it tells him the friendship couldn't survive your honesty. Own the call as yours.

Going cheap on the exit. Skimping on severance to save a few dollars is the most expensive thing you can do here — you're buying back a fifteen-year friendship for the price of a month's salary. Pay it.

Over-explaining to feel better. Piling on reasons and apologies until it's about your guilt. Say it once, then let him react. The conversation is for him, not your conscience.

The bottom line

Firing a friend is the hardest leadership move there is, and most founders get it wrong in the same two ways: they wait too long, then they hide when they finally do it. Neither protects the friendship — both quietly kill it. The way through is the Clean Cut: decide for real, name the two relationships out loud, deliver the news plainly, be generous on the exit, and put the next dinner on the calendar before you leave the room. Do that, and you don't have to choose between the company and the friend. You can keep both — you just have to be brave enough to separate them. Strong relationships, the kind Gallup's research on close friendships at work keeps tying to engagement and loyalty, don't break because of one hard conversation. They break from the avoidance around it.

This is the kind of call you shouldn't make alone. The kind of room where you can pressure-test a call like this — peers who've fired a friend and kept him — is exactly what REBL Dads is built for.

Want more on the hard, lonely parts of leading? Get it in the REBL Dads newsletter, and look for these themes in our upcoming book featuring 100 fathers.

REBL Dads Editorial is the voice of the REBL Dads brotherhood — founders, operators, and fathers who refuse to run their lives on autopilot.