18.11.2026

Why Great Hires Fail in the Wrong Operating Model

Why Great Hires Fail in the Wrong Operating Model

Every recruiter has seen this one. The search goes well, the shortlist is strong, the offer is accepted. Then somewhere inside a year, the new hire is frustrated, the team is disappointed and we’re back at the start.

The usual verdict is “not the right fit”, and sometimes that’s true. More often the person was right and the place wasn’t.

A job description describes a role, not a system.

The brief for a senior Legal, Data, Cyber Security or Finance hire covers what you’d expect, things like experience, technical depth, leadership style, and salary for example. What it rarely covers however is where the person is landing. How does work reach them? Who decides what gets prioritised? Which systems do they inherit, and do those match how the team really works? Which other departments do they depend on, and do those departments know?

Those are operating model questions, and they tend to go unasked until the hire is already struggling.

What a new senior hire inherits.

I’d boil it down to four things. Any one of them can sink a good appointment on its own.

Ownership comes first. Who owns data quality? Who owns contract approvals? Who decides when a security alert becomes an incident? If the honest answer is “it depends”, the new hire spends their first year negotiating territory when they should be delivering.

Then there’s how work arrives, which is usually less orderly than anyone admits. Does it arrive via email, chat, a word in the corridor, or in a Teams/Slack message? A General Counsel who joins a business where every contract request lands in a personal inbox isn’t running a legal function yet. They’re running a queue, and no GC wants to feel like they’re answering tickets.

Tooling is the third. Plenty of businesses have bought a governance, analytics or security platform that never quite got adopted. The new Head of Data or GRC inherits the licence, the bill, and an expectation that it should already be paying off.

Last, measurement. If nobody agreed what good looks like, a new leader can work flat out for months and still struggle to show progress. The business gets twitchy, the hire feels unsupported, and neither says so until it’s late.

None of this is the new hire’s fault, and you won’t hear about any of it in an interview.

It looks different in every function.

A new Head of Legal finds no standard intake route, three versions of the same template and approvals that depend on who’s free. A Head of Data starts in a business where each team defines the same metric differently and nobody owns the quality of the underlying data. A CISO inherits tools that work well on their own, and handoffs between security, IT and engineering that nobody has ever rehearsed. A Finance Director takes over a month-end close that depends on two or three people and the spreadsheets only they understand.

These are capable people being asked to deliver through a system nobody designed with them in mind.

Hire first or fix first?

I’m not suggesting anyone pauses hiring until the house is in order. That isn’t realistic, and often the new leader is exactly who you need to sort it out. It’s completely normal to build the path brick by brick as you go along.

The difference that matters is between hiring someone to fix a problem you’ve named and hiring someone who doesn’t know there’s a problem. The first has a mandate, backing and a realistic timeline. The second finds out the hard way, and in my experience blames themselves first.

This is always worth asking yourself before the search starts:

Where does this person’s work come from, and how does it reach them? Who owns the processes they’ll depend on, and do those people know about the hire? What will they inherit that isn’t working? Have we told them? What does success look like at six months, and how would we know? Are we hiring them to run a good system or to fix a broken one? Have we said which?

Are they hard to answer? That’s useful. It doesn’t make the hire wrong. It makes the brief incomplete.

Say what’s broken.

The searches that go best tend to involve a client who’s upfront. Knowing what works, what doesn’t, and why you need someone senior is refreshing. Strong candidates respect that, partly because they’ve usually seen the alternative. It also lets them plan a proper first 90 days rather than finding out on day 30 what they’ve walked into.

Candour costs a little discomfort. A failed hire costs fees, time, morale and whatever the role was meant to unlock.

Fix the system, then back the person.

Last month, I wrote about asking whether a process should exist before you automate it. Hiring is the same. Before you add a capable person to an operation, check the operation can actually use them.

Get that wrong and you’ll be writing the brief again in a year.

Latest Blogs

View all blogs