
Silos, delays, low ownership, passive meetings, teams that hesitate to speak up. At some point, someone names it: “We need a culture shift.”
So a program gets launched. Posters appear. A values workshop is scheduled. Maybe there’s a new set of principles, a competency model, a new mantra. It all feels like progress, because it is visible. But then the real test arrives: regular work.
The same escalations return. The same incentives win. The same decision bottlenecks reappear. And the same people who said all the right things in the workshop go back to doing what the system quietly requires.
That is the first uncomfortable truth: Culture change is a consequence of the system, not a result of individual will.
So if you want a culture where people act differently, you usually do not start by asking people to “be different.” You start by changing what the system rewards, punishes, slows down, and makes safe.
What culture actually is
Culture is not your values deck. Culture is the behavior that becomes normal over time, especially under pressure.
It is what people do when:
- a deadline is close
- a customer is unhappy
- a leader is stressed
- a risk is inconvenient
- a mistake is visible
If your culture “looks fine” when everything is calm but collapses when pressure rises, that is rarely a people problem. It is usually a system with the wrong defaults.
Why culture change programs fail
This is where many well-intended initiatives run into a wall. Culture change programs often fail because they are built on a hidden assumption: “If we teach people the right behaviors, culture will change.” In reality, people adapt to the system faster than they adopt values.
A few common failure modes:
- Incentives contradict the message. Collaboration is preached, but rewards favor individual heroics.
- Decision rights are unclear. Teams are told to “own outcomes,” but approvals still sit in a few hands.
- Feedback loops exist, but consequences do not. Surveys are run, retros happen, but nothing changes afterward.
- Flow is broken. Work is fragmented across dependencies, so people optimize for local survival, not shared outcomes.
- Leaders try to change people instead of the environment. Coaching becomes a substitute for fixing constraints.
Over time, the culture program becomes a layer on top of reality, instead of a redesign of reality.
A systems view of culture change
If culture is behavior, and behavior is shaped by systems, then the culture question becomes practical: What in our system makes the current behavior the rational choice?
That is the shift: away from judging people, and toward understanding the conditions they are adapting to.
Here’s a simple model you can use.
Culture is shaped by these levers
Incentives and metrics
What gets rewarded, what gets punished, what gets measured, what gets ignored.
Decision rights
Who can decide what, how decisions happen, and what happens when people disagree.
Flow of work
How work moves, where it gets stuck, how dependencies are handled, and how much context switching is normal.
Feedback loops
How often reality is inspected, who participates, and whether feedback leads to action.
Information visibility
What people can see, what stays hidden, and what gets escalated only when it is too late.
Social safety and trust
Whether people can speak honestly without paying a price later.
None of these are abstract. They show up daily in meetings, handoffs, Jira boards, approvals, staffing, and leadership reactions.
So instead of asking, “How do we motivate people into a new culture?” a more useful question is: What does the current system train people to do?
Case example: psychological safety does not improve through slogans
One of the most common culture goals is psychological safety. And it makes sense. Without safety, you do not get learning. Without learning, you do not get adaptability. Without adaptability, you do not get outcomes in uncertain environments.
In a fintech context, we saw a familiar pattern:
- low psychological safety signals in teams and leadership interactions
- people avoiding tough conversations
- a tendency to escalate late instead of raising risks early
The obvious move could have been a training on psychological safety.
Instead, we started with the environment. We ran surveys to understand where safety broke down and how people experienced leadership. Then we focused on actions that changed the social system, not just the language. We designed events that helped leaders and teams learn more about each other as humans, rather than forcing a “let’s feel safe now” ritual.
The shift was subtle, but real:
- relationships strengthened
- openness increased in small moments
- leaders felt more confident, not because they controlled more, but because they understood more
- trust increased because people experienced follow-through, not because someone demanded vulnerability
That is what culture change looks like when you treat it as system design:
You change the conditions that make honesty and learning possible.
If you want to explore how we approach this work in a structured way, start here: Organizational Change service.
The five practical system levers leaders can pull
So what does this look like in practice? If you want a lasting culture shift, these are the levers that usually matter most.
1) Fix incentives that reward the wrong behavior
Culture follows rewards.
If speed is rewarded but quality is punished indirectly, you get shortcuts.
If output is rewarded but outcomes are ignored, you get busy work.
If “being right” is rewarded but learning is seen as weakness, you get politics.
A simple way to spot misalignment is to answer these questions honestly:
- Who gets promoted, and why?
- What behavior gets praised in leadership meetings?
- What gets celebrated at all hands?
- What do people avoid because it creates risk for them?
Culture change often starts by aligning incentives with what you say you want.
2) Clarify decision rights, and make them usable
Decision rights shape ownership.
If teams do not know what they can decide, they stop acting. If they can decide but get overridden randomly, they stop trying. If approvals are slow and unpredictable, people escalate early, not because they want power, but because they need certainty.
Healthy decision systems usually have:
- clear boundaries (what is local vs what is shared)
- visible criteria (how decisions are evaluated)
- a clean escalation path (when conflict is real)
- consistency (same rules under pressure)
If you want a culture of ownership, you need a system where ownership is not punished.
3) Improve flow, because broken flow creates broken behavior
Most “culture problems” are also flow problems.
When work is constantly blocked by dependencies, people become defensive. When priorities shift weekly, people stop caring. When there is too much work in progress, collaboration becomes noise.
Flow levers that can shift behavior quickly:
- limit work in progress
- reduce handoffs
- shorten feedback cycles
- make dependencies explicit, then redesign around them
A culture of collaboration is hard to sustain inside a system that forces constant coordination just to survive.
4) Build real feedback loops, not performative ones
A feedback loop is only real if it leads to action.
Retrospectives that never change anything teach people to stop being honest.
Surveys without follow-up teach people to stop answering honestly.
Make feedback loops smaller and more frequent:
- micro-retros weekly, not only once a month
- clear “we heard you, we did this” communication
- visible ownership for next steps
When people see that speaking up changes something, safety grows naturally.
5) Redefine leadership as system design
This is the big one.
If leadership is mainly framed as influencing people, culture change turns into motivation theater.
A more useful frame is this: Leadership is the ongoing work of shaping the system so that good behavior becomes the easiest behavior.
And the goal is not dependency on charismatic leaders. The goal is a setup where good behavior makes sense, even when nobody is “pushing” it.
If you are a decision-maker in the company, you can start with:
- policies that remove fear
- decision systems that enable ownership
- incentives that reward learning
- structures that reduce dependency friction
- rituals that create visibility and follow-through
This is where systems thinking stops being academic and becomes operational.
Where authenticity fits: integrity and adaptability as culture mechanics
Two pillars matter here: integrity and adaptability. They are not “soft” ideas. They are system stabilizers.
Integrity
Integrity is consistency between what you say and what happens. It shows up when:
- a leader protects the person who raised the uncomfortable risk
- decisions follow the stated criteria, even when it is inconvenient
- shortcuts are not rewarded quietly
- accountability is real, not political
When integrity is missing, people adapt by protecting themselves. That becomes the culture.
Adaptability
Adaptability is the system’s ability to learn without needing a crisis. It shows up when:
- feedback loops are short and acted on
- teams can try small experiments without permission battles
- leaders treat surprises as information, not as failure
- ways of working evolve based on reality, not ideology
When adaptability is missing, people become compliant. They wait. They stop caring. That becomes the culture.
Learn more in our workshops:
- 4 Pillars of Authenticity
- Learning Organization workshop
- Outlast Leadership Challenge (coming soon)
A simple checklist to start your culture change the right way
If you take only one thing from this article, take this:
You cannot change into a culture. The culture is what follows the behavior.
So start with behavior, then ask what shapes it. Use this checklist in your next leadership conversation:
- What does our system reward today?
- Where are decision rights unclear or inconsistent?
- What breaks flow and forces defensive behavior?
- Which feedback loops exist only on paper?
- Where is speaking up expensive?
- What is one constraint we can remove in the next 30 days?
Do that consistently, and you will not need a culture program.
You will get a culture shift as a side effect of better system design.




