Your ops function isn’t supporting your culture. It’s creating it.
I’ve observed, built, and scaled operations across a lot of different environments: small businesses, nonprofits, higher ed, consulting firms, and agencies. And in every single one of them, I’ve run into the same assumption: that culture is something leadership declares, and operations just keeps the lights on.
I want to push back on that. Because in my experience, operations isn’t the background to the culture. It is the culture, but it’s just quiet about it.
Culture isn’t a value on a wall
Here’s what I’ve come to believe after years of doing this work: culture isn’t built in an all-hands or written into a values deck. It’s built into the accumulated experience of working somewhere every single day. The moments that tell people, without anyone having to say it out loud, this is how things work here.
And those moments are almost always operational.
Is the resourcing fair, or are people constantly absorbing more than they were told? Are handovers actually useful, or does everyone have to rediscover the same information from scratch? Is there a clear process, or does everything run on tribal knowledge and whoever shouts loudest? Does someone’s workload make sense, or are they always one bad week away from burning out?
Those aren’t HR questions or leadership questions… they’re operations questions. And the answers to them shape how people feel about coming to work every day.
What your systems are saying, whether you mean it or not
Every operational decision sends a signal. When a project is chronically under-resourced, the signal is: we expect you to absorb the gap. When time tracking is treated as surveillance rather than a planning tool, the signal is: we don’t trust you. When context-switching is constant because nobody protected the schedule, the signal is: your focus doesn’t matter here.
These signals accumulate and become the unwritten rules. They become what people mean when they say “this is just how it is here…”.
Flip it around, though. When operations are genuinely thoughtful, it sends a completely different set of signals. That someone considered how this person would be set up to succeed. That the organization values people’s time and capacity. That’s culture. Built quietly, through operational choices, every single day.
The ongoing problem
I’ve seen this play out in organizations in a particular way. The creative work is often brilliant, and the people are talented and committed. But if the operational infrastructure doesn’t support them, those things don’t matter as much as they should. The best people burn out or leave. Morale fluctuates so quickly between the excitement of the work and the toll it takes on employees. And leadership looks around, wondering why the culture isn’t what they envisioned.
The data bears this out: The upcoming 2026 Integral Index, an annual study conducted with the Harris Poll, found that nearly 88% of employees in high-trust organizations exhibit positive, supportive behaviors at work, compared to just 44% in low-trust ones. Trust, it turns out, isn’t built in a town hall. It’s built into the systems people navigate every day.
Part of what makes this tricky is that ops is often under-invested relative to the size and complexity of the work being done. There’s a tendency to treat operations as something you’ll figure out as you grow, rather than something that enables the growth. But by the time that becomes obviously unsustainable, the cultural damage is already done.
Operations isn’t just a function that needs to work. It’s a function that needs to be intentional, because even when it’s not trying to, it’s shaping how people experience the organization.
It’s not ops alone
I want to be clear that I’m not saying operations is the only thing that shapes culture. Communication matters too: how information moves through an organization, whether people feel informed and included, whether leadership communicates with transparency or opacity. Your people function is important. How you hire, onboard, and develop people sends messages just as clearly as any operational system.
But in my experience, ops is where culture gets made or broken most consistently. It touches everyone, every day. It’s the thing people feel even when they can’t articulate it. And it’s the thing that, when it’s working well, gives all the other culture-building efforts room to actually land.
What this means in practice
If you’re leading a company, it means your culture strategy needs operations at the table, not just as an implementer of decisions, but as an input to them. The person who understands how work actually flows through your organization has a perspective on what’s sustainable, what’s fair, and what’s quietly breaking people that you genuinely need.
If you’re in an ops role, it means owning the cultural weight of the work. Not just whether the process functions, but what it signals. And not just whether the system is efficient, but whether it’s human and real. I’ve watched those things change what it feels like to work somewhere. And that’s culture. Built from the inside out, by the people doing the work.