Hiring Isn't an Event, It's a System

The candidate stood in the middle of the production hall for perhaps four minutes before I understood we had a problem, and it had nothing whatsoever to do with their spreadsheets. On paper this was, without exaggeration, the best BI analyst candidate we had seen in two years, fluent in DAX, faster with a pivot table than half my existing team, able to explain a regression model to a shop floor supervisor without once reaching for jargon. They had sailed through the interview, charmed the panel, and produced one of the cleanest pieces of analytical reasoning I had read from any candidate that year. And then I walked them onto the factory floor, past the forklifts and the packing line and the particular clattering roar a real production environment makes when it is running at full tilt, and I watched something close, quietly, behind their eyes. They lasted the tour. They did not last the role.

I had not tested for this, because it had never occurred to me that it needed testing. We ask candidates about resilience and comfort with ambiguity as though these are qualities that live in the abstract, portable from one context to another like an attachment on a CV. They are not. Resilience in a quiet open-plan office and resilience four feet from a conveyor belt are, it turns out, different muscles entirely, and no amount of asking someone to describe a time they handled pressure will tell you which one they actually have. That hire, and the awkward, mutually agreed parting that followed it within a fortnight, is the reason the whole process now starts on the factory floor rather than saving it for later. It is also the clearest evidence I have that hiring is not an event you run once and then forget about. It is a system, and like any system, it only improves by being wrong in specific, memorable ways and then being redesigned around the wrongness.

What a CV Cannot Tell You

The single most important thing I am hiring for rarely appears on the document in front of me. Skills can be taught, more easily than most people admit, and technical gaps close given time and a reasonable manager. What is much harder to repair, and considerably more expensive when you get it wrong, is whether someone's values sit comfortably alongside how your team actually works, day to day, under pressure, when nobody senior happens to be in the room.

Patrick Lencioni's framework in The Ideal Team Player gives this some welcome shape. The ideal team player, he argues, is humble, hungry and smart, where smart has nothing to do with intellect and everything to do with people, an instinctive read on how one's own behaviour lands on others. I have found this holds up rather better than most management frameworks survive contact with reality, which is to say it mostly does, and where it does not, the gap has generally been mine, not Lencioni's.

The trouble, of course, is that nobody will tell you honestly whether they are humble, hungry and smart if you simply ask them, including the people who genuinely are. Humility rarely announces itself, and the people least equipped to self-report on it are, almost by definition, the ones who need the question the least. So I have stopped asking it directly, and started asking about something else altogether.

Long before any formal question about stakeholder management gets near a candidate, I ask what they do outside work, why they chose the path they chose, where they have lived and what it was actually like living there. None of this is small talk dressed up as process. It is the mechanism. People reveal their real values far more honestly describing their own life than performing competency answers they suspect you have heard forty times already this month, and a surprising amount of an interview's real work happens in the ten minutes that look, on the surface, like pleasantries.

Someone who has lived and worked somewhere genuinely unfamiliar has already demonstrated something an interview question cannot fake: they chose difficulty once, deliberately, and adapted to it. That is a data point no amount of competency-based interviewing replicates. It cuts the other way too. I have ended interviews early because this same conversation surfaced a view I was not prepared to build a working relationship around, and I no longer feel any need to apologise for that. Cultural fit is not only a positive filter, hunting for reasons to say yes; occasionally it exists specifically to say no, and on those days it is doing exactly its job.

Before any of this was formal, I ran personality and cognitive aptitude testing with my existing team, voluntarily, results shared or kept private entirely as people chose. I did this slowly and deliberately, because asking someone to hand over something as personal as an IQ score and a personality profile requires a foundation of trust that has to exist before the data does, not after. A team I had worked alongside for years was willing. A team in its first week would, quite reasonably, have treated the request as faintly sinister.

What came back was more interesting than I expected going in. Our project managers scored consistently traditional on openness, conventional, structured, allergic to ambiguity in the nicest possible way. Our analysts scored close to the opposite, experimental, curious, entirely at home not knowing the answer yet. Neither profile is superior to the other, but the pattern was striking enough to become a soft filter, a cue for which questions to lean into at interview rather than a verdict on anyone. When someone wanted to move from analysis into project management, the profile gave us something concrete to explore together, rather than something to guess at.

My own results, when I finally worked up the nerve to look at them properly, were not what I expected. I scored high on competitiveness and drive, which felt entirely fair and not remotely flattering. I scored considerably lower on self-confidence than I would ever have predicted, and looking back, I think the test had simply caught me honestly, driven to do more, long before I had earned the confidence that experience eventually supplies. It did not show me what I expected to see. It showed me something true, which is a much higher bar for a piece of workplace psychometrics to clear, and the only real justification I have found for using them at all.

Building a Process That Goes Looking for the Truth

