Nobody teaches you how to fire someone, and everyone on your team will remember how you did it. Be direct, be kind, be fast. State the decision, the reason, and the logistics in ten minutes. Do not debate, do not offer false hope, and do not blame them. How you handle this defines your culture. Direct, kind, fast, ten minutes, with the logistics handled before the meeting starts.
Performance management starts with clear expectations
Most performance problems are expectation problems. The employee thinks they are doing well. The manager thinks they are not. Both are surprised at the review. The fix is not more feedback. It is clearer expectations set earlier. Every role should have a written description of what success looks like at thirty, sixty, and ninety days.
After ninety days, the expectations shift from learning to performing. The review should be a thirty-minute conversation every two weeks, not an annual event. Ask three questions: what is going well, what is not, and what do you need from me? If the answers to the second question are the same for three consecutive conversations, you have a performance problem. Address it directly and kindly.
Letting someone go is a skill you will need
Nobody teaches founders how to fire someone. It is the hardest part of building a team and the part most founders handle worst. The principles: be direct, be kind, be fast. Do not soften the message so much that the person does not understand they are being let go. Do not be so blunt that you destroy their dignity.
The conversation should take ten minutes. State the decision, the reason, and the logistics. Do not debate. Do not offer false hope. Do not blame them. If it is a performance issue, you should have been giving feedback for months, so the decision should not be a surprise. If it is a layoff, say that clearly. The person deserves to know their performance is not the reason. How you handle this conversation defines your culture more than any perk.
Culture is what you tolerate, not what you say
Every company has a culture. The question is whether it is intentional or accidental. Intentional culture comes from the behaviors you reward, the behaviors you tolerate, and the behaviors you punish. If you say you value transparency but punish people for sharing bad news, your actual culture is secrecy.
The test for your real culture: what behavior gets someone promoted, and what behavior gets someone fired? Those two answers define your culture more accurately than any values deck. If the person who hits their number but treats people badly gets promoted, your culture is results-at-any-cost. If the person who misses their number but helps the team gets a second chance, your culture is collaborative. Neither is wrong, but you should know which one you are building.
Your first five hires determine your company's DNA
Your first five hires determine your company's DNA more than any mission statement or values document. Hire for slope, not intercept. Someone who is learning fast will outperform someone who knows it all within eighteen months. The interview question that matters most is not what have you done but what would you do here in the first ninety days with what we have.
Reference checks are underrated. Not the ones the candidate gives you, but the ones you find yourself. Spend thirty minutes on the phone with someone who managed them and was not prepped. Ask one question: would you hire them again, and why? The pause before the answer tells you more than the answer itself. Trust the pause.
Design interviews to test the actual job
Most interviews test interviewing skill, not job skill. The candidate who is charming, well-prepared, and great at answering behavioral questions may be terrible at the actual work. Design interviews that simulate the job: a sales candidate should do a mock discovery call, an engineer should review actual code, a marketer should critique your actual content.
The working session interview is the most predictive format. Give the candidate a real problem from your business, thirty minutes of context, and sixty minutes to work through it with you. You learn how they think, how they handle ambiguity, and how they collaborate. They learn what the job actually involves. Both sides make a better decision.
Frequently asked questions
How do you fire someone the right way?
Be direct, be kind, be fast. State the decision, the reason, and the logistics in ten minutes. Do not debate, do not offer false hope, do not blame them. The team watches how you handle this.
When is it time to let someone go?
When you have given clear feedback, a real chance, and honest warnings, and nothing changed. The mistake is almost never firing too fast; it is performing hope for six months past the answer.
What should I never do when firing someone?
Surprise them. If the conversation is a shock, the failure started months earlier in the feedback you avoided. By the meeting, they should know it is coming. Surprises are what turn into lawsuits and public posts.
How do I handle the team after a firing?
Tell them the same day, briefly: the person is gone, you wish them well, here is how the work is covered. No details, no criticism. How you talk about the departed is how the team expects you to talk about them.
Should I offer a performance improvement plan first?
Only if you genuinely believe it can succeed. A plan designed as cover for a decision already made wastes everyone's month and teaches the team that plans mean firing. Use it as a tool or not at all.