One of the biggest shifts in how I recruit has been learning to look at the whole story. Not just the outcome. Not just the metric. Not just whether we filled the role.
If a hiring partner says yes, that's information. If they say no, that's information. If a candidate applies five times, that's information. If five thousand people apply, that's information. If nobody applies, that's information. If candidates consistently move through one part of an interview process and then suddenly fall off at the next stage, that's definitely information.
The question isn't whether the information exists. The question is:
The number isn't the story.
I've become much more interested in data over the course of my career. Funnel health. Conversion. Historical performance. Market analysis. Where candidates enter. Where they advance. Where they don't. That information can tell you a lot. But I've also learned that looking at a number and understanding a number are two different things.
Say there's a drop in conversion between two stages. Okay. I know where something is happening. I don't necessarily know why. Now I want to go underneath it.
What are we learning in the feedback? Are the declines saying similar things? Is there a recurring gap? Did something change? Is the market telling us something different from what we expected? Are we actually evaluating what we said we were evaluating? Is the problem at this stage, or did something upstream create the problem we're seeing here?
That's when data becomes useful to me. Not as a verdict. As an invitation to investigate.
Sometimes the stated problem isn't the problem.
This is probably one of my favorite parts of recruiting. Give me a struggling search and let me figure out what's happening. I love a puzzle. But I don't want to start solving before I understand what I'm solving.
If someone tells me, “We're not seeing enough candidates,” there are a lot of places I could immediately go. We need more sourcing. We need more outreach. We need more applicants. Maybe.
But what if plenty of people are entering the process and we're losing them somewhere else? What if the profiles exist, but our expectations don't match the market? What if we're attracting the right people and evaluating them against the wrong thing? What if we're calling something a top-of-funnel problem because that's easier to see than the problem underneath it? I don't want to spend weeks solving the symptom and then act surprised when it comes back.
So I start turning things over. What do we know? What don't we know? What has already happened? What patterns keep showing up? Where does the evidence agree? Where does it get weird? You keep going until the story starts making sense.
And sometimes the most useful thing you learn is that the hypothesis you walked in with wasn't right. That's useful, too.
A “no” is not empty.
I think recruiting can become so focused on getting to yes that we underestimate how much we can learn from no. A candidate doesn't advance. Why? A hiring partner isn't excited. Why? Someone declines an offer. Why? Candidates keep disappearing at the same point. Why?
The goal isn't to interrogate every individual decision until it becomes something we wanted instead. Sometimes no is simply no. But over time, those decisions leave information behind. And if enough of them start pointing in the same direction, I want to understand what they're pointing at.
Because the absence of a hire doesn't mean the work produced nothing. A search can teach you about the market. It can teach you about your expectations. It can expose a calibration problem. It can tell you that the profile you've described doesn't exist in the abundance you assumed it did. It can tell you that candidates understand your opportunity differently than you do. It can tell you where your process is creating friction.
Sometimes what looks like failure is actually the first useful signal you've gotten. If you're willing to look at it.
This is also why I don't believe data should replace judgment.
There are things a funnel can tell me that my instincts cannot. If I want to understand historical performance across a search, I don't need a vibe. I need the data. If I want to know where conversion is changing, I need the data. If I want to compare what we thought would happen with what actually happened, I need the data.
But there are also moments when I'm talking to someone and something shifts. They're hesitating. Their excitement sounds different. They're asking questions differently. They're suddenly harder to reach. Something feels unresolved. A dashboard can't have that conversation for me. I can. So I ask.
I'm picking up on a little hesitation. Is there something I can help clarify? Is there something you're still unsure about? What information would help you feel more confident in your decision?
Because people make decisions based on the information available to them. And sometimes the only way to uncover what's missing is to talk to them. The human signal doesn't cancel the data. The data doesn't cancel the human signal.
My job is to know when I need which one.
Metrics deserve context, too.
This is where I think organizations have to be careful. We love clean numbers. Time to fill. Time in stage. Conversion. Acceptance. Pipeline health. All useful. But recruiting happens inside systems, and systems are messy.
A number can describe what happened without accurately describing who caused it, what influenced it, or what should change because of it. That's especially important when we start using metrics to evaluate people. If the data is going to carry that much authority, we need to understand how the data was created.
What does the system count? What doesn't it count? What context disappears when the information becomes a number? What variables contributed to it? Otherwise, we risk treating measurement as understanding. They aren't the same thing.
The work is in the interpretation.
I don't think the future of recruiting is recruiters staring at increasingly elaborate dashboards. I also don't think it's ignoring data because recruiting is a “people business.” It's both.
It's being able to look at the evidence and understand the human behavior inside it. It's knowing when to zoom out and look for the pattern and when to zoom all the way in and have a conversation. It's being willing to discover that the thing you thought was broken isn't broken at all. It's resisting the urge to make the evidence support the story you've already decided to tell.
And it's understanding that sometimes the most important information isn't the answer. It's the thing that makes you ask a better question.
That's why I've stopped thinking about recruiting data as something I check after the work happens. The work is producing information all the time. Yeses. Nos. Movement. Stalls. Interest. Silence. Patterns. Exceptions. All of it is telling us something.