The factory tour, for the reasons already given, comes first now, ahead of anything resembling a formal interview room. It gets a candidate out of the performance of being interviewed and into the actual environment they would be working alongside, and it buys a few unguarded minutes to build some rapport and take the edge off before we sit down properly, because an interview, whatever its reputation, runs in both directions. They are deciding whether we deserve them roughly as much as we are deciding the reverse. I bring other members of the team along too, partly for a second, differently angled view of the candidate, and partly because if this person joins us, I want the team to have shaped that decision before it happens, so it lands as something they helped build rather than something announced to them.

The assessment task itself is where the honest information tends to arrive. Solutions analyst candidates receive a deliberately vague requirements brief, stakeholders unnamed, working hours unspecified, the system they would be integrating with left conveniently undescribed, and I care less about the answer a candidate produces than about how they went about finding it. A business analyst I hired some years ago produced, on paper, some of the tidiest documentation I had seen from a candidate, and then, in the room, proved unable to draw information out of a group or sit comfortably inside a genuinely uncertain conversation. Talented, in the narrowest sense of the word, and simply the wrong shape for what the role demanded, a mismatch we both recognised soon enough to part ways without much drama. The candidates worth hiring name what they do not know, make a reasonable assumption anyway, and then defend that assumption exactly as hard as it deserves to be defended and no harder, adjusting the moment you push back on it with something real.

For BI analyst roles, the brief is looser again: here is some data, find something in it, use whatever method you like. What comes back tells you an extraordinary amount for so short a prompt. The best responses tend to arrive in one of two entirely different costumes, an elaborate presentation pulling in outside data and naming its own gaps honestly, or a quiet, immaculately built spreadsheet with formulas that do not need defending because they were built to survive scrutiny in the first place. Both are excellent, and I have learned to stop assuming the quieter one is the lesser piece of work. One analyst who joined us this way had solid SQL, tidy spreadsheets, and a genuine appetite to learn our reporting tool, and still, over time, the mismatch became unmistakable. They wanted, not unreasonably, to be handed a question and return with an answer, and our work was never that tidy, the question itself usually being half of what needed working out. No amount of coaching closed that gap, because coaching was never going to reach it; the mismatch sat somewhere skills training doesn't go. They found a role elsewhere that fit properly, which I choose to count as the system working rather than failing.

I never read the written work before meeting the candidate in person, deliberately, because the bias that arrives from reading someone's output before you have met them is entirely real and entirely avoidable, and declining to do so remains one of the cheapest improvements I have made to the whole process. For developer roles, oddly, the task itself adds less than you would hope. A set of structured questions walking through real decisions on real projects, what broke, what they would do differently, gets you further than any exercise does. People talk their way to the truth faster than they can perform it on a whiteboard.

The Bar You Cannot See Moving

Reed Hastings and Erin Meyer, in No Rules Rules, call the resulting effect talent density, the observation that as the quality of the people around you rises, the informal standard rises quietly alongside it, unannounced, until the team itself becomes the clearest signal you have for who fits next. I have watched this happen in something closer to slow motion than theory. A BI analyst joined and simply changed, by example rather than instruction, what good data presentation looked like across the whole team. Developers arrived and brought better testing habits with them, which spread the way habits do, sideways rather than downwards. Project managers introduced cleaner communication without ever holding a workshop about it. Nobody was told to raise their standard. They simply watched someone else's and adjusted.

There is a second effect that is easy to miss entirely. Bringing in people who genuinely own certain kinds of work frees the people already there to go and do harder work on problems that actually deserve their attention, rather than quietly absorbing everything that lands on the team regardless of fit. The whole team lifts, not because anyone announced a lift, but because the ceiling moved and nobody had to ask permission to reach for it.

This is the friendlier version of the spiral I wrote about in Breaking the Spiral, where dysfunction feeds itself, driving out good people and worsening the culture that drove them out in the first place. The reverse turns out to be just as self-sustaining. A hiring system, designed with enough honesty about where it has previously gone wrong, makes each subsequent hire slightly easier to get right, and the signal only gets clearer from there.

Coming Back to the Noise

I still think about that factory floor, and about a candidate who had answered every question put to them with more composure than most people manage on their best day, undone entirely by a noise nobody had thought to mention beforehand. It would be tidy to close here with something about gardens or soil, the sort of image that fits equally well onto any post about any team anywhere, and I have deliberately resisted reaching for it, because the truth is plainer and rather less pastoral than that. Hiring well is not a system for finding perfect people. It never was. It is a system for finding out, before it costs you six months and a difficult conversation, exactly which room a person can actually stand to be in.

Every hire either widens the room your team can work in, or quietly narrows it, whether or not anyone notices at the time. I would rather find that out on a factory floor, standing next to the person concerned, than three months into a job neither of us can comfortably walk back from. Where would you rather find out?

Sources:

• The Ideal Team Player: How to Recognize and Cultivate the Three Essential Virtues by Patrick Lencioni (Jossey-Bass, 2016)
• No Rules Rules: Netflix and the Culture of Reinvention by Reed Hastings and Erin Meyer (Penguin, 2020)