Why Customers Defend Broken Systems
Part of the series: The Hidden Rules of Organizations
A company continues using a platform everyone complains about. A department defends a process that visibly slows the organization down. An incumbent supplier survives years of poor performance without serious challenge.
From the outside, these situations look irrational.
From inside the organization, they make perfect sense.
The Strange Stability of Bad Systems
Organizations develop systems over time.
Processes, tools, reporting structures, approval layers, vendor relationships. Even when those systems become inefficient, they rarely disappear quickly. They persist.
Partly because replacing a system is operationally difficult. And costly.
But mostly because systems are not just technical structures. They are social structures. People build roles, responsibilities, and reputations around them. Change the system, and you change the balance of the organization.
This is why bad systems survive. Not because no one notices they are bad. But because the people inside them have learned to live around them - and in many cases, to depend on them.
Why People Defend What Isn’t Working
Social psychologist John T. Jost studied a phenomenon he called system justification.
His research showed something counterintuitive: people often defend existing systems even when those systems work against their own interests.
The reason is not ignorance. It is psychology.
Systems provide stability. They create predictability. They allow people to understand their position inside an organization and what is expected of them. Changing the system introduces uncertainty - new expectations, new power relationships, new risks.
Which means that even when a better solution clearly exists, the existing system often feels safer than the alternative.
Not safer technically. Safer organizationally.
That distinction matters enormously in enterprise sales.
When the System Protects the Past
In enterprise sales, this dynamic often appears in subtle ways.
Earlier in my career, I managed one of our larger accounts where part of the workflow relied on a platform delivered by one of our competitors. The vendor had originally been selected on the promise of several features that were critical for the customer’s operations.
Four years later, those features had still not been developed.
The consequences were visible. Operational workarounds had become permanent. Efficiency suffered. From a purely technical standpoint, the situation clearly justified revisiting the decision.
Yet the organization never launched a new RFP.
The reason was simple. The original vendor selection had been championed by a specific individual. Reopening the decision would implicitly raise a difficult question: was the original choice a mistake? Admitting that publicly inside an organization carries reputational cost.
Which means that sometimes the system protects itself not only by defending processes, but by protecting the people who built them.
Interestingly, the situation began to evolve only after that individual moved to a different department and a new stakeholder took ownership of the problem. Only then did the organization feel able to reassess the situation.
In these situations, the system is not protecting the technology. It is protecting the history of the decision.
What This Means for the Rep in the Room
That pattern - a system holding firm not because the logic supports it, but because the people inside it cannot afford to let go - is one of the most common sources of stalled deals in enterprise sales.
A Rep presents a solution that objectively improves the situation. Better performance. Lower cost. Stronger capabilities. The business case is clear. And yet the organization hesitates.
Not because the solution is wrong. But because the change threatens the internal equilibrium.
Adopting the new solution may require new processes, new responsibilities, new visibility into performance, new accountability structures. It alters the system. And systems resist being altered - not as a failure of logic, but as a feature of how human organizations actually work.
The obstacle is rarely the solution itself. It is the system that surrounds it.
A Familiar Example: The Cloud Transition
This dynamic becomes particularly visible in a type of sale many technology companies now experience: the transition from on-premise systems to cloud-based solutions.
During my career, I have often been responsible for promoting SaaS platforms to customers operating traditional hardware environments - either our own platforms or those of competitors.
These conversations are usually framed as technology upgrades. In reality they are something else entirely.
An on-premise environment often requires a sizeable internal team to operate and maintain it. Five people, sometimes ten, responsible for managing the platform day to day. That team is not just a technical structure. It is an organizational one. It represents roles, responsibilities, and a certain legitimacy inside the company.
Moving to a cloud-based solution changes that equation. Some of those roles may need to be repurposed. Others may disappear. The future operating model often requires fewer people and a different profile of expertise.
From a technical perspective, the transition may be clearly beneficial. From an organizational perspective, it is disruptive in ways that have nothing to do with technology.
Which means that what appears to be a product decision is, in reality, a decision about the structure of the organization itself. The product is rarely the real decision. The real decision is what the product does to the organization.
Understanding this changes how you read resistance. You are not encountering skepticism about the solution. You are encountering a system protecting itself.
The Rep’s Actual Role in a System Under Pressure
Enterprise sales is rarely about convincing someone that a product is better.
It is about helping an organization absorb the consequences of change.
Sometimes that means building internal support among stakeholders who stand to benefit from the new equilibrium. Sometimes it means reframing the problem so that change feels like continuity rather than disruption. And sometimes it simply requires patience - waiting until the organization itself becomes ready to move, because the internal cost of staying still finally exceeds the internal cost of changing.
Reps who understand this stop pushing harder when they meet resistance. They start asking different questions.
Not “why won’t they decide?” But “what would need to shift internally for this to become possible?”
Before Looking at the Customer
This dynamic does not exist only inside customer organizations.
Sales teams often criticize customers for resisting change. Yet the same pattern appears internally without much reflection. Product teams defend roadmaps long after the market has moved. Finance defends pricing models that no longer reflect competitive reality. Leadership defends strategic priorities built on assumptions that have quietly expired.
Every organization protects the system it already knows. Including yours.
Understanding this does not make enterprise sales easier. But it makes it more legible.
Resistance is not irrational. It is the natural response of a human system trying to preserve its internal balance.
The question is never whether resistance exists. The question is what it is protecting - and whether that protection can be renegotiated.
What Comes Next
Systems resist change. But not all resistance is equal.
Some stakeholders push back because change threatens their position. Others push back because they genuinely do not yet see the path. And some appear to support change while quietly slowing it down.
Understanding the difference requires understanding where power actually sits inside an organization - and why it is almost never where the org chart says it is.
That is the subject of the next article: where enterprise decisions actually come from.
#EnterpriseSales #B2BSales #SalesStrategy #OrganizationalDynamics #ComplexSales