Hiring for the Gap Not the CV

Article 4 of 12 — Building Design Teams

There is a particular kind of CV that arrives once or twice a year and ruins your judgement for the rest of the afternoon. Their education is immaculate. Their portfolio is the sort of thing that makes you quietly close your own portfolio in a different tab. Every position they have held is a place you’d kill to have worked, or a problem you’d kill to have solved and (worst of all) a logo you recognise. You finish reading it and the only coherent thought in your head is: yes, obviously, hire this person, what are we even discussing here?

That feeling is the single most reliable way I know to miss the best hire.

Not because the person is bad. Usually the opposite because they’re confident and technically excellent, and that’s the whole problem. The danger is that “excellent” is doing all the work in your head, and you’ve quietly stopped asking the only question that actually matters, which is: excellent at what we already have too much of, or excellent at the thing we’re missing?

A team is a shape with a hole in it

Back in the first piece in this run, I made the case that you grow a team, you don’t assemble one. That treating hiring as a series of individual acquisitions gets you a list of people, not a team. Hiring for the gap is where that idea stops being a nice sentiment and starts costing you actual decisions.

Here’s the thing about a team that’s been running for a while: it has a shape. It’s brilliant at certain things and curiously often, consistently terrible at others. That part is rarely random. It’s the silhouette of who’s already there. Take a team of confident, fast, opinionated designers who will ship beautiful work at speed yet will also constantly talk all over the one quiet opposing person in the room and never once stop to check whether the thing they’re shipping so beautifully is the right thing at all.

That team does not need another confident, fast, opinionated designer. It is drowning in those. It needs the person who slows the room down and asks the unfashionable question. But that person, on paper, often does not out-dazzle the confident others. Their CV is quieter. Their portfolio has fewer fireworks and more “here’s the disaster we avoided,” which is the hardest kind of work to put in a portfolio because by definition nothing visible happened.

So you hire another firework, because fireworks interview much better, but the result is that your team gets even faster at being wrong.

The gap is usually not a skill

When people first hear “hire for the gap,” they reach for the skills matrix. That spreadsheet with names down the side and competencies along the top, hunting for the empty cells. There’s nothing against motion design. Right, hire a motion designer. Fair enough, sometimes the gap really is that legible, and a spreadsheet will find it.

The gaps that actually hurt are rarely on the spreadsheet, because they aren’t hard skills. They’re temperaments, behaviours, perspectives, or simply just ways of seeing.

In the enterprise design teams I have led, our worst stretch always comes when we are, on paper, at our strongest. Every seat has been filled, every skill has been covered, and everyone is genuinely good. Yet we would still ship things that were elegant but wrong because we were solving the problem cleanly without ever checking that it was the actual problem worth solving.

No cell on any skills matrix was empty. The gap in the team was a person who instinctively distrusted a brief, who’d been close enough to a real user’s frustration that “the requirements say so” made them twitch. That reflex wasn’t anywhere in the room. A group of people who could answer any question beautifully and backed up with heuristics, but nobody whose first move was to ask whether it was the right question.

You cannot put “twitches at a bad brief” in a job posting. Yet it was the most expensive thing we were missing.

Find the gap by looking at the failures, not the people

The trap is to figure out your gap by listing what your team is good at and inverting it. That gives you a tidy list and the wrong answer, because teams are good at things in flattering ways and bad at things in embarrassing ways, and the embarrassing ways are almost always where the gap lives.

So stop asking “what are we good at?” and start asking “what do we get wrong in the same way every single time?” Not the one-off disasters because those are just part of life, but the patterned ones. The mistake the team makes so consistently that everyone’s learned to shrug at it like the weather (although in the UK that might not be the best analogy!).

In one team I led, the pattern only became clear once I said it out loud: the team was over-engineering every time. Give us a small building to design and we’d return a cathedral. That wasn’t a skills gap, it was a missing instinct toward restraint. Once it was named, I knew exactly who I was hiring for. Not the most technically impressive designer in the CV pile. The one whose work was conspicuously, almost suspiciously, simple.

The consistent failure is the negative space. So hire into the negative space!

This is harder than it sounds, and not for the reason you think

The difficulty isn’t spotting the gap. The difficulty is that hiring for it means, fairly often, choosing the candidate who is less immediately impressive than someone else in the pile — and then defending that choice to a hiring panel who all read the same dazzling CV you did and arrived at the same afternoon-ruining conclusion.

You will sit in a debrief and watch a genuinely excellent candidate get five enthusiastic yeses, and you’ll be the one going “I know, I know, but I think we should pass on this one.” That is an uncomfortable sentence to say out loud. It sounds like you’re being difficult, or have impossibly high standards, or you secretly didn’t like them for a less acceptable reason. What you’re actually doing is your job: holding the shape of the team in your head while everyone else is holding a single brilliant CV.

One guardrail, because this idea is easy to abuse: hiring for the gap is not a licence to hire someone mediocre and call it diversity of thinking. The gap still has to be filled by someone genuinely good. You’re not lowering the bar, but you’re moving it sideways. You’re saying that ‘ good’, for this seat, means something different from what it meant last time, and that the quiet candidate who fills the gaping hole is, for this team, the stronger hire than the loud one who’d have made the hole deeper. If you ever find yourself using “fills a gap” to wave through someone you have private doubts about, you’ve stopped hiring for the gap and started hiring for the excuse.

What you’re actually building

The shift, in the end, is from ‘collecting people’ to ‘completing something’. A great hire doesn’t have to be the most impressive person who applied. That is a huge factor, don’t get me wrong, but it’s the person who makes the people you already have be better. This is achieved by being unlike them in exactly the way the team really needs.

This is a far less flattering way to hire, of that there’s no doubt. There’s no thrill quite like landing the candidate with the spectacular CV, and the gap-hire won’t give you that hit unless you have the team shape in mind. The reward comes three months later, when you notice the team’s predictable old failure mode has quietly stopped happening, and you realise it stopped happening the week that one new person started.

Next up: you’ve hired for the gap. Now you have to fold the person in. Without the team’s immune system rejecting them, and without them quietly reshaping themselves to match everyone else and filling no gap at all. That’s the first 90 days, and it’s a team event, not an HR checklist.

Originally published at https://tijamo.substack.com.