A Culture Recipe: Why Building Great Teams Takes Time You Can't Rush

Like any dish, creating a near-perfect culture takes time. Rushing it destroys the ingredients that make it special. Our culture specialist on what we've learned.

Culture Is Cooked, Not Assembled

Like most dishes worth eating, a decent culture takes time to get right. Rush it and you ruin the ingredients that made it worth building in the first place. As someone who spends a lot of time thinking about this stuff, that means treating every ingredient — every hire, every ritual, every value we actually say out loud — carefully enough that it doesn't lose its flavour somewhere along the way.

The Ingredients We Refuse to Rush

A few things we've learned not to shortcut:

• 01Hiring for curiosity over credentials. A polished CV tells you what someone's already done. It doesn't tell you whether they'll still be asking good questions eighteen months in.
• 02Protecting the rituals that make recognition immediate. Something like the KKG only works because it's never skipped, even on the weeks it'd be easier to let a good moment slide by unmarked.
• 03Letting ownership be earned rather than handed out on day one. Trust given too early doesn't really mean anything. Trust built up gradually, through small wins, is what actually holds a team together.

What Happens When You Rush It

We've seen what a rushed culture looks like from the outside — a values page that reads nicely but doesn't match how people are actually treated day to day, rituals copied from somewhere else that never quite take, hiring done for speed instead of fit. It looks fine for a quarter or two. Then it falls apart exactly when the team needs it most, under real pressure.

The teams that last tend to be the ones willing to let it take as long as it needs, checking at every stage that whatever's being added isn't watering down what's already there.