Culture Is What Your Firm Makes Normal

Culture is often described through the things a firm says it values. Collaboration. Accountability. Client service. Excellence. Autonomy. Growth. Those words can tell you something about what leadership wants the firm to be, but they don't necessarily tell you what it actually feels like to work there.

A firm's culture is also built through repetition. What happens when someone makes a mistake. What happens when someone takes initiative. What happens when a client becomes difficult. What happens when a deadline gets missed. What happens when someone asks for help, challenges a decision, or tries to solve a problem without permission. Those moments happen often enough that people begin learning from them, whether anyone intended to teach them anything or not.

That's the part of culture I want to look at this month. Not culture as a statement on a website or a set of values written in an employee handbook, but culture as something people experience through the way work actually gets done. Because eventually, what happens repeatedly becomes what people expect. And what people expect begins to shape how they behave.

Culture Is Built Through Repetition

Every firm has moments that teach its people what is normal.

Imagine an employee notices a recurring problem with a client intake process. They bring it to leadership, explain what they've noticed, and suggest a change. Leadership takes the concern seriously, considers the suggestion, and works with the employee to improve the process. The employee learns something from that interaction. They learn that identifying problems is useful, that they are allowed to contribute ideas, and that raising an issue can lead to action.

Now imagine the same situation in a different firm. The employee raises the concern, leadership explains why the current process exists, and nothing changes. The employee brings it up again a few months later and receives the same response. Eventually, they stop mentioning it. No policy told them to stop speaking up. No one formally instructed them to stay in their lane. The organization simply taught them, through repetition, what happens when they do.

Neither of these examples requires anyone to say, "This is our culture." The lesson comes from what happened next.

This is why culture can be difficult to identify from inside an organization. The people living within it aren't necessarily thinking about what they're being taught. They're adapting to what they repeatedly experience. Over time, those adaptations become habits, and those habits become expectations about how work gets done.

What Gets Normalized Becomes the Standard

Normalization is not inherently negative. Organizations need standards, routines, and predictable ways of working. The question is what exactly has become normal, and whether that normal is still serving the firm.

If leadership routinely steps in whenever a problem becomes uncomfortable, the team may learn that difficult problems ultimately belong to leadership. If employees are consistently expected to solve problems without being given enough authority to make the necessary decisions, they may learn to protect themselves by asking for permission first. If mistakes are met with curiosity and problem solving, people may become more willing to surface problems early. If mistakes are met primarily with blame, people may become more cautious about admitting them.

These patterns don't have to happen every single time to have an effect. People pay attention to what happens often enough to predict it.

That prediction is important. Once someone knows what is likely to happen when they make a decision, raise a concern, or ask for help, they can begin adjusting their behavior around that expectation. They may stop escalating certain issues. They may start copying the behavior of someone who seems to have figured out how the firm really works. They may avoid taking ownership of decisions they believe will ultimately be taken away from them.

At that point, the culture isn't being created by what leadership says should happen. It is being reinforced by what people have learned will happen.

The Gap Between What You Value and What You Reinforce

This is where stated values can become interesting.

A firm can genuinely value autonomy while creating an environment where employees need approval for routine decisions. It can genuinely value accountability while allowing responsibilities to remain unclear. It can genuinely value collaboration while consistently making decisions without input from the people responsible for implementing them.

That doesn't necessarily mean leadership is being dishonest. More often, it means the operational structure is reinforcing something different from the stated intention.

This distinction matters because people generally respond to the environment they are actually working in. If the message is "take ownership," but the experience is that independent decisions are frequently overridden, the experience is going to carry more weight than the message. If the message is "speak up," but raising concerns repeatedly leads nowhere, people eventually have to decide whether speaking up is worth the effort.

The result isn't always obvious. You may simply notice that people seem hesitant, that fewer ideas are being offered, that decisions keep moving upward, or that employees wait longer than necessary before acting. Those behaviors can look like personality differences or motivation problems when they may actually be reasonable responses to what the organization has consistently reinforced.

Every Response Teaches Something

One of the easiest ways to understand your firm's culture is to look at what happens immediately after something happens.

An employee makes a mistake. What happens next?

