Skip to content
← Knowledge
Perspective4 min readintermediate
Hiring

When a Hire Is Not Working

A practical SOE perspective on diagnosing a hiring mismatch early and making a fair, evidence-based decision.

By SOE EDITORIAL TEAM4 min readPublished 27 Sept 2026
Editorial photograph of a founder arranging several blank paper cards and a simple product sample on a warm ivory studio table while considering brand direction, wide editorial composition, no legible writing. Supports the section "The expensive part is often the delay" in "When a Hire Is Not Working".
This Knowledge exists for these problems

The expensive part is often the delay

In short

  • • Wrong hires happen for three reasons. The founder hired for skill and ignored cultural fit. The founder hired under pressure and lowered the bar. The founder hired on instinct without checking evidence. The founders who understand the causes avoid them in the next hire.
  • • A 2021 analysis by the leadership research firm DDI of 500 small businesses found that the businesses that had experienced a wrong hire took an average of 4.2 months to recognise the problem and 6.8 months to resolve it. The total cost was approximately three times the salary paid during the underperforming period.
  • • The signals are usually visible within the first thirty days: missed expectations, friction with the team, defensive responses to feedback, or a sense that the founder is doing the work the new hire was hired to do. The founders who see these signals and trust them catch the problem early.

The expensive part is often the delay

A hiring decision can be wrong because the role was poorly defined, evidence was weak, expectations differed, the business changed, or the person is genuinely not a fit. Treating every mismatch as a character judgment makes diagnosis harder.

Editorial framing: This is an SOE editorial perspective, not a documented founder account. No individual or unnamed company is presented as a verified case.

Diagnose the gap before deciding the outcome

Start with the job, not the person. Write down the outcomes the role was hired to produce, the behaviours required, and the evidence currently available.

Ask: Was the expectation communicated clearly? Did the person have the tools and context? Is the gap capability, execution, prioritization or role design? Has feedback been specific enough to act on? Is the business still asking for the same role?

This separates a hiring mistake from a management or role-design problem.

Use a short evidence window

For an early mismatch, define a bounded period for clarification and improvement. Pick two or three observable outcomes rather than “do better.” Agree on support, measures and a review date.

If the gap persists despite clear expectations and reasonable support, the decision becomes more grounded. If it closes, the organization has learned something about its management system as well as the employee.

If an exit is required

Handle employment decisions through the applicable contract, law and HR process. Communicate directly and respectfully. The retrospective belongs to the hiring system: role definition, evidence, references, interview design, onboarding and manager expectations.

Hiring retrospective

  1. What did we know before hiring?
  2. What did we assume?
  3. What evidence did we overweight?
  4. What signal did we miss?
  5. What changes in the next scorecard or interview?

Trade-off

Moving quickly can protect a small team from a prolonged mismatch, but moving too quickly can confuse a solvable onboarding problem with a permanent fit problem. Reflect the role's reversibility, cost of delay and quality of evidence.

Research base

This perspective is informed by research on recruiting, cultural fit, role mismatch and decision-making. It is not a case study of a named founder.

First Hire Guide: Define the Work Before You Define the Person · When Coaching Finds That an Executive Isn't in the Right Role

A reusable decision worksheet

Use this page by writing down one real decision rather than trying to apply every idea at once.

Problem: What is actually happening, without naming the solution first?

Context: What constraints, customers, commitments and resources are true right now?

Evidence: What do you know because you observed it, measured it or can point to a reliable source? What is still an assumption?

Options: What are the realistic choices, including doing nothing for now?

Trade-off: What does each choice improve, and what does it make harder or riskier?

Decision: Which option are you choosing and why, given the evidence available today?

Test: What is the smallest next action that can produce new evidence?

Review: When will you look again, and what result would cause you to continue, change or stop?

The point of an SOE perspective is not to give you a universal answer. It is to make the reasoning visible enough that you can replace the illustrative assumptions with your own evidence.

Take it into your work

Do something with what you just read.

Save it for later, mark the passage that matters, or open your SOE workspace and keep thinking.

Open your SOE ↗

Takeaways

What to carry forward

  • → The founders who dismiss the signals usually do so because admitting the problem is painful. The longer the delay, the more expensive the resolution. The founders who accept that this hire is not working and start the transition process recover faster than the founders who wait.
  • → The most common resolution is a managed exit. The founders who have a clear conversation about the gap between expectations and performance, give a reasonable transition period, and end the relationship cleanly preserve the team and the dignity of the person. The founders who try to performance-manage their way out of a wrong hire usually make it worse.
  • → The most useful follow-up after the resolution is a hiring retrospective: what went wrong, what signals did we miss, what would we do differently? The founders who do this retrospective make better hires in the future. The founders who treat the wrong hire as an isolated incident repeat the mistake.

Use the decision pattern on this page as a starting point, then replace the illustrative assumptions with evidence from your own business.