Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / Why Hiring for Culture Add Beats Culture Fit
Transcript
- Lucas: You've heard it a thousand times — 'we need someone who's a great culture fit.' And it sounds harmless, even smart. But I think that phrase has quietly cost companies more than almost any other hiring mistake. Luna: I've definitely been guilty of saying it. It feels like shorthand for 'will they get along with the team?' But I'm guessing you're about to tell me it's actually a trap. Lucas: Exactly. The problem is that 'culture fit' so often translates to 'hires people who think, look, and act like the existing team.' It's a bias magnet. And it actively suppresses the very diversity — of thought, experience, background — that drives innovation. Luna: So what's the alternative? I've heard 'culture add' thrown around. Is that just a rebrand, or is there real substance behind it? Lucas: Real substance. Culture add means you're actively looking for what a candidate brings that your team currently lacks — a perspective, a skill set, a way of working that fills a gap. It's not about rejecting fit entirely, but about making it one factor among many, and not the dominant one. Luna: I want a concrete example. When has this actually worked? Lucas: Let me tell you about a mid-stage SaaS company — about 200 employees — that was struggling with product innovation. Their engineering team was brilliant but homogenous: all CS grads from the same three universities, all early-career, all men. Their hiring process was built on culture fit: they'd ask 'would I want to grab a beer with this person?' Luna: Classic red flag. Lucas: Right. So the CPO decided to experiment. She had an opening for a product manager. Instead of the usual pipeline, she specifically sourced a candidate with a completely different background: a former middle school teacher who had transitioned into instructional design and then into project management. Luna: No CS degree, no startup pedigree. I can already picture the culture-fit panel rejecting her. Lucas: Exactly what happened. In the first round, the hiring manager said 'she's great but doesn't fit.' The CPO pushed back. She asked the team to evaluate her on three criteria: does she have the raw ability to learn the domain? Does she bring a perspective we don't have? And would her addition make us better at solving problems, not just more comfortable? Luna: So they redesigned the interview on the fly. Lucas: More or less. They gave her a case study about a feature rollout, and she approached it completely differently. She focused on user education and onboarding friction — because that's what she knew from teaching. The engineers had never thought about that angle. She got the offer. Within six months, she had revamped their onboarding flow and reduced churn by 12 percent. Luna: So the 'add' was literally a skill and perspective they were missing. That's a tangible result. Lucas: And it goes both ways. I've seen teams that are all senior generalists hire a junior specialist — someone who's deeply technical but maybe not as polished in meetings. The culture-fit lens would have filtered them out. But as a culture add, they brought depth the team didn't have. Luna: What about the flip side? Can culture add go wrong? Like, you hire someone so different they can't integrate? Lucas: Absolutely. The nuance is that you still need baseline alignment on values — integrity, collaboration, whatever's core to how work gets done. But you can have that and still hire for difference. The mistake is treating culture fit as a binary: either they fit or they don't. Culture add is a spectrum. Luna: So how do you operationalize this? If I'm a hiring manager listening, what do I actually do differently next week? Lucas: Start with the job description. Write down what your team currently excels at, and what you collectively lack. Be honest. Maybe you have great execution but weak strategic thinking. Maybe you're all introverts and need someone who can run client workshops. That's your add profile. Luna: Then you rewrite the interview questions accordingly. Lucas: Yes. Instead of 'tell me about a time you worked in a team' — which everyone rehearses — ask 'what's a perspective you've brought to a team that was initially resisted, and how did you handle that?' That directly tests for add. Luna: And you train your interviewers to recognize their own bias. I've seen panels where everyone nods along with a candidate who mirrors their own background, then gives a lukewarm review to someone different. Lucas: That's where a structured scorecard helps. Score for specific add criteria: domain expertise gap, cognitive diversity, unique experience. Not just 'likability.' Luna: I've also seen companies use a 'culture add canvas' — a one-page template that maps the team's current strengths and gaps, then maps the candidate's profile against that. It's visual and forces concrete comparison. Lucas: That's smart. And on the onboarding side, you need to support the culture-add hire. They're the one who's different. If you just throw them in and expect them to adapt, you're setting them up to fail. Luna: So what does good onboarding look like for someone hired for add? Lucas: Pair them with a buddy who's explicitly not a clone. Have a 30-60-90 day plan that leverages their unique skills early — so they feel valuable for their difference, not pressured to conform. And create a feedback loop where the team learns from them, not just the other way around. Luna: That last point is key. The team has to be open to being changed by the new person. Otherwise you're just tokenizing. Lucas: Exactly. And you know, this whole conversation reminds me that quality content like this — practical, evidence-based — is only possible because of listeners who support the show. If you find these episodes useful for your work, you can help keep it ad-free and independent. Luna: Yeah. We don't do sponsors, we don't do ads. It's just us and our research. So if you've ever learned something here that helped you make a better hiring decision, consider tossing a few dollars our way. Lucas: It's simple: buy me a coffee dot com slash fexingo. That's all lowercase. And it genuinely makes a difference — helps us invest more time into each episode. Luna: Alright, back to culture add. One more practical tip: after you hire for add, measure it. Track whether the new hire's unique perspective actually led to new product ideas, process changes, or revenue. That's the proof. Lucas: Exactly. And I'd add: do a six-month review not just of the hire's performance, but of the team's evolution. Did the team become more adaptable? Did they adopt any of the new hire's methods? That's the ROI of culture add. Luna: So final takeaway: stop hiring for comfort. Start hiring for what you're missing. Lucas: And if you're the candidate in a culture-fit interview, you can flip the script. Ask them directly: 'what's a perspective your team currently lacks, and how would you support someone who brings it?' If they can't answer, maybe that's a sign. Luna: I love that. It turns the interview into a two-way evaluation. Lucas: Alright, that's our episode. Until next time, hire for what's missing, not for what's familiar. Luna: See you next time.