Strategy sets the direction. Culture is what gets you there.
You can have a clean roadmap, the right metrics, a compelling narrative. But culture is what people default to when the plan runs out - when the customer call goes sideways, when two people disagree and there's no process to resolve it, when someone has to make a call in the room and the roadmap doesn't cover it. In those moments, culture is the only thing doing the work.
I started to understand this clearly as Risk Ledger scaled. When the team was small, culture was implicit - everyone had been in the same rooms, caught the same decisions, absorbed the same instincts about what mattered and why. Nobody needed it written down. Then the team grew, and new people joined who hadn't been in those early rooms. Suddenly the culture that had felt obvious wasn't transferring on its own. It needed to be made explicit - not because it had changed, but because you couldn't rely on proximity to carry it anymore.
That's when I realised culture isn't something you define once and move on from. You revisit it. You test it against real decisions. You notice when someone optimises for the wrong thing and ask why - not to blame, but to understand what signal they were following. You tell the stories that show what good actually looked like. You let people see the reasoning behind the calls that shaped things, so they can pattern-match rather than just comply.
The moments that reveal it are usually small. Whether someone feels safe to push back in a meeting, or just smiles and moves on. How a mistake gets handled - with curiosity or with blame. Whether the default when things are uncertain is to communicate or to quietly wait. None of that is in any handbook. But it's all culture.
And it compounds, in both directions. A team with strong shared instincts makes better decisions faster, without needing to align on everything. A team without them spends that same energy on confusion, second-guessing, and politics.
One of the places this compounds most consequentially is in who you hire first. The first five or ten people aren't just functional choices - they're cultural ones. They define the standard that everyone who comes after is calibrated against. Get those hires right and something interesting happens: quality people attract quality people. The team itself becomes part of the signal you send to every candidate after that. Get them wrong and you set a ceiling that's very hard to raise - because the culture that forms around early compromises tends to become self-reinforcing.
The founder's specific job here is to be the person willing to hold the bar when it's uncomfortable. To turn down someone who would have been fine, and wait for someone who would be exceptional. To treat a seat going unfilled as less costly than the wrong person sitting in it. That patience isn't just good hiring practice - it's a cultural statement. It tells the team, and everyone watching, what the actual standard is.
The best early-stage teams I've seen built this way have something in common - a founder willing to leave a role unfilled longer than felt comfortable, because they knew the cost of the wrong person compounded faster than the cost of the gap. Each excellent hire raises the bar for who wants to join next, and for what everyone expects of each other. That's the compounding effect culture can have when it's treated as a competitive advantage from day one, not something you come back to once the team is already built.
Culture isn't part of the work. It is the work.
