How to Let Someone Go With Dignity

The first person I ever let go, I did badly. It was 2011, I was a newly minted team lead, and I had rehearsed the meeting so many times in my head that when he...

Originally published onanselmfowel.com

The first person I ever let go, I did badly. It was 2011, I was a newly minted team lead, and I had rehearsed the meeting so many times in my head that when he walked in and sat down I skipped straight to the sentence that mattered and then filled the silence with reasons. Fourteen minutes of reasons. He deserved four sentences and a clear next step, and instead I gave him a defense of a decision that was already made. He never raised his voice. He just looked tired, and I have never forgotten the look.

Since then I have had to end a lot of employment: performance cases, restructures, one acquisition that quietly deleted half a department. I am not going to pretend I enjoy any of it. But I have learned that letting someone go with dignity is a skill, not a personality trait, and that most managers are bad at it for reasons that are fixable. This is what I wish someone had told me at that first meeting.

Dignity is not softness

People hear the word dignity and assume it means going gentle, softening the blow, dressing the thing up. That is exactly backwards. The single most undignified thing you can do to an adult is be unclear with them about whether they still have a job. Ambiguity is the cruelty. I have watched managers spend forty minutes talking around a termination because they could not bring themselves to say the words, and the person left the room genuinely unsure whether they had been fired or given a stern warning.

Dignity means you treat the person as a competent adult who can handle the truth and make decisions with it. That means the truth arrives early, plainly, and without a fog of euphemism. It means you do not make them do the work of figuring out what you actually mean. Respect, in this context, is mostly a synonym for clarity delivered on time.

The decision should already be made

A termination meeting is not a negotiation and it is not a debate. If you walk in still ninety percent sure, you have no business being in that room. The decision has to be finished before the door closes, because the moment you leave a crack of ambiguity, a reasonable person will try to pry it open, and then you are relitigating months of context in real time while both of you are flooded with adrenaline. Nobody thinks well in that state.

This is also why I am ruthless about the paper trail on the way in. Before I ever schedule the conversation I want to be able to answer three questions cleanly: what specifically did not work, what did we do to try to fix it, and why is the door genuinely closed now. If I cannot answer all three without hand-waving, the person is not ready to be let go, I am just frustrated. Those are different problems and they have different solutions. I once caught myself about to fire an engineer who had never actually been told, in plain language, that his work was below the bar. That is not his failure. That is mine, and firing him would have been laundering my own management debt onto his record.

The rule of no surprises

For performance cases, the meeting where you end the job should be the least surprising conversation of the whole process. If the person is genuinely shocked, something upstream broke. Either the feedback never landed, or it landed so gently that it read as a suggestion instead of a warning. I hold myself to a simple standard here: by the time we get to the end, the person should have heard the specific concern at least three separate times, in words they could not mistake for encouragement.

The kindest firing is the one the person half expected. The cruelest is the one that comes out of a clear sky after a year of positive-sounding reviews.

Restructures and redundancies are different, and I want to be honest about that. When a role is cut for business reasons, the person often could not have seen it coming, and pretending otherwise is insulting. In those cases you do not owe them a warning they could not have acted on, but you owe them something else: a crisp explanation that it is the role and not the person, and enough specificity that they believe you. Nobody believes it is the role and not them if you cannot say a single concrete thing about why the role went away.

How to run the actual meeting

Keep it short. The whole thing should run ten to fifteen minutes, and the decision itself belongs in the first ninety seconds. I lead with a clear line, something close to: I have some difficult news, we have made the decision to end your employment, and I want to walk you through what happens next. Then I stop talking and let it land. The silence is uncomfortable and you have to let it be uncomfortable. Do not rush to fill it. That first pause is you handing them a moment to react like a human being, and taking it away is a small theft.

A few things I have learned to hold firm on, most of them the hard way:

  • Do not give a laundry list of reasons. One or two sentences of honest context, then move to logistics. Reasons offered after the decision read as justification, and justification invites argument.
  • Never say you know how they feel. You do not, and it is not about you.
  • Have the practical details ready on paper: last day, severance, benefits continuation, equity treatment, what happens to their laptop. A person in shock cannot retain a verbal list, and fumbling these details signals that they were an afterthought.
  • Have a second person in the room for anything sensitive, usually someone from HR. Not as a heavy, but as a witness and a source of accurate answers about benefits I might get wrong.
  • Never schedule it for a Friday afternoon into a weekend of silence with no one to call. Mid-week, mid-morning, with the afternoon free to handle whatever comes.

