The first senior leadership role I inherited came with a culture I had not been warned about clearly enough. The organization was technically competent, had a strong track record on measurable outcomes, and had a well-established set of values that were posted in every meeting room. It also had a specific, deeply embedded pattern: people told those above them what those people wanted to hear. Not obviously — the organization was too sophisticated for obvious sycophancy. But the information that reached senior leadership was systematically optimistic, problems arrived late when they were already large, and decisions that went against what the senior leader seemed to want were made rarely. The culture was not of the kind that any diagnostic framework would label "broken." It was in many ways high-performing. But it had a structural problem with honesty that was expensive in ways that weren't always visible.
What I learned over the following three years of genuinely trying to shift that pattern is the subject of this essay. The short version: you can change inherited culture, but not by doing most of the things that feel most natural when you're new to a role. You can't change it by announcing what you want to build. You can't change it by redesigning systems before people believe the change is real. You can't change it through a series of culture-focused off-sites or cascaded communications. You change it the same way culture gets built in the first place: through the accumulated weight of repeated behavioral choices, made consistently enough, over enough time, that people start to believe the new pattern is actually real.
That takes longer than anyone wants it to. It requires more patience and more consistency than most leaders expect when they step into a new role with a clear vision of what they want to build. And it starts with a diagnostic period that most leaders underinvest in because it feels like delay rather than progress.
The diagnostic first — and why it matters
Before any culture-change effort, the most important work is an honest diagnosis of what you've actually inherited — not of the stated culture, which is usually visible in the values document on the wall, but of the actual culture: the real norms, real incentives, and real behavioral patterns that determine how things actually work.
This diagnosis is harder than it sounds. The actual culture is not always what people will tell you directly, particularly in the first weeks of a new role when they're still calibrating how safe you are. What you learn in your first month is often more about what people are willing to say to a new leader than about what's actually true. The real diagnostic work happens through observation: what comes up repeatedly in different conversations? What seems undiscussable? What patterns of avoidance are consistent across different people and contexts? Who gets protected and who doesn't? Where does information slow down or stop?
The most important diagnostic question I've found is: what would have to be true for this culture to make sense? Almost every inherited culture, even one with significant problems, was a rational response to something — an organizational history, a previous leadership style, a period of threat or instability that required certain behaviors to survive. Understanding that history is what makes culture change possible rather than just irritating to the people who lived through it. The culture that protects leaders from hearing bad news wasn't built by people who think that's a good idea; it was built by people who learned, through experience, that bringing bad news was costly. Changing that culture requires understanding and addressing the original learning, not just announcing that things will be different now.
What the first ninety days actually teach
A new leader's first ninety days are a critical culture-setting period — not primarily because of what the leader announces or decides, but because of what the organization learns from watching the new leader in unscripted moments. People in inherited organizations are calibrating, during this period, several specific questions: what does this person actually care about, not just what do they say they care about? How do they respond when things go wrong? What happens when someone tells them something they don't want to hear? Is this change real, or are we waiting it out?
The answers to these questions are not produced by a well-crafted 90-day plan, though such plans have value for other reasons. They're produced by the small, observed moments that happen constantly in the early weeks: how the leader responds to a small problem, what they do when they receive uncomfortable information, how they engage in the meetings where the culture plays out in real time.
In the organization I described, the first culture-shifting moment I had was in a leadership team meeting about six weeks in, when a direct report presented projections that I suspected were more optimistic than warranted. In the previous culture, the response to optimistic projections from a senior leader had been acceptance — maybe with some probing questions, but ultimately endorsement. I asked for the downside scenario, asked why it hadn't been included in the materials, and said directly that I needed to see the honest range rather than the preferred case. The room went slightly quiet. Several people later told me independently that this was the first meeting where they believed the culture might actually be changing.
One meeting doesn't change a culture. But one meeting can teach people what the new leader is actually going to do — and that learning starts to reshape what they put in front of them next time.
The sequencing that works
Culture change that actually produces lasting shifts follows a sequence that is counterintuitive to most leaders who are eager to build something different. The sequence: understand first, then model the behaviors you want to see, then recognize and celebrate early examples of the new culture from others, then make structural changes that make new behaviors easier and old behaviors harder, and then — only after demonstrating sustained behavioral commitment — update the formal systems to reinforce the new direction.
The failure mode, which is extremely common, is reversing this sequence. Changing the formal systems first — announcing new values, revising performance review criteria, launching culture initiatives — before anyone believes the change is real. Formal systems changed without behavioral modeling get absorbed by the existing culture and interpreted as the latest management initiative: to be acknowledged publicly, waited out privately. People who have survived multiple leadership transitions in an organization develop sophisticated filters for distinguishing between changes that are real and changes that are performative. The signal that distinguishes the two is not what leaders say they value; it's what they consistently do in the moments that reveal what they actually value.
The behavioral modeling phase is the longest and least glamorous part of culture change. It requires doing the same things repeatedly — honoring honesty, addressing problems directly, owning failures accurately, protecting the people who tell the uncomfortable truth — without immediate organizational feedback that anything is changing. For the first six to twelve months, the leader is essentially working without visible results. The culture is watching, calibrating, deciding whether this is real. The answer comes out gradually, in small behavioral shifts that only add up to visible change over years, not months.
The elements you can't skip
Several specific elements of the culture change process cannot be skipped without undermining the rest of the effort.
The first is addressing the people who embody the old culture most visibly and most influentially. Every organization has people — sometimes very senior, sometimes informal influencers — who are active carriers of the cultural patterns you're trying to change. Not because they're malicious, but because those patterns have served them and they've built their professional identity around them. These people will not simply adapt to the new culture when they observe the new leader modeling different behaviors. They will continue to generate the old culture in their own interactions, in ways that have more influence on many people's daily experience than the new leader's behavioral modeling.
Addressing these people requires honest, direct conversations about what's expected and what will change. Sometimes it requires decisions about whether those people can make the transition. The leader who tries to change culture while protecting the most influential carriers of the old culture typically produces a culture in permanent transition — one where the official narrative says one thing and the actual power structure says another, and people learn to navigate the gap.
The second is the structural changes that make the desired behaviors easier. Culture is shaped by what the system makes easy and hard. If the performance management system rewards individual heroics and punishes collaborative failure, you will have difficulty building collaborative culture regardless of how clearly you model it. If the meeting structure always runs out of time for substantive problem-solving and prioritizes status reporting, you will have difficulty building a culture of candor regardless of how much you talk about it. The structural work — redesigning the systems that shape the daily experience of the organization — is what makes the behavioral changes sustainable rather than dependent on constant leader reinforcement.
The third is patience that is genuine rather than performed. The leadership literature on culture change almost universally notes that significant culture change takes three to five years in organizations of meaningful scale and history. This is true, and most leaders believe it intellectually while expecting the culture they're building to be visible in twelve to eighteen months. When the twelve-to-eighteen-month markers don't show the change clearly, leaders often lose faith, change their approach, or decide that this particular culture is unusually resistant. The three-to-five-year timeline is not pessimism — it's an accurate description of how deeply encoded cultural systems actually change. The culture-building process is inherently slow because it requires accumulated experience to replace accumulated experience.
What progress actually looks like
Progress in culture change is hard to measure against the destination you're moving toward. It's easier to measure against the starting point. The indicators that the work is producing something real tend to be behavioral and incremental: problems that previously arrived late are now arriving earlier. Conversations that were previously superficial are becoming more direct. People who previously managed information are starting to share it more honestly. These changes don't show up in engagement surveys in the first year — they show up in the quality of conversations the leader is having and the quality of information they're receiving.
One particularly reliable indicator: the first time a leader in the organization does something that embodies the new culture at visible cost — chooses honesty over convenience, acknowledges a failure clearly instead of managing the narrative, surfaces a problem when it would have been easier to let it ride — and is visibly supported rather than penalized. That moment is a culture-setting event. The organization watches it and updates their model of what's true here now.
After three years of consistent work in the organization I described, the specific indicator I noticed was this: senior leaders started bringing me problems before they had solutions. In the old culture, the norm was to only surface an issue when you could simultaneously present a resolution — because surfacing a problem without a solution felt like acknowledging inadequacy. The shift to bringing problems early, trusting that the response would be collaborative rather than evaluative, was not something I could have manufactured. It was something that accumulated through enough repeated experience of problems being received with curiosity rather than judgment that the new behavior started to feel safe. By the time I noticed it clearly, it had been developing for at least a year. That's how culture change actually moves.