Skip to main content

The downside of hiring for cultural fit

For years, hiring for cultural fit has been a cornerstone of my recruitment strategy. The idea is simple: more than focusing only on skills, I focused on finding people who aligned with our company's values, norms, and practices to create a harmonious and productive work environment. This also means that I put a lot of focus on building a strong culture inside my team.

Cultural fit

However, when listening to Malcolm Gladwell and Adam Grant on the Work Life podcast, I had to re-think this approach as it highlighted the potential downsides of overemphasizing cultural fit.

In the podcast Adam says that startups where founders put culture fit first, their organizations are dramatically less likely to fail. So culture fit clearly wins in terms of startups surviving and then going public. But studies have shown that after their IPO, these ‘culture fit’ firms grow at slower rates. 

He thinks that what is happening is that early on when you have a really clear mission, it's very helpful to have a bunch of people who are bought into that mission. But then once you become a bigger organization, you end up too homogeneous, having a lot of ‘group think’ making it harder to change and innovate.

Once you become a bigger organization, you can end up too homogeneous having a lot of ‘group think’ making it harder to change and innovate.

By hiring for cultural fit I aimed to ensure that new employees seamlessly integrate into the existing workplace culture.  But although this approach can certainly lead to greater job satisfaction, higher performance, and better retention rates., it also has its pitfalls. When cultural fit is narrowly defined, it can lead to a monoculture, stifling creativity and innovation.

Cultural contribution

So now I’m rethinking my approach and instead of focusing solely on cultural fit, I focus on cultural contribution. This means looking for candidates who bring diverse perspectives and experiences that can enrich the workplace.  This creates more room for diversity of thought and hopefully to better problem-solving and more innovative solutions.

It’s time to embrace cultural misfits—those who don't fit the traditional mold— so that we can foster a more dynamic and creative environment.

 


My to-do list for embracing more diversity

How do I want to put this into practice?
  • Rewrite job postings: Emphasize core values and the unique contributions I'm seeking, rather than rigid qualifications and experience.

  • Revamp the screening process: Look beyond resumes and traditional qualifications. Consider candidates' backgrounds, passions, and potential for cultural contribution.

  • Support new hires: Create an inclusive onboarding process that encourages new employees to share their unique perspectives and ideas.

Conclusion

Rethinking cultural fit doesn't mean abandoning the idea altogether. Instead, it's about broadening the definition to include cultural contribution. By valuing diversity and encouraging employees to bring their whole selves to work, organizations can unlock new levels of creativity and innovation.

It's time to move beyond conformity and embrace the power of diversity.

More information

The wrong way to think about culture fit (Transcript)

Malcolm Gladwell on the importance of self-correction (Transcript)

Think Again: The Power of Knowing What You Don't Know: Grant, Adam

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...