Culture Just Happens — And That's the Problem
Most founders don't think about culture. Not because they don't care, but because there are a hundred urgent pulls on their time and thinking about core values, mission, and vision feels like number 100 on that list. Most founders are highly technical. They're subject matter experts in their field. Just like the financial model, culture is something they know is important, but every hour spent on it is an hour not spent developing the product or landing the first customer.
So culture just happens. And it doesn't always happen in a good way. The first five hires set the tone — how decisions get made, how conflicts get resolved, whether people tell you the truth or what you want to hear. Every person after that either reinforces or dilutes what those first five established. If you're not deliberate about it, you end up with a culture shaped by accident rather than intent. And culture is hard to change later, once people are used to it.
Culture Is Often Why Your Best People Stay or Leave
Compensation gets people in the door. Culture is what keeps them. Talented engineers leave companies paying top-of-market salaries when the culture is toxic — meetings that start late, commitments that slip without consequence, bad news that gets buried. On the other hand people take below-market offers to stay at companies where they felt respected, heard, and part of something real.
At the seed stage, you can't compete on salary. You can compete on culture. The kind of people you want — the ones who thrive in ambiguity, who build things from nothing, who stay when it gets hard — those people care deeply about how the team operates. They're watching. And they'll leave if what they see doesn't match what they were promised.
Culture Match Should Inform Hiring Decisions
Culture is best instilled early, and culture match should actually inform who you hire. Skills can be taught. Work ethic can't. Integrity can't. The willingness to own a mistake and fix it rather than defend it — that's a character trait, and it's the kind of trait that either fits your culture or corrodes it.
When I help founders build hiring processes, we screen for culture fit as deliberately as we screen for technical ability. Not "culture fit" in the lazy sense of "would I have a beer with this person?" but in the operational sense: Does this person commit and deliver? Do they surface problems early? Do they plan carefully and then execute relentlessly? Those are cultural questions, and they matter as much as whether someone can write clean code or build a financial model.
Core Values Need to Be Operational
Core values that nobody can remember are decoration. Core values that change behavior are infrastructure. The difference is specificity. "We value excellence" means nothing. "We ship what we commit to, on the date we committed to" means something. "We value integrity" is generic. "When something is broken, the person who discovers it owns communicating it within 24 hours" is operational.
I help founders write three to five core values that pass a simple test: can you point to a specific situation and say "that's what this value looks like in practice?" Can you point to another situation and say "that violated this value?" If a core value can't be violated, it's not a value — it's a platitude.
High-Performance Teams Commit and Achieve
I give teams extra time to plan. I expect them to question requirements, seek clarity about what they need to do, and push back if timelines are unrealistic. But once the team commits, that commitment is met — because everyone else has planned around it. Failure is not an option. Gene Kranz said those words during the Apollo 13 crisis, and they've guided how I build teams ever since.
"Commit and achieve" is both a cultural value and a standard operating procedure, and that's exactly what culture is — culture guides how work gets done. High-performance teams don't just work hard. They plan carefully, commit publicly, and deliver what they promised. The combination of realistic planning and ironclad execution is what separates high-performance teams from busy ones. Teams that over-commit and under-deliver destroy trust. Teams that plan honestly and then execute relentlessly build it.
Bad News Travels Fast
The culture you want is the one where bad news travels fast — because that's the culture that fixes problems before they become crises. A great manager I once worked for told me: "Be a part of the solution, not a part of the problem." It was an acknowledgement that mistakes will happen and bugs will pop up. But once you realize it's your oversight, you have a decision to make — will you spend your energy defending why it happened, or solving the problem?
A healthy culture is one where mistakes are OK as long as you learn from them. Learn from your mistakes — just keep the tuition cost low. And only make original mistakes. There's something deeply wrong when the same mistakes get repeated, and that's a cultural failure, not a technical one. Intellectual honesty means leadership admits mistakes publicly, explains what they've learned, and describes what's changing. That behavior, modeled from the top, gives the entire organization permission to do the same.
Culture Shows Up in the Small Things
Do we arrive at meetings two minutes early, or five minutes late? One CEO I worked for required attendees to put a quarter in a jar every time they arrived after he did. An SVP at Verizon required the last person to arrive at a large meeting to go to the front of the room and sing a song. Those sound like gimmicks, but they're not — they're signals. They tell the team that time is respected, that commitments matter, and that showing up prepared and on time is the baseline, not the exception.
Culture is the accumulation of these small signals. How you run meetings. How you handle missed targets — do you celebrate objectives achieved and debug objectives missed, or do you look for someone to blame? How fast does information flow? These aren't HR topics. They're operational infrastructure. And they're being established right now, whether you're paying attention or not.
Culture Is the Leadership Team's Job
The buck stops with the CEO — ultimately the founder is responsible for everything that happens in the company. But more broadly, culture is the job of the entire leadership team. In the smallest startups, that may just be the founder. Which is exactly why bringing someone with deep experience in early is so valuable. A fractional COO who has built culture at multiple companies knows how to make values operational, how to build hiring processes that screen for fit, and how to establish the rhythms and standards that high-performance teams run on.
Culture should not be left to chance. It's not fluff. It's not something you formalize at 50 people. It's the operating system your team is running on right now, and it's either helping you execute or quietly working against you. Build it deliberately, starting today.