What you actually owe them

Generosity here is not charity, it is proportionate. Someone gave you two years of their working life; the exit should reflect that, not the accounting department's worst instincts. I fight for severance that gives people real runway, not a token two weeks, and I fight to keep health coverage running through the transition wherever the jurisdiction and the plan allow it. In fintech we operate in enough regulated markets that the specifics vary wildly, and I have learned to bring the actual numbers to the meeting rather than promises I have to walk back later.

On equity, be honest and be early. The single most common way companies quietly betray departing people is through opaque handling of vested options and short exercise windows, and the person often does not understand what they are losing until it is gone. If someone has vested equity, they should leave the meeting knowing exactly what they hold, what the exercise window is, and what it would cost. Making that clear will not always make them happy. Hiding it makes you a coward with a spreadsheet.

The reference you will give later

Here is a thing almost nobody plans for: the phone call you will get in eight months from someone doing a reference check. You should decide, at the time you let the person go, what you are going to say when that call comes, and you should tell them what it will be. A person who is being let go for fit or for a role cut, rather than for misconduct, deserves to know they can put you down and that you will speak well of the parts that were genuinely good.

I keep a private note after every difficult exit with two or three true, positive, specific things about that person's work. Not vague warmth, specifics: shipped the reconciliation service under a brutal deadline, was the only one who understood the settlement edge cases, mentored two juniors well. When the call comes I read from that note. It costs me nothing and it can meaningfully change someone's next year. The people who fire badly tend to treat the departing person as if they cease to exist at the door. They do not. They have a career that continues, and you are a small permanent part of its record.

The team that stays is watching

Everyone else on your team is reading this event closely, whether they say so or not. They are not primarily asking whether the decision was correct. They are asking a quieter question: if it were me, would I be treated like a person or like a line item. How you handle one exit sets the emotional weather for everyone who remains, and a callous firing costs you trust from people you very much wanted to keep.

So say something true to the team, promptly, without oversharing. I do not narrate the departed person's failings; that is nobody's business and it teaches the survivors that you will discuss them the same way once they are gone. I acknowledge that it happened, I take responsibility for the decision as mine, and I make space for people to be unsettled. After a redundancy round a few years ago I made the mistake of going straight into an all-hands about roadmap priorities, as if nothing had happened, and the flatness in the room told me exactly how badly I had misjudged the moment. People need you to acknowledge the loss before you can ask them to look forward.

Sit with your own part in it

Every time I let someone go, I make myself write down honestly what I could have done differently, and often the answer is a lot. Hired against my gut. Ignored the first quarter of warning signs because the person was likeable. Gave feedback that was technically delivered but emotionally hedged into meaninglessness. The termination is frequently the last and most visible failure in a chain of smaller ones that were mine to prevent.

This is not self-flagellation, it is the only reliable way I know to fire fewer people over time. If you treat every exit as purely the other person's shortcoming, you learn nothing and you will be back in that chair again soon, doing it again, surprised again. The managers I respect most are the ones who have made their peace with the fact that letting someone go is sometimes necessary and always at least partly a verdict on their own judgment. Hold both of those at once. It keeps you honest and it keeps you human.

Anselm Fowel, CTO and fintech architect
Anselm Fowel — CTO & fintech architect

Conclusion

I still think about that meeting in 2011, the fourteen minutes of reasons and the tired look. What I got wrong was not the decision; the decision was probably right. What I got wrong was treating a person's worst afternoon as a problem to talk my way through, rather than a moment to be clear, brief, and generous, and then to get out of the way. If you remember nothing else, remember this: the goal is never to make the firing feel good, because it cannot and it should not. The goal is that a year later, the person can describe how they were let go without bitterness, and mean it. Aim for that. It is a higher bar than comfort, and it is the only one worth clearing.

Chat with us