Why HR and Ops Keep Disagreeing on Hires, and the One-Page Fix

In short: HR and operations disagree about candidates because they judge them against different pictures of the job. HR looks at the résumé. Ops pictures a Tuesday afternoon when everything is on fire. The fix is a one-page scorecard that both teams write before the first interview. It sets out what the person must deliver in 90 days, the situations they will face, and the evidence that counts. When both sides score the same things, the arguments happen before the search, which is where they're cheap.

Two people, two blueprints

Picture a renovation where the architect and the site foreman were handed different drawings. Both are good at their jobs. Both are confident. And every conversation turns into an argument about a wall that only one of them thinks should exist.

That's most of the hiring debriefs I've sat in. HR brings a candidate with the right degree, the right titles and clean references. Ops meets the same person and says no inside four minutes, often without being able to explain why in words that sound fair. HR hears bias. Ops hears box-ticking. The role stays open another three weeks.

Neither side is wrong. They're working from drawings nobody put side by side.

What each side is actually protecting

HR is protecting the company from risks it can see: unexplained gaps, claims nobody can verify, pay that's out of band, and a process that won't hold up if someone challenges it. That's real work, and it matters even more when you're hiring across borders.

Operations is protecting throughput. The ops lead knows the role isn't really "Accounts Payable Specialist." It's the person who has to reconcile 400 invoices when the ERP export breaks on the 28th and the controller is on leave. A résumé can't tell you how someone behaves in that moment, so Ops falls back on gut feel, and gut feel doesn't survive an HR review.

The fix: one page, written before the search starts

The most useful change I've seen is a shared scorecard, agreed before anyone reads a CV. It isn't a job description. Job descriptions are marketing documents. A scorecard is a promise about what "good" looks like.

It fits on one page and has four parts:

• The 90-day outcome. One or two sentences on what this person will have delivered by the end of month three. "Month-end close for both US entities runs without the controller touching it" belongs on a scorecard. "Strong attention to detail" doesn't.
• Three real scenarios. Pulled from the last quarter of actual work: the broken export, the client who emails at 11 p.m., the handoff that got dropped.
• Must-haves versus trainables. Most roles have two or three genuine must-haves. Everything else can be taught in the first month, and pretending otherwise shrinks your candidate pool for no reason.
• What counts as evidence. For each item, agree what you'd need to see or hear in an interview to score it. This is where HR's rigour and Ops' instinct finally meet.

Turn the scenarios into the interview

Once the scorecard exists, the interview almost writes itself. Instead of "tell me about a time you showed initiative," you say: "Here's an export from our system with three errors in it. Walk me through what you'd check first." Ops gets to see real behaviour. HR gets a consistent, defensible question asked of every candidate. Everyone scores against the same page.

For offshore and remote roles this matters twice over. You don't get the corridor chat or the lunch that tells you how someone thinks. The scenario has to do that job, so make it specific to how your team works, including the time zone the new hire will work in.

Where the argument should happen

A scorecard won't end disagreement. It moves it. The argument about whether the role needs a CPA, or whether the person must overlap four hours with Toronto, takes one 45-minute meeting before the search starts. Without a scorecard, it gets fought out across six debriefs afterwards. The early meeting is a far cheaper place to argue.

We insist on this step before we run any search for a client, whether it's through our recruitment process outsourcing practice or for a dedicated offshore team. If we can't write the scorecard together, we're not ready to hire, and neither is the client.

A quick test for your next open role

Ask your HR lead and your ops lead, separately, to write down what the new hire must have achieved after 90 days. Compare the answers. If they match, you're in good shape. If they don't, you've just found out why your last three finalists were turned down.