Culture Is What You Repeat

Let's be honest, most engineers would rather debug production at 3 AM than sit through another culture workshop.

We've all been trapped in those painful HR sessions about "living our values" while actual work piles up. The eye-rolling is almost audible when someone mentions "culture fit" or "team building exercises."

I get it. I've been there too. Culture feels like corporate fluff.

But whether you hate the word or not, culture is already happening on your team. It's not what HR puts on posters. It's what your team actually does when the deadline is tomorrow and everything's on fire.

It's what it feels like to work on your team and work for you.

This chapter isn’t about company values or all-hands slogans. It’s about how your team actually operates. How decisions get made and how people respond when things go sideways.

Culture is what gets repeated under pressure.

Whether you realize it or not, it’s already happening. The way your team works right now is your culture. And that culture is shaped by your leadership.

If you want to shift the culture, you have to shift what gets repeated. And that starts with you.

So ask yourself:

Do they act with focus, or just chase what feels urgent?

Do engineers ask questions, or wait for orders?

Do they build with users in mind?

You don’t create culture by declaring it. You reinforce a Product Driven culture through what your team sees every day: rituals, reactions, and rewards.

You Don’t Roll Out Culture. You Reinforce It.

At some point, you probably tried to roll out culture like a product launch. You gave a rousing talk about how “things are going to be different around here.”

Your team believed you.

But old habits have a way of creeping back in. The meetings still look the same. The decisions still sound the same. Your team waits it out, wondering if this is real change or just another short-lived executive epiphany.

That inspiring talk didn't fail because your team didn't care. It failed because culture doesn't respond to announcements. It responds to patterns. Your team learns from what you model, what you correct, and what you return to, even when it would be easier to let it slide.

The Product Driven Model gives you the foundation, but only if those behaviors show up in all your meetings and rituals. These repeated moments are where psychological safety begins.

Culture doesn’t change because you announced something new. It changes when your team sees you repeat what matters.

Rituals Teach, Whether You Mean To or Not

If you want to know what your team really values, don’t read the mission statement. Check the calendar.

Culture doesn’t live in posters or slogans. It lives in your standups, demos, 1:1s, and postmortems.

These are the moments where culture actually happens. Not in Slack threads or async updates, but in real-time collision. When people engage, disagree, and decide together.

Every ritual teaches something. The question is: what are yours teaching?

When rituals lack intent, they become theater. Status updates that change nothing. Demos that impress but don't improve. 1:1s that check boxes but miss what matters.

But when you treat these moments as culture-building tools, everything shifts.

A standup becomes a daily reconnection to the customer's world. A demo transforms from performance to "here's the problem we solved." A 1:1 evolves from task review to coaching ownership and courage.

The same meetings. Different intent. Completely different culture.

Vision doesn't live in quarterly kickoffs. It lives in the repeated question: "Why are we doing this?" Focus isn't a roadmap. It's what you say no to when planning. Clarity isn't documentation. It's the conversation that prevents confusion.

These moments compound. They teach your team that customer impact isn't optional, it's the point.

Are your rituals reinforcing a Product Driven team, or are you just going through the motions?

How Demo Days Changed Everything at Basys

Chris Borchers understood this when he joined Basys as Chief Technology and Product Officer. His team was stuck. Stories rolled over. Progress was invisible. Product thinking was missing.

He didn’t start with a reorg. He started with a ritual.

A simple, consistent Demo Day where engineers showed working software to the rest of the company, live.

“It started small with just the team,” Chris said. “Then we added the president. Then operations and sales. Eventually, the CEO showed up and said, ‘That was the best meeting I’ve ever been in.’”

And the tone shifted.

They started building for visibility, so their work could be understood and valued.

In one demo, a junior engineer walked through a redesigned claims interface. A support manager jumped in and said, “That’s going to cut our support calls in half!”

Not only did that shift the engineering team culture, but it also shifted the entire company culture.

Reinforcement Is the Culture

Your team doesn’t learn what matters from a values slide. They learn it from what gets rewarded. It shows up in who gets praised, promoted, and thanked out loud.

Those signals shape the culture, whether you realize it or not.

When you celebrate the engineer who shipped at midnight, even with good intentions, it can still send a signal: speed over sustainability.

Celebrate the one who paused to rethink a decision based on new user feedback, and you’ll signal curiosity matters too.

Promote the person who hit every deadline but left a mess behind, and you’ll get more short-term thinking.

Shout out the PM who admitted they were wrong and changed course, and you’ll get more courage.

People copy what gets noticed.

Cultural drift doesn’t come from bad intentions. It creeps in through signals we don’t always notice, when the words say one thing but the rewards say another.

Praising courage while punishing risk. Preaching outcomes while rewarding output.

Ask yourself:

If you were on your team, what would you assume your leader actually values?

Based on what your team sees in meetings, what do they believe gets rewarded here?

What behaviors are you repeating, intentionally or not?

Pick one ritual to run with more intention this week. One question to ask that reinforces product thinking. One moment to praise the behavior you want to see more of.

Then do it again.

Repetition isn’t just how culture forms. It’s how culture sticks.

Vision gives the work meaning. Repetition makes that meaning last.

Culture isn’t built in big moments. It’s forged in every question you ask, every behavior you praise, every meeting you lead.

How do you want it to feel to work for you?