Someone misses a deadline. What happens next?

A client complains. What happens next?

Someone makes a decision without asking for permission. What happens next?

A team member tells leadership that a process isn't working. What happens next?

A new person makes a mistake that an experienced employee would have known to avoid. What happens next?

The response matters because every one of these moments creates information about the firm's expectations.

A leader doesn't have to deliver a speech about accountability for the team to understand whether accountability matters. The team learns by watching whether responsibilities are followed through, whether problems are addressed, whether people are allowed to correct their own mistakes, and whether the same expectations apply consistently across the organization.

The same is true for trust. You don't have to tell someone you trust them to make decisions if the structure gives them meaningful authority and allows them to exercise it. Conversely, repeatedly requiring approval communicates something about where trust and authority actually sit, regardless of how empowering the firm's language may sound.

Culture Can Become Self Reinforcing

Once a pattern becomes normal, it can begin reproducing itself.

A new employee joins the firm and asks how something is handled. An experienced employee explains the usual process. The new employee follows it. Eventually, they become the experienced employee teaching someone else.

That's how organizational habits survive changes in personnel.

The person who originally made a decision may leave the firm, but the expectation created by that decision can remain. A managing partner may stop personally reviewing every document, but if the team has spent years believing that leadership approval is required, they may continue routing things upward anyway. A new process may be introduced, but if the old behavior is still rewarded or reinforced, the organization may quietly return to it.

This is one reason changing culture can be more difficult than announcing a new policy.

A policy can change in an afternoon. Expectations take longer.

People need to experience the new pattern enough times to believe that it is actually the new pattern. They need to see that leadership responds differently, that authority is being honored, that accountability works differently, or that the organization really does want them to behave differently.

Culture changes when the experience changes consistently enough for people to adjust what they expect.

What Is Your Firm Making Normal?

This is where I would encourage managing partners to look beyond the obvious signs of culture and examine the ordinary moments instead.

What does your team do when they aren't sure who owns something?

What happens when someone makes a mistake?

What happens when someone disagrees with leadership?

What happens when an employee takes initiative?

What happens when a client pushes back?

What happens when a deadline becomes unrealistic?

What happens when a process stops working?

What happens when someone asks for more authority?

What happens when leadership gets pulled into something that should eventually belong somewhere else?

And perhaps most importantly, what behaviors seem to repeat even though nobody has formally asked for them?

Those patterns are worth examining because they may tell you more about your firm's culture than a list of values ever could.

You may discover that your team is more independent than you realized. You may discover that people are waiting for permission because the structure has taught them to. You may discover that a process everyone considers normal is creating unnecessary friction. Or you may find that your firm is already reinforcing many of the behaviors you want to see more of.

The point isn't to label the culture as good or bad. The point is to understand what the organization is teaching through its everyday operations.

Designing What You Want to Reinforce

Once you can see those patterns, you have something useful to work with.

If you want greater ownership, look at whether people have the authority to actually own their responsibilities. If you want more accountability, look at whether expectations and consequences are clear. If you want employees to raise problems earlier, look at what happens when they do. If you want leadership to spend less time in the middle of routine decisions, look at whether your structure gives other people enough information and authority to make those decisions themselves.

Culture doesn't change simply because leadership decides it should. It changes when the organization consistently creates different experiences.

That may require changing a process, clarifying a responsibility, moving authority, redefining an expectation, or simply responding differently the next time a familiar situation occurs. Sometimes the change is operational. Sometimes it is behavioral. Often, it is both.

This is where intentional operations and culture meet. The systems you design create the conditions in which people work, but the repeated experience of working within those systems teaches people what the organization expects from them. Over time, those expectations become part of the firm's identity.

Your firm is already teaching people how to operate. The question is whether you are paying attention to what they are learning.

Culture isn't only what your firm says it values.

Culture is what your firm makes normal.

The next step is to look at what your firm's current patterns are teaching people, and decide which of those lessons you actually want to keep.

What is one behavior your firm has normalized that you never intentionally decided should become part of the culture? Share it in the comments, or use it as a conversation starter with your leadership team. Sometimes identifying what has become “normal” is the first step toward deciding what should change.