Why change fails

The language of change

Over the years, I’ve learned to recognize the difference between companies that are truly ready to change and companies that simply like the language of change.

On the surface, they can sound exactly the same. They talk about growth, accountability, alignment, and better performance. They say they want more discipline, more visibility, and a clearer connection between effort and results. They want functions to operate more strategically and contribute more directly to the business. In the early stages, it can feel like real alignment.

But I’ve seen enough transformation efforts by now to know that the real test comes later, when the work stops being theoretical and starts exposing how the organization actually operates.

That is the moment that separates the companies that change from the ones that don’t. Real transformation never stays neatly within a single function. It moves across the organization. It surfaces inefficiencies, disconnected systems, unclear ownership, and the workarounds people have built to compensate for deeper structural problems. It also makes people uncomfortable, because at a certain point, the work stops feeling like an evaluation of a department and starts feeling like an evaluation of how individual leaders and teams are doing their jobs.

When change is real

In the environments where transformation works, leadership understands that discomfort is part of the process. They do not interpret it as a sign that the work is failing. They treat it as evidence that the work is finally getting honest. Some of the most meaningful experiences of my career have come in organizations that were willing to stay with that honesty long enough to do something with it.

I’ve seen that happen in large companies, and I’ve seen it happen in much smaller ones. The common denominator was never size or even budget. It was leadership’s willingness. Usually, that takes the form of a clear mandate from the CEO that the work matters and that no one gets to stand on the sidelines while one team carries the burden. Occasionally, it comes from a group of aligned leaders who understand the stakes and are willing to push the organization toward a more mature way of operating. Either way, the principle is the same: change works when it becomes shared work.

When that mandate is real, teams are expected to work together, not merely encouraged to. Leaders look honestly at their own areas. They identify where things break down, where handoffs fail, where systems don’t connect, where ownership is fuzzy, and where people have learned to manage around problems instead of solving them. None of this is especially glamorous, but it is where progress begins. Once people stop protecting their own lane long enough to solve for the whole, the work gets sharper, and the outcomes improve.

When the mandate isn’t real

What often gets missed is how personal this can feel. People do not only react when their function is being evaluated. They react when it feels like they themselves are being evaluated. That is when some people lean in, and some do not. It is also when leadership proves whether it really wants change or simply wants the comfort of saying it does.

The failed versions usually start the same way. The language is all there. Growth. Transformation. Better performance. But there is no real mandate underneath it. Collaboration is suggested, not required. Problems that span functions are identified, but no one is made responsible for resolving them together. Everyone wants better results, but the organization does not change how it works.

There are usually signs that this is where things are headed. One of the clearest is when a systemic problem gets assigned to one department to solve. If the issue is growth, revenue, customer acquisition, efficiency, or product competitiveness, and the “fix” lands squarely on one team, that is a red flag. It usually means either the problem is not fully understood or the organization is reluctant to address it at the level where it actually exists.

I pay particular attention to the relationship between sales and marketing when growth is the stated goal. If those teams are not jointly talking about the customer lifecycle, the customer journey, what customer acquisition actually looks like in that business, and where the experience is breaking down before someone becomes a customer, the organization is already working in silos. And silos do more than create inefficiency. Over time, they create blame.

Without a neutral place for teams to solve problems together, everything becomes more political. Responsibility gets fragmented. Finger-pointing takes the place of real discussion. The weakest team or the least protected function often ends up carrying more than its share of the burden. In sales-driven environments, that can very easily become marketing.

When it works, the relationship feels very different. Sales and marketing see themselves as part of the same effort. I often think of it as standing back-to-back. One side is focused on attracting and engaging interest. The other is focused on converting that interest into real business. The tactics may differ, but the responsibility is shared. At the end of the day, it is still people trying to attract, engage, convert, and build relationships with other people. If the people inside the company are not connected, the customer experience will not be connected either.

What shared work looks like

One of the best examples I have seen of this did not begin with a formal CEO mandate. It began with a group of leaders who understood what the company was trying to do and recognized that it would not get there by continuing to operate as it was. We came together at the VP level, got permission to work as a cross-functional growth team, and committed to regular alignment with the executive team. It was not quick, and it was certainly not elegant. We spent months in a room together mapping the technology stack, the product roadmap, the marketing and sales funnel, the onboarding process, and the points where things stopped connecting.

What we found was not especially surprising, but it was important. Marketing was generating interest, but the handoff to sales was not working. The opportunities were not qualified in the way sales needed them to be, and the resources in sales were too limited to absorb everything equally. So we changed the model. Marketing took on more responsibility for qualifying and nurturing at scale, while we created a human bridge to ensure that only the right opportunities moved through. We tightened the handoff, clarified definitions, simplified parts of the stack, improved onboarding, and created better feedback loops. It took time, but the company moved forward because the work was shared and the problem was treated as systemic.

That has stayed with me because it demonstrated something I have seen repeatedly: real change does not happen because one strong leader inside one function pushes harder. It happens because an organization decides to solve a problem at the level where it actually lives.

That is also why leadership panic is such a bad sign. Once leaders begin to panic, they tend to narrow the problem. What should remain an enterprise issue is reframed as a performance issue within a single function. Planning gives way to reacting. Patience disappears when change does not produce immediate results. Pressure gets pushed downward. What should have remained shared accountability becomes a localized burden.

At that point, the effort usually starts to break down. Not because the idea was wrong. Not because the strategy lacked merit. Because the organization was no longer willing to face the problem honestly. It needed relief more than it wanted change.

What leadership actually requires

That is the distinction I keep coming back to. There are organizations that want the language of transformation because it sounds ambitious and responsible. Then there are organizations that are actually willing to live through what transformation demands. Those are not the same thing.

Leadership sits at the center of that difference. If you are leading through change, you cannot demand transformation from a safe distance. You cannot ask teams to do the hard, exposing work of changing how they operate while protecting yourself from the discomfort of what that process reveals. Leadership requires more than setting expectations. It requires getting your hands dirty, staying in the room when tensions rise, helping teams work through conflict, and working harder than the teams you are asking to change.

That, to me, is the uncomfortable truth leaders need to see themselves in. If an organization is struggling to change, the question is not only whether teams are resisting it. The question is whether leadership is demonstrating what change actually requires, or simply demanding it without taking on the cost itself.

Without that, what gets called transformation is often something else entirely. It is pressure applied to one part of the organization in the hope that it can compensate for a problem that was never confined to that part in the first place.