It’s week 10.
You hired someone three months ago. You’ve invested £12,000 in salary, 20+ hours training them, and significant political capital with your team.
And it’s not working.
They’re not terrible. They’re just… not what you expected.
The work is slower than you hoped. They need more direction than you anticipated. The cultural fit feels off.
Your co-founder says “give them more time.” Your team is frustrated. You’re losing sleep wondering if you made a mistake.
The question keeping you up: Do you try to fix this, or do you cut your losses?
I’ve helped 400+ founders navigate this exact moment over 20 years. It’s one of the hardest decisions you’ll make because:
- You’ve already invested money and time
- You don’t want to be the “bad guy” who fires someone
- You’re second-guessing yourself (“Maybe it’s my expectations that are wrong?”)
- Starting over feels exhausting
Here’s how to recover from a bad hire. Here is the framework I use to help founders make this decision with clarity and confidence.
FIRST: ACKNOWLEDGE THE REAL COST OF KEEPING A BAD HIRE
Before we talk about fixing or firing, you need to understand what keeping a bad hire actually costs.
Most founders only calculate the obvious costs:
- Salary: £12K for 3 months, £48K annually
- Time: 20 hours of training and management
But the hidden costs are devastating:
1. Opportunity Cost
Every month you keep them is a month the work isn’t getting done properly. If this is a revenue role, you’re losing deals. If it’s a product role, you’re shipping slower. If it’s operations, things are breaking.
2. Team Morale
Your A-players notice immediately when someone isn’t pulling their weight. They start working harder to compensate (hello, resentment) or they start questioning your judgment as a leader.
I’ve seen founders lose their best people because they kept a bad hire too long. Your top performer quits because they’re “tired of carrying dead weight.”
3. Your Time and Energy
You’re spending 10-15 hours per week managing someone who should be making your life easier, not harder. That’s 10-15 hours you could be spending on product, customers, or actual growth.
4. Your Reputation
Internally: Your team wonders why you’re not addressing the obvious problem.
Externally: If this is a customer-facing role, clients are getting mediocre service.
Total cost of keeping a bad hire for 6 months:
- Salary: £24K
- Your time: 50-80 hours
- Lost productivity: £10K-£30K+ (deals not closed, features not shipped, operations breaking)
- Potential loss of A-player: £40K+ (recruiting + lost productivity)
- Team morale damage: Immeasurable
Total: £74K-£120K+ over 6 months
Letting them go and restarting costs: £24K (salary paid) + £5K-£12K (recruiting) + 2-3 months to hire = £29K-£36K
The math is brutal, but clear.
Here’s how to recover from a bade hire: THE FIX-OR-FIRE FRAMEWORK
Here’s how to decide whether this is fixable.
I use a three-question framework. Answer these honestly.
QUESTION 1: IS THE PROBLEM SKILLS OR CHEMISTRY FIT?
Skills problems are usually fixable. Fit problems rarely are.
Skills problems look like:
- They don’t know how to use your tech stack yet (but they’re learning)
- They haven’t done this specific type of work before (but they’re capable)
- They’re making mistakes because they’re new (but they’re improving)
- They need more training in specific areas (and they’re receptive to it)
Fit problems look like:
- They need constant direction (you hired for autonomy)
- They’re methodical and slow (you need speed and scrappiness)
- They want structure and process (you’re building those in real-time)
- They avoid conflict (you need direct communicators)
- They’re low energy (your team is high-energy and moves fast)
- They’re corporate in mindset (you need startup mentality)
The litmus test:
Imagine they magically gained all the missing skills tomorrow.
Would you be thrilled to work with them for the next 3 years?
If yes: Skills problem. Likely fixable.
If no: Fit problem. Unlikely to fix.
Real example:
Emma hired a developer, Tom, who was brilliant technically but incredibly slow. Emma’s startup needed to ship fast and iterate.
Tom would spend 2 weeks perfecting code that needed to ship in 3 days.
Emma asked herself: “If Tom could work faster, would he be perfect?”
Answer: No. Even if Tom sped up, his perfectionism clashed with Emma’s “move fast and iterate” culture.
That’s a fit problem.
Not fixable.
QUESTION 2: ARE THEY IMPROVING OR STAYING STATIC?
Trajectory matters more than current state.
Someone who started at 40% and is now at 60%? That’s promising.
Someone who started at 40% and is still at 40%? That’s a problem.
Signs they’re improving:
- They’re asking fewer questions each week (not more)
- They’re making different mistakes (learning from previous ones)
- They’re starting to anticipate problems before you mention them
- The quality of their work is noticeably better than week 1
- They’re taking feedback well and implementing it
Signs they’re static or declining:
- You’re repeating the same feedback with no change
- They’re asking the same questions repeatedly
- Mistakes aren’t decreasing
- They seem defensive when you give feedback
- You find yourself micromanaging more, not less
The litmus test:
Look at their work from week 4 vs. week 12. Is there visible improvement?
If yes: Give them another month and reassess.
If no: It’s time to have a difficult conversation.
QUESTION 3: DOES YOUR GUT SAY THIS IS TEMPORARY OR PERMANENT?
Trust your instincts. You know.
Your gut says temporary if:
- “They’re just adjusting. This is normal startup chaos.”
- “Once they get through X milestone, they’ll be great.”
- “They’re asking great questions and clearly engaged.”
- “I see flashes of brilliance, just not consistently yet.”
Your gut says permanent if:
- “I have a sinking feeling every time I see their name on my calendar.”
- “I’m doing mental gymnastics to justify keeping them.”
- “I’ve been telling myself ‘one more month’ for three months.”
- “I’m embarrassed to introduce them to investors/clients.”
- “My team keeps asking me when I’m going to address this.”
The litmus test:
Close your eyes and imagine them still here in 12 months, performing at this exact level.
How do you feel? Relieved they improved? Or dread that nothing changed?
Your gut knows the answer.
THE DECISION MATRIX
Based on those three questions, here’s what to do:
SCENARIO 1: SKILLS PROBLEM + IMPROVING + GUT SAYS FIXABLE
→ Fix It: Give them a clear 30-day performance plan
SCENARIO 2: FIT PROBLEM + NOT IMPROVING + GUT SAYS PERMANENT
→ Fire: Have the conversation this week
SCENARIO 3: SKILLS PROBLEM + NOT IMPROVING + GUT UNCERTAIN
→ Fix It (With Deadline): 30-day plan with clear metrics. If not hit, part ways
SCENARIO 4: FIT PROBLEM + IMPROVING + GUT UNCERTAIN
→ Honest Conversation: Tell them your concerns, see if they see it too
Let’s dive into how to execute each scenario.
HOW TO FIX IT: THE 30-DAY PERFORMANCE PLAN
If you’ve decided it’s fixable, don’t just “give them more time.” That’s vague and unfair to both of you.
Create a clear 30-day performance improvement plan:
1. Name the specific problems
Don’t sugarcoat. Be direct.
“Over the past 10 weeks, I’ve noticed these concerns:
- Tasks that should take 2-3 days are taking 7-10 days
- You’re waiting for me to assign work instead of identifying priorities yourself
- The quality of deliverables needs improvement in [specific areas]”
2. Define what success looks like
Give them measurable goals.
“Here’s what I need to see in the next 30 days:
- Complete [specific project] within 5 days (not 10)
- Proactively identify and pitch 2-3 priorities each week without me asking
- Deliverables meet [specific quality standard] without requiring multiple rounds of revision”
3. Offer support
Make it clear you’re invested in their success.
“I want you to succeed here. Here’s how I’ll support you:
- Weekly 30-minute check-ins to unblock you
- Access to [training/resources]
- Clear feedback within 24 hours of submitting work”
4. State the consequences
Be honest about what happens if they don’t improve.
“If we’re not seeing clear improvement in these areas by [date 30 days from now], we’ll need to discuss whether this role is the right fit. I’m being direct because I respect you and want you to know exactly where you stand.”
5. Document everything
Send this in writing. Have them acknowledge receipt.
This protects both of you and removes ambiguity.
30 days later:
If they’ve improved: Great. Keep monitoring.
If they haven’t: You’ve given them a fair chance. It’s time to part ways.
HOW TO FIRE WITH RESPECT: THE DIFFICULT CONVERSATION
If you’ve decided it’s not fixable, move quickly. Don’t drag it out.
Every week you delay costs you money, morale, and momentum.
Here’s how to have the conversation:
1. Be direct in the first sentence
Don’t soften the blow with small talk. Rip the plaster off.
“I’ve asked to speak with you because this isn’t working out. Today will be your last day.”
Or if you’re giving notice: “I’ve decided this role isn’t the right fit. Your last day will be [date two weeks from now].”
2. Give them the reason (briefly)
“Despite the training and support, the pace and autonomy this role requires aren’t matching your working style. It’s not about effort – I can see you’re trying – but the fit isn’t right.”
Don’t list 15 things they did wrong. Don’t negotiate. Don’t apologise excessively.
3. Outline the practical next steps
“Here’s what happens next:
- You’ll be paid through [date]
- We’ll provide a reference that confirms your employment dates and role
- [HR person/I] will walk you through final paperwork”
4. Keep it short
This conversation should be 10-15 minutes maximum. Don’t let it turn into a 2-hour debate.
They may want to argue, negotiate, or ask for “one more chance.”
Hold firm: “I understand this is disappointing. The decision is final.”
5. Handle the team communication
Same day, tell your team:
“[Name] is no longer with the company as of today. The role wasn’t the right fit for what we need at this stage. We’ll be moving forward with [plan for coverage]. If you have questions, let’s talk individually.”
Don’t badmouth them.
Don’t overshare.
Keep it professional.
THE EMOTIONAL SIDE: HOW TO HANDLE GUILT
Let’s address the elephant in the room: This will feel terrible.
You’re going to feel guilty. You’re going to second-guess yourself. You’re going to worry you’re a bad person.
Here’s the truth:
Keeping someone in the wrong role is crueler than letting them go.
You’re wasting their time in a role where they’re failing and miserable. They could be thriving somewhere else – in a corporate environment if they need structure, in a different industry if they need bigger budgets, in a role that matches their working style.
By letting them go, you’re giving them the chance to find the right fit.
And you’re protecting your team, your company, and your ability to hire great people in the future.
Firing someone doesn’t make you a bad person. It makes you a responsible leader.
WHAT TO DO NEXT: HIRE BETTER THE SECOND TIME
Once you’ve parted ways, you have two choices:
1. Hire DIY again (and hope you get it right this time)
2. Hire differently (with a process that tests for fit, not just skills)
If you’re here because your first hire didn’t work out, the job description and interview process probably missed something critical.
Most founders hire on:
- Impressive CV
- Strong interview performance
- Relevant experience
But they don’t test for:
- Working style compatibility
- Comfort with ambiguity
- Self-direction vs. needing structure
- Speed vs. perfectionism
- Cultural values alignment
That’s why Chemistry First hiring works: it tests these things before you hire, not after.
THE BOTTOM LINE
If it’s a skills problem, they’re improving, and your gut says fixable: Give them a clear 30-day plan with measurable goals.
If it’s a fit problem, they’re not improving, or your gut says it won’t work: Have the conversation this week. Every day you delay costs you.
If you’re still uncertain: Give yourself one more week to observe, then decide. But not longer. Indecision is expensive.
You didn’t make a bad hire because you’re a bad founder. You made a bad hire because hiring is hard and most hiring processes don’t test for the things that actually matter.
The good news? You can fix the process and hire better next time.
READY TO HIRE BETTER?
If you’re recovering from a bad hire and want to make sure the next one works out, let’s talk about how to hire for chemistry, not just credentials.
I’ve helped 400+ founders navigate exactly this situation – recovering from bad hires and building processes that test for fit before you invest £12K and 3 months.
Inside, you’ll get:
- Chemistry fit assessment (test for working style before you hire)
- Interview question bank (questions that reveal culture fit and working style)
- 30-day performance plan template (if you decide to try to fix it)
- Red flag checklist (spot problems in week 2, not week 12)
Let’s talk about your situation – whether to fix or fire, and how to hire better next time.
No pressure. No sales pitch. Just honest advice from someone who’s seen this 400 times.


